I made a text-and-images version of this guide:
Added to the article. Thanks for the suggestion :)
You should ask in /c/mlemapp
And if it’s a bug, please report it on GitHub
Edit: A quick search on github issues brought this up
I made a text-and-images version of this guide:
The only thing I need to improve this article is a short video demonstration showing how to find and add remote lemmy communities
Are there any video producers on Lemmy that can help? You’ll easily get thousands unique views per day if you make a short “Guide to Lemmy” video :)
Thanks! Please also let me know if you’re aware of any other lemmy communities (for video content creators) where we can cross-post this to <3
I’m actually very surprised how high the uptime is on most of these instances.
The awesome-lemmy-instances
repo on GitHub displays uptime:
This list may help newcomers:
At what point do you plan to close this instance to new users?
See this list of “Privacy-Conscious Email Services”
Honestly I’m not sure I’ll stick to lemmy if the amount of content doesn’t grow. And I’m sure I’m not alone. I’m here for news, and there’s very little coverage of world events on lemmy (though that has already noticeably improved as our userbase grows).
I do want lemmy to grow, but not for growth’s sake. I want it to grow so the content (news article submissions and quality comments about those articles) grows.
If an instance (eg Hexbear) wants to deviate from this, that’s fine. That’s what the Fediverse is all about :) But we shouldn’t recommend those instances to new users as it will cause new user attrition.
That’s not going to happen automatically, but we can manually remove instances that go down.
I only know of one site that monitors uptime of lemmy instances:
They do have an API, but I’m not sure yet how to query it (help would be appreciated!)
I found this site that tracks uptime of lemmy services. They have an API that helps you construct a query in the WUI.
Or you can use cURL to get the uptime of all known lemmy instances
curl 'https://api.fediverse.observer/' -X POST -H 'Accept: */*' -H 'Accept-Language: en-US,en;q=0.5' -H 'Content-Type: application/json' --data-raw '{"query":"query{\n nodes (softwarename: \"lemmy\") {\ndomain uptime_alltime\n }\n}\n"}'
See also:
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.
Instances aren’t added manually. They’re discovered using lemmy-stats-crawler.
As long as your instance is federating, active, and the API is reachable then it will make it onto the list.
Edit: It looks like your instance’s API isn’t reachable, which may be why it’s missing:
Please fix the availability of your instance’s API.
Ok, thanks. I see the i18n text changes were here:
18n is probably good, but it does really make it harder for folks to collaborate. It totally stopped me from contributing. Thank you for your help <3
Suddenly my server started getting thousands of requests per minute and my varnish cache hit rate jumped to 99%. Thank god for varnish!
Looks like the reddit blackout is #1 on the frontpage of hackernews, and this article is #2.
I actually posted this article to hackernews, but I never got a single upvote. This isn’t my first time getting on the frontpage of hackernews, but it always happens when someone else reposts my link.
Can anyone tell me how the fuck hackernews’ algorithm works to where I can’t ever get traction but someone else does after me?