Discover the magic of the internet at Imgur, a community powered entertainment destination. Lift your spirits with funny jokes, trending memes, entertaining gifs, inspiring stories, viral videos, and so much more from users like Arwagollon.
What causes this and is there anything I can do about it?
So I believe how it works is that if someone subscribes to a remote community, the feeds should stay relatively fresh (depends how often the remote instance sends content out to federated subscribers, perhaps that hits a rate-limit on the major instance?) but if nobody is subscribed it will only refresh whenever someone searches for it.
Edit: In regards to your image, comments only show up after a post has already federated. If the comment was made before that, they won’t show unless their original link is put into search on the home instance.
From the FAQ I found somewhere: Discovering: Hey I can’t see [x] newly started community on my server! I can’t find [y] popular community from my small server! What gives? (IMPORTANT)
Some communities might not appear from All, until any logged in user of that server searches for it in the lemmy-ui (web) searchbar.
For example, to “discover” coolcommunity @coolserver.com from instance yourlemmy.server, you would type “[email protected]” within yourlemmy.server’s search bar and wait 10 seconds. Ensure that community has at least one post that can sync, and even then it may take a while to actually appear in some cases. If you set the filter to “communities”, enter the community in that format and press search and nothing happens, that means it is discovered. If it says No results, try again after 10 seconds, check that you have spelled and formatted correctly.
That causes your server to “discover” it and will start syncing posts and be searchable and also available on apps like Jerboa. Only after it is discovered can you use a URL link to it in this format: https://yourlemmy.server/c/[email protected] I coined the term discovering here but in essence it’s initiating federation and post-fetching from that community.
So I believe how it works is that if someone subscribes to a remote community, the feeds should stay relatively fresh (depends how often the remote instance sends content out to federated subscribers, perhaps that hits a rate-limit on the major instance?) but if nobody is subscribed it will only refresh whenever someone searches for it.
Edit: In regards to your image, comments only show up after a post has already federated. If the comment was made before that, they won’t show unless their original link is put into search on the home instance.
From the FAQ I found somewhere: Discovering: Hey I can’t see [x] newly started community on my server! I can’t find [y] popular community from my small server! What gives? (IMPORTANT)
Some communities might not appear from All, until any logged in user of that server searches for it in the lemmy-ui (web) searchbar.
For example, to “discover” coolcommunity @coolserver.com from instance yourlemmy.server, you would type “[email protected]” within yourlemmy.server’s search bar and wait 10 seconds. Ensure that community has at least one post that can sync, and even then it may take a while to actually appear in some cases. If you set the filter to “communities”, enter the community in that format and press search and nothing happens, that means it is discovered. If it says No results, try again after 10 seconds, check that you have spelled and formatted correctly.
That causes your server to “discover” it and will start syncing posts and be searchable and also available on apps like Jerboa. Only after it is discovered can you use a URL link to it in this format: https://yourlemmy.server/c/[email protected] I coined the term discovering here but in essence it’s initiating federation and post-fetching from that community.