Anyone know anything?
You must log in or register to comment.
We had a <10 minute outage due to an issue with our database. I was able to quickly bring it back up, but the root cause is still under investigation.
Of course as soon as I post it, it’s back up ;-).
Thanks for your service.
how did you post it, when it was allegedly down?
I posted it from lemmy.world in the hopes it would federate to the other instances people were using besides lemm.ee and someone would see it.
but it has to federate from the source. if it were down at the moment, you wouldn’t be able to post it and other instances would have nowhere to download it from.
so you choosing to post this on lemm.ee to ask if lemm.ee is down is like using your gmail to send someone “hey, is your gmail down as well?”. if you can use the service, then it is not down. and if it is really down, you can’t use the same service to receive confirmation about the fact.
He didn’t post it to “https://lemm.ee/c/meta”, he posted it to https://lemmy.world/c/meta@lemm.ee, which is on lemmy.world but federates to other servers via lemm.ee.
are you saying the post is first created locally on that remote instance and then synced, if possible, to lemmee? are you sure about that? i am not really arguing, but that is not how i thought it works.
This is also why the beehaw defederation from lemmy.world was initially so confusing, because lemmy.world users thought they could still see and comment on beehaw posts and communities: What they were actually seeing was “lemmy.world/c/[community]@beehaw.org”, which took some time to desync and still let them post.
My understanding is that yes, it stores it locally first then synchs via the master.
I guess regular break. I assume lemm.ee doesn’t have redundancy.
