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.
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).
There is a security issue by allowing automatic federation with any federated instance: an attacker could just create a huge number of communities, with a large number of posts, exhausting the resources of small instances.
That’s what I guess it the main reason why it works like it does now: the server only gets the content if someone is interested.
Folks have given you a half dozen solutions here and your answer is consistently dismissive.
Did you want your problem solved or did you just want to bitch and argue?
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.
I agree community discovery could be improved but let’s say I had an instance with 200 users and none speak German. Would it make sense for my instance to still pull everything from the German language communities and clutter an All feed where no one can read it? Or is it better to wait for a German speaking user to register and actively choose to participate in those communities before federation begins?
I think the way federation works as a whole would have to be reworked for your solution. Simply federating with all communities not on your black list isn’t the best solution.
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.
