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

[–] Levsgetso@lemmy.zip 22 points 9 months ago (2 children)

Isn’t that intentional though? I don’t believe many instances, especially the small ones, can afford to federate every community. Sure, sometimes it can be a bit annoying but you can always check on lemmyverse.

[–] PeriodicallyPedantic@lemmy.ca 20 points 9 months ago (2 children)

It should show up in community search even if they're not constantly pulling down every single post of those communities

[–] Levsgetso@lemmy.zip 6 points 9 months ago

Fair enough

[–] intensely_human@lemm.ee 6 points 9 months ago

And just the instance metadata is tiny

[–] Chewy7324@discuss.tchncs.de 10 points 9 months ago (1 children)

As a middle-ground, I think it's enough to only sync the community name and user count and maybe the description. More isn't shown in the search anyway and those 3 data points shouldn't take too much storage.

Syncing name solves the problem of communities not showing up. The problem with only being shown posts in a community someone on the instance has already subscribed to is more difficult, as you wrote.

[–] threelonmusketeers@sh.itjust.works 3 points 9 months ago* (last edited 9 months ago)

Descriptions can be of arbitrary length. Date and time of the most recent activity might be more realistic and useful.