The 41% number combines both instances that have actually blocked Threads and those who have pledged to do so at some point, so “have blocked” is a bit misleading
As stated, this is a percentage of instances, not users. Roughly 24% of users are on instances that have limited, blocked, or pledged to block Threads.
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.
For clarity:
How do we as users go about blocking them? Can we yet? Or do we have to wait for v .19?
Pre-0.19 I assume you would need to be on an instance that is blocking them.
Post-0.19 you can block them as an instance, meaning “any posts from communities which are hosted on that instance are hidden”
So, the answer still varies depending on your goals for blocking.
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.
Thank you!