Looks like it. Does this mean that what you wrote here will only be visible in the sh.itjust.works instance until lemmyml is online again, or is it more resilient than that?
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.
Looks like it. Does this mean that what you wrote here will only be visible in the sh.itjust.works instance until lemmyml is online again, or is it more resilient than that?
That I’m not sure, this community and instance is separate but is a fork so lemmy.ml may have something to do with it.
I’m a bit new to all this so let me know if anything changes or if you still can’t post, I’ll find out what I can
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.