How to Kill a Decentralised Network (such as the Fediverse) écrit par Ploum, Lionel Dricot, ingénieur, écrivain de science-fiction, développeur de logiciels libres.
This is why I’m in favor of not having await and see policy toward Threads. The safest thing to do is assume they’re lying.
Threads users aren’t Fediverse users. Meta isn’t another instance. Even former Meta employees should be treated with extreme suspicion for years if they try to defect.
Nobody who’s ever worked for “Big Social” should be allowed to touch the ActivityPub standard. It should be obvious that their livelihood goes against what it stands for.
Cool, so pick an instance that plans to defederate with them and you’re golden.
Personally, I think all the anti-Threads stuff is paranoid rhetoric and I’d rather see how it pans out. My instance admin agrees so we’ll see how it goes.
Point is you can choose because that’s the entire point of the fediverse. And it’s why I don’t understand why folks are expending so much energy writing paranoid pieces on this topic when they could just defederate and move on.
pick an instance that plans to defederate with them and you’re golden.
That’s not how this works. This is a threat to the concept of the fediverse. It doesn’t matter what instance any of us picks.
Threads already has hundreds of millions of users. Once they activate ActivityPub, they will be hundreds of times larger than the rest of the Fediverse combined. Instantly we will be a tiny minority of the users of this platform. That will give Meta unimaginable influence over this platform and technology.
If you don’t like an ActivityPub participant you block it. It’s in the architecture.
And given the current fediverse is already a tiny fraction of total social media activity, if a bunch of anti-Threads instances hive off to form their own fediverse subgroup, it’ll basically be a no-op from their perspective. They’ll just keep talking to each other off in a little corner by themselves just like they’re doing today. That’s kinda the whole damn point of a federated architecture.
This is why I’m in favor of not having await and see policy toward Threads. The safest thing to do is assume they’re lying.
Threads users aren’t Fediverse users. Meta isn’t another instance. Even former Meta employees should be treated with extreme suspicion for years if they try to defect.
Nobody who’s ever worked for “Big Social” should be allowed to touch the ActivityPub standard. It should be obvious that their livelihood goes against what it stands for.
Cool, so pick an instance that plans to defederate with them and you’re golden.
Personally, I think all the anti-Threads stuff is paranoid rhetoric and I’d rather see how it pans out. My instance admin agrees so we’ll see how it goes.
Point is you can choose because that’s the entire point of the fediverse. And it’s why I don’t understand why folks are expending so much energy writing paranoid pieces on this topic when they could just defederate and move on.
That’s not how this works. This is a threat to the concept of the fediverse. It doesn’t matter what instance any of us picks.
Threads already has hundreds of millions of users. Once they activate ActivityPub, they will be hundreds of times larger than the rest of the Fediverse combined. Instantly we will be a tiny minority of the users of this platform. That will give Meta unimaginable influence over this platform and technology.
I’m not sure I can spell it out more clearly.
No, that’s literally how this works.
If you don’t like an ActivityPub participant you block it. It’s in the architecture.
And given the current fediverse is already a tiny fraction of total social media activity, if a bunch of anti-Threads instances hive off to form their own fediverse subgroup, it’ll basically be a no-op from their perspective. They’ll just keep talking to each other off in a little corner by themselves just like they’re doing today. That’s kinda the whole damn point of a federated architecture.