in short: we tried to fix a Lemmy issue that started on 9/13 and is causing or has caused problems with apps for the software. we're aware of basically all of them besides Sync exhibiting some sort of problematic behavior since this issue arose. however: attempting to fix this issue on our side of things did not go well.

i am not qualified to make a formal write-up of the exact mechanism of what went wrong here--and in this case the mechanism isn't really important for your informational purposes, although @Penguincoder@beehaw.org can elaborate as needed--but basically we made a fix that seemed fine in testing and was not fine when actually applied. when it became obvious something was wrong, we tried restoring literally everything but the database. that, unfortunately, did not work, so eventually we just pulled the trigger on restoring from a backup. this has lost at least some posts, but probably no more than 8 hours of them by our estimation.

hopefully this will not happen again, either upstream or on our side of things.

you are viewing a single comment's thread
view the rest of the comments

[–] MJBrune@beehaw.org 1 points 1 year ago (2 children)

fediverse is an API in which these services can share information. That's how Mastodon users and Kbin users can comment on Lemmy posts. These services all federate together through federation lists. Making a new API for this would be pointless.

The fediverse is supposed to allow for more open and transformable platforms but in reality, what it's doing is making groups of people between these services that fit into their own echo chambers. I predict in the future people are going to start sharing allow/deny lists of groups and join mini federations that will consolidate more and more power in the fediverse. New instances will have to be adopted into a shared list of allowed instances. Like bitcoin, the fediverse promises to fix something but will likely make it worse.