I did a search from shitjustworks for “reddit die” and did not find https://lemmy.world/c/watchredditdie so I made https://sh.itjust.works/c/watchredditdie (unnecessarily). This should really not happen. When someone makes a community there should be a “ping” sent out to notify all other federated instances.
And from what I know, if I post to !sh.itjust.works/c/watchredditdie only users on sh.itjust.works will see the posts until other people from other instances randomly come across it somehow and subscribe? This really needs to be improved.
The devs actually talked about this in the AMA from a couple of days ago. Sounds like the current plan is to have all federating servers send their entire list of communities to each other on a regular basis.
The other thing that I think is worth mentioning is Lemmy Community Boost which is basically a bot that serves the same purpose.
https://boost.lemy.lol <- link to it, doesnt work for instances not connected to it like lemmy.world but theres still ~ 26 major ones
I’m surprised there was no issue filed for this already, maybe I just failed to find it, but I made a new issue
https://github.com/LemmyNet/lemmy/issues/4412
if anyone wants to give it a thumbs up reaction then the devs will know to prioritize it, and if you have any ideas you could leave a comment there
Edit: that was somewhat a duplicate of this issue
https://github.com/LemmyNet/lemmy/issues/2951
Give that one a thumbs up
The community you’re trying to subscribe to only has one post, and I believe that post may predate your instance spinning up.
It’s not really a good example of federation on Lemmy, because it doesn’t have content to federate.
Even your ping idea wouldn’t have worked here
Even your ping idea wouldn’t have worked here
Why not? When the person created the sub it would have sent out a ping to all federated instances, and thus when any account on a federated instance searches the keyword they would find that sub. IE: each instance would have a list of subs of all other federated instances. Like a sitemap.
Why not? When the person created the sub it would have sent out a ping to all federated instances
No it wouldn’t? Unless you mean that’s what you think it should do?
Anyway, there are tools to do this manually if you make a new community and want it to appear it popular all feeds.
Lemmyverse.net show both communities: https://lemmyverse.net/communities?query=watchreddit
It probably didn’t show up in the first place it only has 66 subscribers, and probably none on SJW.
About your second point, you indeed have to promote your community, using !newcommunities@lemmy.world, or related communities. This works quite well usually.
I will add that in your case, people knew about your community as you posted in other communities, but as discussed then, people seemed happy with the existing Reddit-focused communities.
This works quite well usually.
I definitely don’t agree. I think this is very problematic. I rely on all to find new communities. I don’t think one newcommunities sub is a valid replacement. It would suffer from the same issue – people would have to spam their post to every single instances’s newcommunities sub, which is ridiculous and not even viable.
Relying on !all to have your newly created community to reach most of the people could work, but using the Scaled sort as it wouldn’t have enough subscribers to push it using Hot or Active.
There is only one !newcommunities@lemmy.world, it has 15k subscribers, seems like a pretty good way to promote it.
I’m not even subscribed to that, and even if I was, and it was a default subscription for every new lemmy.world user, I don’t think it’s a good replacement for a functional search or an all that includes all posts from federated instances. I see lots of posts on all-hot with 0-5 upvotes so it seems fine if it actually showed all communities on federated instances (which it doesn’t).
But your solution would require every new instance to subscribe to every community in existence even if no users there care about certain ones. It’s innefficient.
How would you know no one cares if no one can even see them…
“Inefficient” doesn’t seem important since if there’s no content/activity there then it doesn’t use any resources.
Lemmy is pretty centralized in practice and people are on Lemmy.world, mostly.
It’s like hotmail or gmail. Default choice.
10k, which is around 25% of the whole Lemmy: https://fedidb.org/software/lemmy
It’s reasonable. Could be better, but could be worse (Gmail is probably much more prevalent in emails)
Yeah, the whole point of lemmy is to not be like that… so it definitely needs improvement.
Isn’t that intentional though? I don’t believe many instances, especially the small ones, can afford to federate every community. Sure, sometimes it can be a bit annoying but you can always check on lemmyverse.
It should show up in community search even if they’re not constantly pulling down every single post of those communities
As a middle-ground, I think it’s enough to only sync the community name and user count and maybe the description. More isn’t shown in the search anyway and those 3 data points shouldn’t take too much storage.
Syncing name solves the problem of communities not showing up. The problem with only being shown posts in a community someone on the instance has already subscribed to is more difficult, as you wrote.
