there is indeed a cutoff. there is exponential delay for retrying and at some point lemmy will stop trying until it sees the instance as active again.

there is also a scheduled task running once a week that will delete local activities older than a week. downtimes of a day or two can generally be easily recovered from, depending on latency it can take a lot more time though. if an instance is down for an extended time it shouldn't expect to still get activities from the entire time it was offline.

downtime should not result in missing content when the sending instance is lemmy 0.19.0 or newer. 0.19.0 introduced a persistent federation queue in lemmy, which means it will retry sending the same stuff until the instance is available. depending on the type of down, it can also be possible that there is a misconfiguration (e.g. "wrong" http status code on a maintenance page) that could make the sending instance think it was successfully sent. if the sending instance was unreachable (timeout) or throwing http 5xx errors, everything should be preserved.

we are planning to post an announcement about the current situation with lemmy updates and our future plans in the coming days, stay tuned for that. you can find some info in my comment history already if you are curious.

we're currently aware of delayed federation from lemmy.ml towards lemmy.world and still working identifying the root cause - see https://lemmy.world/post/22196027 (still needs updating that it's happening again).

aussie.zone has been about 6 weeks behind lemmy.world for a few weeks i think at this point, which at least means they're no longer losing activities, but it's still taking ages to reduce the lag.

i don't know what issue there might be with discuss.online right now, but for startrek.website the explanation is rather simple. as you can see in the sidebar, there are 0 local subscribers for the community. when there aren't any subscribers to a community on an instance, the instance will not receive any updates for posts in that community. this includes posts, comments, as well as votes.

startrek.website also had federation issues over the last weeks due to accidentally blocking lemmy instances in some situations.

lemdro.id has recently had some db performance issues that caused it to get around 3d behind lemmy.world, they've been slowly catching up again over the last days.

they did leave before taking the screenshot

a moderator on another instance than the community instance

that was a logic flaw for the selection of which reports are considered for alerting. a fix is currently being deployed, but you should be good for the next 2 days anyway.

the bot has been marked as bot since the very beginning and is also clearly marked as bot in the screenshot, so your comment does not apply here.

we were only counting users active in the last 6 months (based on lemmys active user stats) for this calculation. with the update to lemmy 0.19 back in march 2FA for all existing users was reset, so all users that had 2fa set up before and never reactivated it wouldn't count towards this, nor would users that weren't active at all since then.

Hi,

this was unfortunately an error on our end.

Please bear with us while we work on resolving this situation.

Us not upgrading has nothing to do with making a point.

We're aiming to run a stable instance, which can come at the cost of delayed updates.

We didn't update to 0.19.4, and a few weeks later 0.19.5 was released with a number of critical bugfixes.

0.19.6 will have several more fixes for issues introduced in 0.19.4+, such as a fix for remote moderators updating local communities, allowing admins to filter modlog entries by moderator, as well as some performance issues reported by other instances.

We usually wait for other instances to run the latest version for some time to allow bug reports to surface before we update ourselves.

so far this has been a single case with kbin.earth and lots and lots of cases with kbin.social.

no other instances have been observed behaving like this yet.

it's mostly !asklemmy@lemmy.ml, !asklemmy@lemmy.world, !opensource@lemmy.ml, and !selfhosted@lemmy.world, though some of the latest spam also started arriving in !warframe@dormi.zone.