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.
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?
I don’t agree that they are solutions. The only proposed solutions are in the new github issue that someone created.
did you just want to bitch and argue?
I want lemmy to be better. I want it to be a viable alternative to reddit so people will leave that site.
