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.
Nope. You can subscribe/post/comment on any community on any instance. There is one small seam though: if you’re the first person to subscribe from your instance, you need to put in the full URL of the community (https://lemmy.ml/c/gaming, for example) to pull it into your instance.
After that, everybody on the same instance as you will see it when searching for communities just like it was local.
EDIT: Oh, forgot to mention: make sure the search is set to “All”, not “Communities” when you do this.
Thank you :3
Does accessing communities from other instances count as “using other instances” (i.e. will lemmy.ml still be get overloaded eventually)?
Also, can I still access these communities through lemmy.ml if it is down?
Technically yes, but it’s not even vaguely in the same ballpark. If I’ve understood the devs talking about the optimization issues (I could be wrong! Just my limited understanding) the big performance hit is in the local feed. That means being on another instance takes a gigantic amount of the load off, even if you’re still accessing the same community.
If lemmy.ml is down, so are all the communities hosted there. All communities not on lemmy.ml would still be up.
Correct the performance problem now is all from local users (visiting lemmy.ml in their browser or app).
If lemmy.ml goes down, other instances still have full mirrors of them. Users there can interact with their local mirror as usual, and other users can see those interactions. However these would not be federated to other instances (lemmy.ml is responsible for announcing community posts to followers). However federated actions are retried a few times so it might federate later.