2FA has been restored for all LW users that had it enabled before and didn’t reactivate it on their own since.
There will be an announcement posted later on explaining what happened.
edit: announcement is out: https://lemmy.world/post/18503967
2FA has been restored for all LW users that had it enabled before and didn’t reactivate it on their own since.
There will be an announcement posted later on explaining what happened.
edit: announcement is out: https://lemmy.world/post/18503967
this is a separate issue unrelated to the 0.19 update.
this was not a Lemmy bug.
Hi,
this was unfortunately an error on our end.
Please bear with us while we work on resolving this situation.
@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.
it’s not just this community getting hit.
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
Most of these are unfortunately limited to local instance moderation, which means all instances that don’t run these bots don’t benefit from them.
The posts have already been modified in ways that they aren’t as easy to reliably filter anymore, though still possible with fairly low false positive rate.
To add to this, depending on how content is removed, removal may or may not federate properly. on Lemmy.World, we’ve been removing content in a way that reliably federates, so while a lot of this spam does arrive in !asklemmy@lemmy.world and !selfhosted@lemmy.world, the removals on Lemmy.World should federate to all other instances (0.18.5+).
The other portion of the spam is mostly on Lemmy.ml, in !asklemmy@lemmy.ml and !opensource@lemmy.ml, and not all of their removals have been done in a way that federates.
they appear to be advertising their “criminal organization”, listing some of the illegal activities they do and where to find them.
posting and commenting.
voting should work: https://lemmy.world/post/11967676
you may have been thinking of https://poliverso.org/objects/0477a01e-1166-c773-5a67-70e129601762, which was neither lemmy devs, mastodon devs nor lemmy.world admins