I think instance admins should leave it to their users to block #Meta (or not). All the tooling is already there; it's very easy for a user to block an entire domain.
@null if a server is configured to be higher security (aka AUTHORIZED_FETCH is turned on) then an instance level block does offer specific privacy protections that a user level block does not
if authorized fetch is on (defaults to off) and the instance is blocked, then it can’t maliciously access the posts aside from scraping; ActivityPub calls are then gated behind authorization.
If it’s off and/or only individuals block the instance, it can still fetch posts from those individuals; you have to trust that the instance’s code is well-behaved.
@darius@null
Just a question, maybe you can help me to understand it. After I read your post, I search for answers in the documentation of Mastodon, and I found that as a user, I can block other users or a domain, but with different results https://docs.joinmastodon.org/user/moderating/#block
That means, when I block a user, I don't get her/his data and she/he doesn't get my data.
But if I block a domain, that means that I silence it, I don't see the data and that from the blocked domain my data is accessible, is it right? That mean, that if as a user I block the instances of Meta, that wouldn't prevent Meta to access my data.
Have I understood well?
The only possibility to block effectively Meta in Mastodon is if the administrator defederates Meta?
Thanks a lot!!
Add comment