Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to [email protected].
Controversial idea: I think we should remove the "users per month" number on the instance list. It's confusing to newbies and encourages people to join a "large" instance when the number doesn't really correlate with actual server capacity.
Edit: And don't display the ones with 1 or fewer users. They are obviously private single user ones. If someone wants to start a public one, they'll be able to come get 2 or 3 others to join up and they'll pop onto the list.
Yea, when I looked for an instance to join, the activ user number discouraged me and I thought that these instances are basically dead. Maby just a baar without numbers just saying very activ - unactiv would be better.
Exactly. Or allow the instance owners to specify large, medium or small, depending on whether or not they have the capacity and resources for more people.
Same here. The numbers looked sooo low that I was thinking that everything is dead, but it is not. Though I did go to sopuli due to being Finnish but anyway.
I think we should add the following criteria to instances at the VERY TOP that are recommended to new users:
allowed list of instances...otherwise new users (eg from reddit) are not going to use lemmy because it won't match their expectations.
Personally, I was pretty disenchanted by my experience on lemmy when I first joined. I had to create accounts on like 5 different instances before I found one that worked (that's why I created the comparison table of lemmy instances).
Most new users won't have that perseverance. If, for example, they see there's no downvotes on the "recommended" instance, they'll probably give up and leave lemmy.
This critria is very well thought out, and explained. Thank you for making this list, it is how I found what instance to join.
I'm not sure I can add much value to the recommendations themselves, but I do believe the page needs to explain in relatively simply terms that that joining a particular instance isn't necessarily hindering access to any content, otherwise people will generally choose the most populous.
the page should also not show the users/month per instance
I agree. I know I initially joined lemmy.ml (before moving to a smaller instance) because of both these reasons. I felt I would miss out on content and that I should join the biggest community.
Those are solid requirements to be listed on joinlemmy.org and I would also add another one about moderation policies prohibiting racism, sexism, anti-LGBTQ+ bigotry, Islamophobia, etc. Otherwise, if a user joins an instance that the "official" page recommends and discovers it's racists / sexist / etc, they'll see it as a problem with #lemmy as a whole, as opposed to just one bad instance.
And as we've seen on Mastodon, if a Black user goes to a site where racism is tolerated and quickly encounters racist sh*t, they leave and tell their friends; ditto for trans, queer, Muslim, etc. users having bad initial experiences. Once that happens a bunch of times the reputation becomes hard to shake. Much better to steer people to sites where they're less likely to have a bad experience!
Good point
I think something to focus on would be a clean and easy-to-understand explanation of Lemmy and how the instances federate together.
This is still something Mastodon is struggling with when it comes to onboarding. Even for the technologically minded, it can be a steep curve and there are potentially a lot of other people who will balk at the walls of text and technical jargon.
Obviously, it all can't be fixed overnight, but I feel a lot can be done to improve the onboarding for users without overloading them with information.
Maybe a small step-by-step wizard-style system to help someone find and instance and explain Lemmy in bite-sized chunks of info would be a good first step.
Professionally I'm a UX Designer and Business Design consultant and I'd love to be able to lend expertise to the project!
I literally only understood this after getting an account on one instance, and realizing I still saw posts and could interact with them from other instances. And I'm a web developer with pretty deep technical knowledge.
A simple "choose your home, see and interact with content from everywhere" would go a long way.
If I hadn't already settled into Mastodon I would have been super lost, still was to a degree...
And Join-Lemmy seemed to be pushing me to Lemmygrad, which is cute, but I wanted something more general and had only heard of beehaw through other people discussing Lemmy
The iconography on posts is pretty confusing too, needs some good labeling "Open in Home Instance" & "Open in Original Instance" would help
Contributions welcome, all of our code is open source.
I’m very new to contributing in that kind of style, git and code is scary to me; I’m more here for research, recommendations and element design.
What would be the best way to contribute non-coding expertise? I always feel like I’m imposing in these kind of spaces when I want to offer advice and insights as they come from such a different sphere
1,000,000%! I grew up on the internet, love tech, etc, but the onboarding process is confusing.
I'll be submitting my instance to be considered to the recommended list. I've thrown a nice amount of resources at my lemmy instance and i'm pretty excited to see how it will handle the extra load that is expected!
Perfect, can you make a pull request?
Got this completed! Looks like the merge request was accepted and merged into the main already. Thanks for giving the heads up.
Will have this done before the end of the day! I will be adding support for the French language as well to accommodate french speaking individuals as well!
Thank you for your work btw. Love the domain name.
I think my server lemmy.world would qualify :-)
Great, can you make a pull request?
Ohh, never done that before. Should I create a fork, edit the file, and then submit as PR?
(yes)
Lemmy try that.
OK I submitted the PR.
Our server on slrpnk.net can very likely take some more users, but I am pretty new to hosting Lemmy and it's currently only me that has some time to managing the server and approve applications.
So maybe better not to add it directly to the recommended instances list.
I'm happy for people to join my instance vlemmy.net, its got plenty of resources on dedicated hardware so I'm sure it could help out in case of an influx.
The admin team needs to be prepared for a large influx of users, both in terms of hardware and moderation
Reddit has almost half a billion users, so until there is horizontal scaling I would argue no instance is ready.
One criterion i would add is economic viability, Lets look at beehaw, it has about 1000 monthly active users and according to opencollective got about 1000$ this month (for some reason the opencollective page of lemmy can't show this stat), that puts him at the ARPU (active revenue per user) of about 1$ a user which is similar to reddit that has ARPU of about $1.02 (and was much lower in 2021, about 0.5$).
There is horizontal scaling through federation. Even if lemmy.ml, beehaw.org and lemmy.one go down, users can still join instances like sh.itjust.works. The instance list on join-lemmy.org works as a load balancer.
This just the emphasizes how crucial it is for join-lemmy to succeed. If your load balancing hinges on the onboarding experience then it must at the top of priorities, though I'm sure you're aware and would like ideas instead.
I wonder if the site could simply offer one at random from the list of recommended ones, offer it in a big frame with a "sign up" button.
Below it could something along the lines of "Any of these will also do: they all connect to eachother anyway." And list the rest of recommended instances.
Below that it would have a "show more" button that would reveal the rest of the instances.
I also feel like the site could start with this dumbed down instance picker. First with an introduction and then the recommended instances. The vast majority joins and the ones who want to run an instance will likely join one first anyway. Skip the two buttons step.
Is it possible to have users automatically distributed to different places to help with scaling and load, and at the same time be able to select which "rules/content of that instance" they'd like to be part of without it having to be dependent as it is now on which instance they join?
Right now everything appears to be entirely tied to the instance joined when it comes to accounts, rules, and most importantly load. Wonder if it is possible to have the rules/content portion separated from all that in the future.
So to try it put more simply have in the future specific instances behaving more like joining a subreddit that have different topics and moderation instead of having everything tied the instance where the account was created.
If your goal were wider adoption, having a big "sign up" button (with the server name on/next to it) that links to a random "recommended" general instance could be best. Put a "sign up on a different instance" button next to it, and a list of instances below that.
Of course - that's IF it's your goal.
I think Mastodon does this, but just a static link to mastodon.social instead of randomly rotating it.
Edit: that's what they do on the app - but not joinmastodon.org
Instances have different topics and moderation, so it should be left to each person which one they prefer to join.
And it would be - no choice is being removed. It's more of a "I'm not sure what all this is... I just want to join lemmy" button. But I know that perhaps that's not completely in line with the core/original culture of the Fediverse. But a lot of people have incorrect assumptions on what federation is, if indeed they know anything about it at all. This leads to decision paralysis and confusion. People overthink which instance to join, at least among the open "general" instances.
And it would need to be explicitly opt-in for each server.... I don't think BeeHaw would be open to this for example.
I agree with your way of thinking. I believe a lot of people would be open to recreating an account on an instance that vibes with them more once they understand how it all works too.
I did that about 3 or 4 times already and only a couple of them were by accident!
If your goal were wider adoption, having a big "sign up" button (with the server name on/next to it) that links to a random "recommended" general instance could be best. Put a "sign up on a different instance" button next to it, and a list of instances below that.
I think this is an excellent idea
Ideally the recommended instances section wouldn't be static. It would put a different instance in prime position for each user that visits... a poor mans load balancing I guess.
The order of recommended instances is randomized, there is a different one at the top each time you reload.
That works.. hadn't realised it was randomized with only two recommended.
I was trying to edit my comment and accidentally deleted it! D'oh!
If your goal were wider adoption, having a big "sign up" button that links to a random "recommended" general instance could be best (with the url/name clearly on the button). Put a "sign up on a different instance" button next to it, and a list of instances below that.
Of course - that's IF it's your goal.
I think Mastodon does this, but just a static link to mastodon.social instead of randomly rotating it.
Edit: that's what they do on the app - but not joinmastodon.org
FYI you can restore deleted comments by clicking the delete icon again.