good.
Don’t stop now
MOAR
I wonder how that breaks down in terms of numbers of users. The largest instances seem to have federated, and they’re the ones that cost the most to run, and Meta has vast amounts of disposable income. I worry Meta will fund some of them in exchange for influence.
Meta doesn’t need to bother with back-channel influence peddling of existing instances. If Meta simply opened its own Lemmy instance it would immediately be the largest Lemmy instance by orders of magnitude.
For clarity:
- 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.
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.
