I’ve used this analogy before, but threads is like a huge, 5k passenger cruise ship docking in a small town in Alaska. You don’t have to know ahead of time that the 2 public bathrooms, one at the general store and the other at McDonalds, aren’t going to be enough. You can also forecast the complaining about how everything isn’t really tourist ready. It will suck for everyone. The small museum will be overrun and damaged, the people will be treated like dirt. It’s an easy forecast.
Here’s the important bit, just because they’ve never been in the cruise line business, doesn’t mean you have to give them a chance to ruin your town.
edit: made sentence make sense.
The problem with analogies is that they are not literally the thing that you’re analogizing, so there’s going to always be parts of the analogy that don’t “work.”
In this case, what resource is Threads (the cruise ship) actually using from the small town (the rest of the Fediverse?) that causes the inhabitants of that small town any actual trouble? The fact that people on Threads can read posts from people on the Fediverse doesn’t actually affect people on the rest of the Fediverse in any way. If you’re concerned about the converse - the Fediverse being overrun with content from Threads - that’s not actually something that they’re implementing.
This comment feels like it’s been on the Fediverse too long. To continue the analogy, your small town suddenly starts hosting a lot of voices on soap boxes. The more visited the town becomes, the more town criers it gets. Those criers bring their audiences, so not only do you have long queues for the two public bathrooms but you get fights in the town square; struggles over ideologies and all the underhanded trolling that entails. Corpos move in, governments move in, all eager to bend the ear of anyone unfortunate enough to get in grabbing range.
I liked Digg. I loved Reddit. At some point you just need to make a stand. Money and profitability aren’t part of the equation, fuck’em. I’ll keep my small town tyvm.
that’s not actually something that they’re implementing.
That’s not true, their CEO said that you’ll be able to converse and comment without leaving the app in the near future. Also, most instance owners are small, they could be overwhelmed pretty easily.
I’m 100% sure that this small town isn’t ready for a cruise ship. That’s not to say, that in a year or two, we couldn’t be prepared for it. Right now, the relatively small influx from Reddit brutalized the existing community. This is the wild, wild, west for Meta because they’re not getting enough new users for their shareholders in their existing platforms, I’m sure they’re salivating.
A Threads users’ content is only going to be visible outside of Threads if the user explicitly opts in to that. The vast majority of people aren’t going to do that, or even be aware they can do that. In this analogy, most of the people aren’t going to be aware their cruise ship has docked at a town and aren’t going to be interested in getting off of it.
Is it really that big? I thought a bunch of folks tried it for a week then stopped–especially when they realized you can’t delete your account without also deleting your linked Instagram account (assuming you have one).
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.
We haven’t blocked Threads yet, but I haven’t seen any content from it either. When exactly are Threads supposed to federate?
good.
MOAR
