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.
if you're a registered user on a server, when you click [Communities], there you can see
You can subscribe to a community of any server which your server can federate with. The list of connected servers you can find via the /instances link at the bottom of the page.
There's an easy to use community search tool here https://browse.feddit.de/
If you've found a community you like to follow, translate the original URL to a federated URL You do this by putting the community URL of the original server in the search bar; e.g.
(This search functionality is available in the web interface, but not yet available in the Jerboa app)
The result will list the federated URL. A federated URL has the form:
https://<your server>/c/<community-id>@<other server>Visiting the federated link, and clicking [Subscribe] will make that community be federated to your server from now on. Your subscribed community will now also be listed under the [all] communities listing on your server.
Is there a newbie guide written up already somewhere? This is exactly the sort of things it needs, which should be linked to new signups.
Documentation etc can be found from their github page
https://github.com/LemmyNet/lemmy
Sure it can be found there, but pointing newbies to github would be too demanding.
At the bottom of every page, there you find a link to the documentation pages.
Sure, its a bit wordy... lacking in images with step by step instructions. If I had time I'd put something together with screenshots and figure out git and submit a pull request... maybe eventually.
Thank you, this is suitable for pointing people here who have this veryFAQ. Could you please add a line, that this search functionality is not yet available in the Jerboa app?
Ok, that works great. I do have another question though. When I want to view stuff, I go to lemmy.ml and view the stuff I'm subscribed to, but now I'm worried that that causes more overload on the lemmy.ml server. Is that true? Does it work that way?
You are subscribed to lemmy.ml, so anything you view from lemmy.ml including federated communities, will be served from there. Therefore: yes!
But anyway, that's how it is supposed to be, so your doing will just contribute to the beta-testing.
Ah ok I see, thanks for the reply.
Maybe a developer is better suited to answer that question. @[email protected] i'd assume there's a difference in load in the backend and load on the frontend.
No. I am on my own little single-user instance and I can follow, vote, post and reply anywhere from here. It's just a little awkward sometimes because you have to learn how to paste URLs in the search box, and until you subscribe there will be some missing content. But once you get past that, everything works.
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.
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.