Technology

37573 readers

576 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

[email protected]

How to Kill a Decentralised Network (such as the Fediverse) (ploum.net)

submitted 1 year ago by [email protected] to c/[email protected]

4 comments fedilink hide all child comments

A warning and a perspective from an insider who has been through this before.

top 4 comments

sorted by: hot top controversial new old

[–] [email protected] 0 points 1 year ago (1 children)

I've never really understood the EEE argument here. XMPP was an open proptocol, Google embraced it and attracted users, then extended it and took those users away. But according to this article, Google didn't extinguish XMPP. It's still around and serving its niche community.

That's already the situation the fediverse is in. This is a niche community and there are already existing social media companies that the majority of internet users are on. If Facebook joins the fediverse, it brings billions of new users to the fediverse. If they then leave the fediverse, ActivityPub will still be here and all of us on the real fediverse will still be here, in a niche community. Everyone here has already chosen the fediverse despite it being a clunky, unpolished, niche network. How is EEE a relevant fear for the fediverse?

[–] [email protected] 0 points 1 year ago (1 children)

It's in the article but to paraphrase it:

When a large company takes an open protocol, embraces it using adding users to the network through heir platform, then extends it using proprietary means, they have full control over how the protocol runs in the network.

When the open standards are forced to make changes to be functional with the dominant proprietary app that is poorly (and sometimes incorrectly) documented, open source groups are constantly on the backfoot in order to maintain compatibility, and that makes it harder to compete on their own right.

A second example given is LibreOffice, whose documents are made to fit the XML standard by Microsoft, but there are quirks in their documented standard that if you follow it too closely it isn't formatted quite the same as the document produced in Microsoft Office, so they were pressured to effectively copy MS and deviate from the standards MS claims to follow.

[–] [email protected] 2 points 9 months ago (1 children)

Ironically XMPP is a counterexample to your argument. They made the switch to mandatory TLS even though GChat didn't.

[–] [email protected] 1 points 9 months ago

That's a neat fact!