(These instructions are for using Lemmy in a browser. If you are using an app, some steps may differ.)
How to Join Lemmy
To use Lemmy, you need to be a member of one instance from the list at https://join-lemmy.org/instances. You will still be able to see content from anywhere, but the instance you choose will determine:
- What URL you use to log in to Lemmy,
- What content shows on the homepage when you select “Local” or “All”,
- Who moderates your instance, and
- What rules you agree to when you sign up.
Choose an instance that matches your interests, language, and region. (If you want more information about an instance, you can tap its “Join” button, which will show you its current homepage in the main view and its description in the sidebar. You can also check the tables here and here.) Please avoid joining instances that are already crowded (1000+ users/month). If an instance gets overcrowded, it can start running slowly or experiencing downtime, so choosing an uncrowded instance will give both you and others a better Lemmy experience.
Once you have decided on an instance, tap its “Join” button to open it and then tap “Sign Up” in the upper-right corner. Fill out the form and wait for your account to be approved.
When your account is approved, log in and customize your profile and settings. If you change your language settings, select “Undetermined” in addition to any languages you speak so that you can still see posts and comments that are not tagged as being in any particular language.
How to Find and Subscribe to Communities
There are four ways to find communities through Lemmy:
-
To browse communities that others in your instance are already subscribed to, tap the “Communities” tab at the top of the page and choose the “All” scope. Tapping on a community name will open it through your instance.
-
To browse communities across all instances, visit https://browse.feddit.de/. Tapping on the community’s name will open it, but probably not through your instance (in which case the page will say that you are not logged in). Instead, follow these steps:
a. Copy the community’s URL or remote name. You can use the copy button next to the community name, you can open the community outside your instance and copy the URL from your address bar, or you can open the community outside your instance and copy the remote name (which will look like
!community@instance.tld) from the sidebar.b. In your instance, tap on the “🔍 Search” button in the upper toolbar.
c. Make sure that you have chosen “All” for each of the four filters: “Type”, “Scope”, “Community”, and “Creator”.
d. Paste the community’s URL or remote name into the search field and tap “Search”.
e. One of the results should be the community shown as an icon, a name, and a subscriber count. If you do not see it, or it is buried too deep in the search results, try changing “Scope” to “Local”. If that does not work, you may need to wait a bit and try again.
f. Tap on the community in the search results to open it in your instance.
-
If you want an experience similar to Reddit’s
r/all, visit https://lemmy.directory/home/data_type/Post/listing_type/All/sort/Hot/page/1, which aggregates from these communities as described here. As in Option 2, you can copy and search for a community’s URL to open it in your instance and subscribe to it. -
If you don’t see a community by browsing, subscribe to https://lemmy.ml/c/findacommunity and make a post about what you’re looking for.
Once a community is open in your instance, subscribe to it by tapping on the “Subscribe” button at the top of the sidebar. It will then appear in the “Subscribed” section of your “Communities” tab, and its posts will show on your home feeds.
Can’t find a community you’re looking for? If your instance allows it, you can create the community yourself by tapping “Create Community” in the upper toolbar.
How do I subscribe to a kbin community (or “magazine”)? I’ve tried entering the url in my instance like https://partizle.com/c/eve@kbin.social or searching like you’ve described but it can’t find the community. Is that because the instance I’m a member of (partizle) doesn’t federate with kbin?
AFAIK, that’s supposed to work, but it doesn’t for me either. Question raised here. We’ll see what people say.
(My instance does federate with the kbin instance for the magazine I tried to search for, so the problem must be something else. It looks like your instance federates with
kbin.socialat least.)
I can agree with it on lighthearted communities like memes, aww, etc. But for more serious topics everyone wants to see quality content, so please continue lurking on if you don’t have anything constructive to say!
That’s very helpful!
My 2cents: I would expand on “Please avoid joining instances that are already crowded”, new users might not know which ones they are.
I mean, from the perspective of redditors used to subs counting millions of users, no server on lemmy appears crowded, so I think actually giving numbers could help, something on the line of, please join servers with less than 1K users, if it makes any sense.
Or maybe actually suggesting specific names of instances that are more general purpose and not overcrowded yet, I personally joined lemmy only yesterday and I would have no idea of which they are, my only “parameter” was choosing a server with less than 500 users because I saw lemmy.ml saying they were overloaded, so I chose lemmy.world instead.
Other users may not pay that much attention so I believe the more specific the guide is on this, the better for everyone.
If this gets refined a bit with input from the community, I’d recommend adding it to the join-Lemmy repository and making it a part of the official join-Lemmy.org site so instance admins can point to a single location. Also makes it more likely users will see it when checking out Lemmy in the first place
Exactly this. The documentation repo is [here] (https://github.com/LemmyNet/lemmy-docs).
Got it. I’ll wait for a little more feedback and then try to figure out a PR.
PRs for join-lemmy.org now here and here. If I have time later, I’ll also look at a PR to expand what is already in the doc repo a bit.
