PeleSpirit@lemmy.world 1 year ago
I think right now it’s like you can communicate but you have to call or check up on each other often, especially if it’s niche. When you put in a web address in your search to find another community from another instance, they’re calling to see if you can get the number. Once you subscribe, it all depends on how you have the time specified and if they have called into to check with all the other instances. That’s for Lemmy to Lemmy, not Lemmy to Kbin which is probably worse. Please anyone correct me if I"m wrong, but that’s my understanding.
r00ty@kbin.life 1 year ago
Half right. I can talk from kbin->kbin/lemmy. Since that is what I'm doing here.
Yep, when you search for a remote community your instance will connect to the remote one to look for that community/group/user. If it finds it, it will show all the info about it. Kbin will also automatically subscribe you to it.
Once the remote instance has your subscription, from that moment on it will send all interactions with that community to your instance. This results in some confusing things happening. You'll see a lot of new stuff start to appear, but sometimes old stuff, but not all old stuff. The reason for this is, if someone on another instance comments or likes a comment on old content, your local instance will not be able to action that like (or at least show it) or comment without getting the comments above that one up to the post. Which is why you'll see a mix of old and new content, but never all of it.
PeleSpirit@lemmy.world 1 year ago
Thank you for explaining it to me, I finally get it. That’s why a 3 year old post was showing up a couple of days ago and then I liked it not seeing the date, then a whole bunch of the same post started showing up. My like must have sent it to someone else to start a cycle of bringing a 3 year old post back to life.
r00ty@kbin.life 1 year ago
Yes, that's likely exactly what happened.