this post was submitted on 20 Jun 2023
207 points (100.0% liked)
Fediverse
287 readers
1 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
One of my concerns is that a big corp adopts it, makes it popular and contributes to it so much that they might as well own it. For example, imagine a company like Microsoft or Google ends up making an instance and their own software like Lemmy or kbin. Since they have the money to develop, refine it and advertise, it could gain mainstream popularity and people start creating communities and content inside Microsoft's or Google's instance. If it grows to a point where 80%-95% of the content generated is from that single instance then what happens then? Sure we can still create accounts on Lemmy.world or kbin.social and see that content but we're relying on the content on their instance. If they decide to defederate then we lose all that content so then you'll have to create an account with them to access it (just like Reddit). And if we don't we'll have to start over again, at least when it comes to content.
I'm still figuring out how all of this works so I might be wrong.
You've almost got it. The thing is when you view content posted to another instance you're not actually accessing the other instances, you're viewing a copy of those posts stored on your instance. Federation works by distributing copies to all federated instances.
So if a big company like Google did as you said, and then suddenly defederated from everyone, you wouldn't actually lose any of the content. All those posts up until the point of defederation would still be stored on every instance they were previously federated with. You would just stop getting new posts from that point forward.
There's a bit of weirdness though, since the "true" post on the hosting instance is what handles syncing/distributing copies. So any new posts you made to those communities or comments on those posts couldn't be copied back to the true post and then spread to the other instances. So everyone ends up with a desynced "ghost community". So while you might see new posts/comments in those ghost communities from people on your instance, they don't get synced to any other instance. (If you're on an instance that beehaw.org recently defederated from, you can see that in action right now.)
So at the very least, the content would still be backed up, but you're right in that people would need to "start over" and create new communities with new mods and new posts if they wanted the content to be federated. We just wouldn't lose the old content.
This is basically correct, they could also create a scheme where they charge for federation and introduce it on short notice, similar to what reddit and Twitter did with their api. I think the best way to prevent this is to not federate with corpos, especially when they've been bad actors in other ecosystems like fb and Google.