Federation with communities on other instances
Federation with communities on other instances
Yesterday I made a post in the football community located on lemmy.world (https://lemmy.world/c/football). Now when you look at the post from here discuss.tchncs.de/c/[email protected] it has 0 comments and 1 upvote:
https://discuss.tchncs.de/post/183785
Whereas it actually has 1 comment and 4 upvotes on the Remote instance:
https://lemmy.world/post/343210
Because on discuss.tchncs.de the comment doesn’t show up, I obviously get no notification nor can I respond.
Anyone got an idea?
You're viewing a single thread.
Comments don't show up until there's a user from the local instance subscribing to the remote instance. You need just one subscriber though.
Think of it like email subscription where you get emails from the moment you subbed.
On Mastodon it is possible to search for a comment's url and have it fetched manually, but here that doesn't seem to be the case yet, although it surely will be implemented.
Thanks for the clarification. Could get complicated, especially with smaller remote instances…
The good thing is that it can be automated. On the flip side it works that way to reduce the load. Makes no sense in getting all comments if no one is going to read them. But I agree that once a user clicks on a thread, comments need to be fetched from the remote server.
Hm, I have to ask again: initially thought I had to follow a user on the remote instance, similar to mastodon. But is that possible in Lemmy? See it only in kbin. Because the remote community in question I have subscribed to before posting.
No. You can only follow communities but that is enough.
Please check something. Make sure your community is set AT LEAST to both English and Undetermined languages.
In your user settings make sure you have selected at least English and Undetermined.
This could be what's happening and why you can't see the comment.
Ok, got it. In this case it was something else: on my local instance it showed that I subscribed to the community, but on the community page itself it was stuck in status pending. Subscribed again now, hopefully this solves the problem.
—
Oh, I see. That makes sense. That would explain why your instance didn't receive the comments.