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.
Why is this good news exactly? Doesn’t this just mean that people who want to see content from Threads will be driven to that app instead? Why not allow Lemmy users to see Threads content without them actually having to support Meta?
this article here gives a pretty good rundown of the likely intent of any sort of federated integration with any meta product, with examples of the same thing happening twice before with other technologies.
supporting it puts them in a position to “help” it… as they “help” they implement new closed source features… then drop support.
much of the growth that would occur during the “support/help” phase would be on their proprietary iteration and would not benefit the fediverse.
the trajectory would likely be co-opting the fediverse, obscuring their service from the fediverse, while building their services behind closed doors, and then dropping support.
they’re recognizing the fediverse as a reasonable competitor, and this is a move intended to kill it.
These are very good news, I just hope more instances beyond lemmy.ml do so too.
Why is this good news exactly? Doesn’t this just mean that people who want to see content from Threads will be driven to that app instead? Why not allow Lemmy users to see Threads content without them actually having to support Meta?
https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html
this article here gives a pretty good rundown of the likely intent of any sort of federated integration with any meta product, with examples of the same thing happening twice before with other technologies.
supporting it puts them in a position to “help” it… as they “help” they implement new closed source features… then drop support.
much of the growth that would occur during the “support/help” phase would be on their proprietary iteration and would not benefit the fediverse.
the trajectory would likely be co-opting the fediverse, obscuring their service from the fediverse, while building their services behind closed doors, and then dropping support.
they’re recognizing the fediverse as a reasonable competitor, and this is a move intended to kill it.