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.
Yea agree, not a fan of “Meta”. But I think limiting who can use federated networks kinda goes against the federated nature of such networks. What’s next, we’ll have a centralized blacklist of lemmy instances.
The nice part about federated networks is that if you disagree, you can just move instances. Nobody is bound to the will of the admins like with traditional centralized social media
The problem is when bad actors enter the situation. Meta has no interest in being a part of the community, they want to take it over and commercialize it.
This is mentioned in pretty much every thread but I haven’t seen anyone apply the theory to the fediverse. The second step is for threads to create features that lure people over from Lemmy (or activitypub). So are the people saying eee by extension saying they’ll move to threads from their current server because threads have a bigger and better development team?
they’ll move to threads because threads will be incompatible with the rest of fediverse (thread essentially defederate themself), and if most content is being posted in threads, they’ll move there (since they can’t access it from other instance)
this has happened before, such as
MSN messenger breaking compatibility with AOL IM (MSN wins since it got 95% market share)
MS Office doing obfuscation to their office file data to prevent FOSS editor like LibreOffice from rendering it correctly
I’ve been saying exactly this since the news dropped. I fully understand people being worried, but I haven’t seen a concrete pathway to damage that doesn’t involve meta-hating users moving over to a meta product.
Yea agree, not a fan of “Meta”. But I think limiting who can use federated networks kinda goes against the federated nature of such networks. What’s next, we’ll have a centralized blacklist of lemmy instances.
deleted by creator
The nice part about federated networks is that if you disagree, you can just move instances. Nobody is bound to the will of the admins like with traditional centralized social media
The problem is when bad actors enter the situation. Meta has no interest in being a part of the community, they want to take it over and commercialize it.
Let people decide on their own what they want to see.
And by commercializing it they would destroy it, since they will be promoting content that generates most clicks and everything will become agresive.
they did this specially prevent the Embrace, Extend, Extinguish strategy
This is mentioned in pretty much every thread but I haven’t seen anyone apply the theory to the fediverse. The second step is for threads to create features that lure people over from Lemmy (or activitypub). So are the people saying eee by extension saying they’ll move to threads from their current server because threads have a bigger and better development team?
they’ll move to threads because threads will be incompatible with the rest of fediverse (thread essentially defederate themself), and if most content is being posted in threads, they’ll move there (since they can’t access it from other instance)
this has happened before, such as
I’ve been saying exactly this since the news dropped. I fully understand people being worried, but I haven’t seen a concrete pathway to damage that doesn’t involve meta-hating users moving over to a meta product.