Skip to main content

If you're an ordinary Mastodon user, the "block domain" option does not block servers, it just mutes them. It hides their posts from you, but does not hide your posts from them.

Only server admins can do actual blocks through defederation, preferably on a server that has activated "authorized fetch".

For example, if you want to avoid threads.net, you need to join a server that has defederated threads.net. (You can find nice servers that block threads.net at https://fedi.garden)

#FediTips


Fedi.Garden

Highlighting nice servers on Mastodon and the Fediverse
fedi.garden
#FediTips

reshared this

in reply to Fedi.Tips

Fedi.Tips
Fedi.Tips
• •

p.s. For anyone interested in following up the technical side of the problem with user-level domain blocks, have posted in the relevant Github issue about the topic at https://github.com/mastodon/mastodon/issues/18345 (my specific post is at https://github.com/mastodon/mastodon/issues/18345#issuecomment-2047232852)

I've included screenshots of testing so people can see what the problem is. The first screenshot is from a user-level account block (posts all hidden, follow button greyed out), the second is user-level domain block (posts visible, follow button clickable).

Screenshot of an account that has blocked the viewing account. None of the posts are visible, and the follow button is greyed out so it cannot be clicked.
Screenshot of the same account viewed from the same server, but only the domain block is active. The posts are visible, and the follow button is not greyed out so it can be clicked.

Blocking instances by users ยท Issue #18345 ยท mastodon/mastodon

Pitch I would like to see the addition of the possibility for users of any instance to be able to block instances themselves, not just mute them. Motivation I think it could reduce work for moderat...
GitHub
This entry was edited (3 weeks ago)
โ‡ง