Eh, kinda, but I see Lemmy as multiple centralized services, not actually decentralized. All of the content I view is stored on my instance, even if it was created elsewhere. This means it’s going to have issues scaling because there will be a ton of copies of everything throughout the fediverse.
A properly decentralized service won’t have so much duplication, it’ll have just enough redundancy so it’s not at risk of failure if too many nodes fail.
yuki2501@lemmy.world 11 months ago
Ah, I see your point.
If we want to be precise, we could say Lemmy is federated.
There’s centralized, federated,and distributed (e.g. DHTs).
On federated networks like Mastodon, I can send messages to my followers that I’m moving instances; after I finish moving, my followers can refollow me on the new instance.
I can export and import the people I finish and my block lists. I’m not sure if Lemmy has this functionality, but the point is that it’s still better than Reddit. A node daying doesn’t mean the end of the network.
The ideal would be to have a fully distributed version of Lemmy, where people could join virtual instances over a distributed architecture. Perhaps that will be possible one day, but for now Lemmy’s better than nothing.
sugar_in_your_tea@sh.itjust.works 11 months ago
Yup, I’m actually working on one distributed alternative, but I’m not sure if I’ll ever actually finish it.
And yeah, Lemmy is good in that it’s resilient to nodes dropping off, but it doesn’t solve the problem of costly hosting. I would assume the total cost of running Lemmy is way more expensive (perhaps an order of magnitude) than running Reddit, for the same number of users, because of how much duplication and communication there needs to be across instances.
So yeah, I’m here while lemmy is sustainable, but I’m worried about how it’ll scale.