Technology

37627 readers

22 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

TheRtRevKaiser@kbin.social

260

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

submitted 1 year ago by Niello@kbin.social to c/technology

89 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] 0x1C3B00DA@lemmy.ml 1 points 1 year ago (1 children)

Yes I read that and explained why I don't think its relevant. Facebook can't slow down progress on the fediverse because:

progress is already slow. The fediverse has been in development for 15 years and still is a clunky, niche network and likely will always be less polished than large corporate networks.
Every developer on the fediverse is aware of the EEE playbook and next to none of them will try to remain compatible with any corporate extensions.

[–] Ropianos@feddit.de 2 points 1 year ago (1 children)

What do you mean? Progress is already slow so any additional slow down will seriously harm the fediverse precisely because of the limited resources IMHO.
I'm not quite as optimistic as you but yeah, I don't think it will be easy for Facebook and if they misjudge it they will end up making a competitor stronger by bringing more attention to it.

[–] 0x1C3B00DA@lemmy.ml 1 points 1 year ago (1 children)

But #1 is predicated on #2. If developers are aware of the risk of EEE, then they won't try to remain compatible with Meta extensions, which means development of the open AP ecosystem will continue at the same pace.

[–] Ropianos@feddit.de 1 points 1 year ago

Okay, sure. Still a bit skeptical about point 2 but we will see.