Mute is local client-side filtering, blocking happens server side.
When you mute something it’s just filtered out of the view you’re presented with in the client - you’ll still see that content if you visit using a web browser.
v0.19 will have this feature natively and app developers can use the API endpoint to allow their users to block posts from whole instances from their feeds. It won’t block comments however.
I don’t think lemmy supports blocking instances (only users and communities)
However boost can mute instances (as well as users and communities)
I’m not sure what the difference is. But I think it’s that boost will not show thing from your feed based on the mute list
Whereas setting something as blocked will prevent the lemmy servers from ever serving that community in your feed.
Fwiw Connect has the ability to block instances
Mute is local client-side filtering, blocking happens server side.
When you mute something it’s just filtered out of the view you’re presented with in the client - you’ll still see that content if you visit using a web browser.
v0.19 will have this feature natively and app developers can use the API endpoint to allow their users to block posts from whole instances from their feeds. It won’t block comments however.