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.

you are viewing a single comment's thread
view the rest of the comments

[–] Anon518@sh.itjust.works 17 points 8 months ago (19 children)

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.

[–] Blaze@discuss.online 15 points 8 months ago (11 children)

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.

[–] Anon518@sh.itjust.works 8 points 8 months ago (10 children)

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).

[–] Blaze@discuss.online 16 points 8 months ago

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.

load more comments (9 replies)

load more comments (16 replies)