This site is currently struggling to handle the amount of new users. I have already upgraded the server, but it will go down regardless if half of Reddit tries to join.
However Lemmy is federated software, meaning you can interact seamlessly with communities on other instances like beehaw.org or lemmy.one. The documentation explains in more detail how this works. Use the instance list to find one where you can register. Then use the Community Browser to find interesting communities. Paste the community url into the search field to follow it.
You can help other Reddit refugees by inviting them to the same Lemmy instance where you joined. This way we can spread the load across many different servers. And users with similar interests will end up together on the same instances. Others on the same instance can also automatically see posts from all the communities that you follow.
Edit: If you moderate a large subreddit, do not link your users directly to lemmy.ml in your announcements. That way the server will only go down sooner.
Well yeah, point taken that replicating everything everywhere and forever might be impossible. But I do believe at a minimum my identity should be portable and accessing Fedi (ie. in microblogging: posting and viewing a feed of the latest posts of my follows) should be decoupled from which instance I pick to access the Fediverse.
I don’t particularly like how owners of instances which grew are now essentially locked in to having to spend 100s or 1000s of dollars a month keeping their now expensive instances running and providing service. This is a bad place to be for a platform ran by volunteers. Letting instance owners scale their service down as well as up would be ideal. But this requires at least decentralized identity, and at best some form of content hosting redundancy…
It’s easy to say the current architecture of Fedi works when it’s still small. Your instance has 139 users… That’s not intended as a slight. Hosting instances is good and I applaud you for it! But I wish it were easier to more equally share the load once the platform becomes more popular.
Is there any group of devs that work on this issue that you know of? I’d be interested in looking into it.
No. And I think it’s a really hard problem. poVoq was right to call me out on full replication being a bad move, because duplicating all content on every server is obviously inefficient. But a solution in-between, with decentralization and redundancy, is probably a very complex challenge. Doesn’t seem impossible, but very complex network protocols rarely seem to succeed.
Edit: Sorry I was still thinking about some fabled perfect protocol. But if you’re looking into decentralized identifiers, W3 is working on one approach. It’s not something I have seen used anywhere or integrated with ActivityPub yet, but that could be the future I’m hoping for. Probably.
It almost sounds like you’re describing RAID 5 of content across fediverse servers.
Something like that. But also with fully decentralized identity. So all content is signed by a keypair which is local to the user, and can be used to access Fedi through arbitrary instances. Probably I am too wishful.
I like the idea of decentralizing identity. One of the oddest things about the current fediverse is how closely tied accounts are to servers that host specific content. From the server’s perspective it would be like everything’s posted anonymously except all the messages are pgp signed.
But how would the system handle user customization settings? Things like blocked users or subscribed topics. Would that all need to be stored locally in your browser and parsed by the arbitrary instance you’re using?
And what if some instances want to refuse hosting certain content on the network. Maybe there’s some way defederating instances could account for that.
I could envision a 2nd class of server, running something like OAuth/OIDC, which handles the authentication into any Lemmy instance (or better yet, any ActivityPub based instance).
This server would also be self-hostable, and provide only authentication services, so it would be rather lightweight. But would help reduce the load on the content servers.
I feel like for decentralized identity maybe a page could be taken out of Blockchain. Ethereum ledger is duplicated in its entirety on every host, and there are L2s that help spread the load but roll up to the L1. If identity could be attached to something like that, each person has a key to identify themselves. Identity I think would be best separated from all content related to the identity, the user could choose a server to host that data, as well as back it up with like a shared user data backup agreement between a few servers in case one dies. It’d be very similar to raid but the data only needs to be on 2-3 servers. I suppose community data could be the same. I can envision when a new server joins the federation, it could be auto assigned to share with 2-3 similarly sized communities with algorithms making sure there aren’t any closed groups of sharing (a->b&c, b->a&c, c->a&b) wouldn’t ever want that. They all seems to be the most reasonable solution in my head.