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.
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: !watchredditdie@lemmy.world, !watchredditdie@sh.itjust.works
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).
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.
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.
This. I want to be able to see every community of every instance i‘m federated with with post and sub count. Thats a laughable amount of data. This would boost subscriptions by insane amounts.
The number of subscribers being completely different depending on which instance you search from is really weird/bad too IMO.
This is fixed in version 0.19.3, hopefully your instance will update soon
Yes. Lemmy is deep in “good enough” territory. It mostly works for most people, much of the time. But if you stray outside of the main use cases, you’re gonna be disappointed.
