Fediverse

42 readers

5 users here now

This magazine is dedicated to discussions on the federated social networking ecosystem, which includes decentralized and open-source social media platforms. Whether you are a user, developer, or simply interested in the concept of decentralized social media, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as the benefits and challenges of decentralized social media, new and existing federated platforms, and more. From the latest developments and trends to ethical considerations and the future of federated social media, this category covers a wide range of topics related to the Fediverse.

founded 2 years ago

122

If ActivityPub can't survive Meta, it was never going to succeed in the first place (kbin.social)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

91 comments fedilink hide all child comments

Corporations don't just sit out on new technologies, and no matter how hard you try you can't force them to. Defederating from Meta's new project preemptively is naive, and will not do much of anything.

Protocols are going to be adopted by corporations, whether we like it or not. SMTP, LDAP, HTTP, IP and 802.11 are all examples of that. If it ends up that meta is able to destroy the fediverse simply by joining it, that is a design flaw on OUR end. Something would then clearly need to be different in order to prevent future abuse of the protocol.

FOSS is propped up by corporations. By for profit corporations. If you want to stop those corporations from killing projects, you put safety guards up to make sure that doesn't happen. You don't just shut them out and put your head in the sand.

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

[–] [email protected] 8 points 1 year ago* (last edited 1 year ago)

This is a misunderstanding of the issue. ActivityPub the standard will of course survive the extension of use to Meta. ActivityPub is just a protocol. There are reasonable concerns about the distortion to the priorities and focus of the projects development long term if Meta gets more involved but those are not unresolvable, and have been seen in other open source projects when big business gets involved.

People's objections are also due to how federating with Meta's software, content and commercial priorities will distort the existing communities in Fediverse/Federation/Threadiverse.

While the technology allows the Fediverse to exist, one federation is not the be all and end all of the fediverse; it is understandable that existing parts of the Fediverse might not want to federate with Meta. There can be multiple federations within the fediverse; it doesn't have to be one joined up mass and it's not likely it's going to be one single complete federation long term. People will naturally form interconnected communities around different ethoses, priorities etc. I think there will likely be one big "primary" part of the fediverse just due to shear size and mass of content; but it doesn't follow that it needs to be linked with Meta's implemenation nor that Meta's implementation would damage a separate fediverse. That is what people are pushing against - they do now want the main threadiverse or other elements of the fediverse to be subsumed and lose it's identity due to being swamped by Meta's social media platforms.

It's about the separation between the fediverse as a technological solution and the fediverse as a philosophical solution.