285
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 08 Jul 2023
285 points (100.0% liked)
Technology
37742 readers
494 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
This article is “How to Kill a Decentralised Network (such as the Fediverse)” and it tells you how Googled killed a federated protocol for instant messaging, XMPP, by the Embrace, Extend, Extinguish process.
I don't see that connection. XMPP wasn't big before and it wasn't big after. XMPP is still not big. But it also still exists and is still used.
I think what Google achieved with the usage of XMPP was not some EEE tactics, just as I don't see Threads extinguishing ActivityPub. I think they use open standards as a way to calm regulatory bodies. "Hey look, we have no evil in mind, we use open standards and allow others to play along." Then once they are out of the spotlight, they can slowly defederate again and be a proprietary beast.
Users who leave other fediverse instances to join Threads (or back then Talk) would have also left if they never federated in the first place, simply because they have the bigger network and all their friends are there. The difference is, that they had a relatively brief period of time where you could actually keep communicating with friends without leaving the fediverse.