Basically, during the short stints where lemmy.ml is actually able to function, it sends out all posts & comments. Those posts & comments are cached on every subscribed server.
This means that sh.itjust.works can interact with !lemmy@lemmy.ml, post, comment, vote, but none of it is synced back with lemmy.ml until it recovers again. We’re communicating on the cached version on sh.itjust.works right now.
I run my own server, I wonder which server sent me this comment chain, lemmy.ml or sh.itjust.works. Fancy backup federating would be cool, but I’m pretty sure just lemmy.ml sent me this data.
Basically, during the short stints where lemmy.ml is actually able to function, it sends out all posts & comments. Those posts & comments are cached on every subscribed server.
This means that sh.itjust.works can interact with !lemmy@lemmy.ml, post, comment, vote, but none of it is synced back with lemmy.ml until it recovers again. We’re communicating on the cached version on sh.itjust.works right now.
I run my own server, I wonder which server sent me this comment chain, lemmy.ml or sh.itjust.works. Fancy backup federating would be cool, but I’m pretty sure just lemmy.ml sent me this data.
Yes, lemmy.ml is in charge of that. Other instances run their own caches of that content, but only for users on that instance.