It should come as no surprise that the lemmy.ml [http://lemmy.ml] admin team
took about 2 minutes to decide to pre-emptively block threats / Meta. Their
transparent and opportunistic scheme to commodify the fediverse and it’s users
will not be allowed to proceed. We strongly encourage other instance
administrators to do the same, given the grave threat they pose to the
fediverse.
You don’t wait and see how it goes with these sorts of things. They will destroy the community before you can take action and it’ll be too late. They will do their best to destroy the fediverse and privatize it. They can’t buy it like they usually do with competition, so they’ll ooze their way in, contribute bullshit to the project, create new proprietary functionality that only works on their instance, convince everyone all the other instances are broken, and walk away with all the users. You don’t invite vampires into your house.
Do you realize that fediverse is not one single project? For example Lemmy and Mastodon has different implementation and developers. The only thing that connecting them is ActivityPub, which is owned by W3C, not the community.
So basically Meta created their own implementation for Threads (so it’s already propertiary), and theoretically already able to pressure W3C to change the ActivityPub without even joining fediverse
How will they destroy it if they are literally only making it larger and more useable. The average normie today has no reason to create a mastadon account, because almost no one uses it. But if they can use a major social media platform, and use a federated free service like mastadon, then that makes mastadon much more valuable to them.
The fact that a social media service is objectively good doesn’t mean anyone is going to use it. Having backing from the biggest social media company in the world, might actually get people to use it.
I started swaying towards defederating after reading this article, maybe you’d like to take a look and see what you think? It argues much better than I ever could.
So that settles it. We have an option if meta federated and it goes to shit. Lemmy.world’s stance is correct. Let’s just see how this goes.
You don’t wait and see how it goes with these sorts of things. They will destroy the community before you can take action and it’ll be too late. They will do their best to destroy the fediverse and privatize it. They can’t buy it like they usually do with competition, so they’ll ooze their way in, contribute bullshit to the project, create new proprietary functionality that only works on their instance, convince everyone all the other instances are broken, and walk away with all the users. You don’t invite vampires into your house.
Do you realize that fediverse is not one single project? For example Lemmy and Mastodon has different implementation and developers. The only thing that connecting them is ActivityPub, which is owned by W3C, not the community. So basically Meta created their own implementation for Threads (so it’s already propertiary), and theoretically already able to pressure W3C to change the ActivityPub without even joining fediverse
How will they destroy it if they are literally only making it larger and more useable. The average normie today has no reason to create a mastadon account, because almost no one uses it. But if they can use a major social media platform, and use a federated free service like mastadon, then that makes mastadon much more valuable to them.
The fact that a social media service is objectively good doesn’t mean anyone is going to use it. Having backing from the biggest social media company in the world, might actually get people to use it.
I started swaying towards defederating after reading this article, maybe you’d like to take a look and see what you think? It argues much better than I ever could.
This is the classic size vs purity argument. Would it be better to have a large fediverse with corporate input or a small one without?