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.

this is a separate issue unrelated to the 0.19 update.

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.

@PugJesus@lemmy.world, you might have been posting only for LW users for a while :-/

this is unfortunately correct for the time being.

while we still have aggressive rate limits in place to limit federation impact from kbin bugs, which started with the measures that @sunaurus@lemm.ee mentioned, this wouldn't impact activities coming from lemmy.world towards kbin.social.

while kbin.social used to break down every now and then based on what i saw people comment, service was typically restored within a short period of time. more recently however, any time i've looked at kbin.social in the past couple weeks, it's only been showing an error page. i suspect it may have been unavailable the entire time, not just at the times i looked at it. looking at our federation stats, the last successfully sent activity from lemmy.world to kbin.social was dated 2024-06-18 00:12:25 UTC, although the actual send date may have been later. successful is also not necessarily guaranteed, as some error codes might be misinterpreted as success due to how servers can be set up and how response status codes are interpreted on the sending side.

if activities sent from lemmy.world don't reach kbin.social then the posts and comments won't be relayed to other instances. this is generally an issue in activitypub when instances are down, as such "orphaned" (at the time) communities effectively become local-only communities, isolated islands on all instances that already know about them.

at this point, the last time we've received an activity submission (federation traffic) from kbin.social as on 18th of June, so it seems like it was working for some time on that day and has been broken since.

at the start of this month, @ernest@kbin.social (kbin.social owner, main kbin dev) said that he was going to hand over management of kbin.social to someone else, as he's currently unable to take care of it. presumably this hasn't happened yet.

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.

Lemmy.World is legally primarily bound by the countries listed here.

If we get a request, of course we will evaluate that request.

When it comes to taking down content, such as copyright infringing content, we may err on the side of caution to reduce the legal risk we're exposing ourselves to.

When it comes to handing over data that is not already publicly accessible, such as (not-really-)private messages or IP addresses of users, we will not "err on the side of caution" and hand out data to everyone, but we must follow the laws that we're operating under. See also https://legal.lemmy.world/privacy-policy/#4-when-and-with-whom-do-we-share-your-personal-information.

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.

posting and commenting.

voting should work: https://lemmy.world/post/11967676