Lemmy has cleared some early hurdles to grow from near-zero to 60k DAUs in a month. I’ve enjoyed talking to people over the past month in a more friendly and intimate way than on that other site. The main communities are fun and viable but the niche ones are mostly empty. I run a niche hobby community and despite having a few hundred subscribers <5% have ever commented, <0.5% have posted. I think Lemmy needs to be perhaps 10x larger than it is now to be self-sustaining for niche communities.
Bite my shiny metal ass!
That fourth quote is legit quality.
It’s called a single-point of failure in Engineering.
For that instance, yes. For the whole of Lemmy, no. Everything else keeps on chugging along.
Good stuff 👍 Right now you’re using “can” and “should” which are somewhat vague. What happens if bots don’t do something they should?
Consider clarifying requirements using the following RFC-style language: “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL”.
why make users set a home instance? i can see a list of communities local to lemmy.world at https://lemmy.world/communities in the [Local] tab, and i can search my home instance at https://lemmy.world/search. i figured a search engine would span instances so users could find things across the lemmy-verse?
cleared cache, your url still gives me no results. in the top right the dropdown as “Ice Orchid”. I’m not sure what that is
Cool, how do I do it? https://www.search-lemmy.com/results?query=ultralight still returns “Found 0 results in 0.01 seconds”
very cool, thanks for the feedback and the site! my question is more along the lines of whether someone interested in a topic would be able to find my community without knowing it existed in the first place?
I created !ultralight@lemmy.world – searching for “ultralight” returns zero results on your site https://search-lemmy.com/results?query=ultralight&page=1 whereas searching for it at least returns something on each lemmy instance i’ve searched
🫘 bean strong 💪
a better solution is to decouple the query from individual api requests by adding a caching layer. we’ll get there eventually