yes, on Mastodon when a user block an instance, it’s more like a mute than a block. Your posts will still be available to them, but you won’t see their content.
The only solution if you want to protect your content from being shared on an instance is to block it at the instance level AND that the instance use Authorised Fetch.
Not all instances have this feature on.
Indeed, it’s downright incoherent on a protocol like ActivityPub. The whole point of a system like this is to let content spread around. This isn’t supposed to be a walled garden, with all sorts of terms and conditions and DRM and whatnot. When you make a post and click “send” you’re announcing that content to the whole world. Even to parts of the world that you may not like.
It’s ironic that many of us came to the Fediverse because Reddit tried exactly this sort of nonsense.
I came to the fediverse in 2017, so nothing to do with reddit or meta or twitter.
The fact is here, we have a choice. So you do you.
On mastodon I have an account on an instance that blocked meta and is using authorised fetch (so the proper way to block a domain) : great, my content won’t go there or on any other blocked domains : it’s my choice.
I have another account on another instance that didn’t blocked meta : great, my content will be shared with threads users and I will be able to browse threads.
Choice, isn’t it great?
protecting your content from being pushed to an instance that you though your blocked.
protecting your content from being shared where you though it won’t because of the way things are worded.
And what’s stopping these people and these instances from spreading that content using just the publicly available link? Instead of just clicking “share” they’ll have to open an anonymous browser window and copy paste the link from there, the horror!
