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

[–] can@sh.itjust.works 7 points 9 months ago (1 children)

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.

[–] Anon518@sh.itjust.works 1 points 9 months ago (1 children)

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.

[–] can@sh.itjust.works 4 points 9 months ago

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.