

we’ll try to get the post out the coming week, at this time we’re roughly looking at updating late January.
we’ll try to get the post out the coming week, at this time we’re roughly looking at updating late January.
while this is generally the intention, unfortunately we’re not always there yet.
i know that lemmy <-> piefed already works, but private messages between lemmy and mastodon users for example do not currently work, and there is also currently no indicator that those messages never were delivered. for lemmy <-> mastodon, this is tracked in https://github.com/LemmyNet/lemmy/issues/2657 and there is work going on right now to resolve this incompatibility.
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
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.
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.
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.
It’s not automatic, admins have the option to ban with or without content removal.
Different instances deal with this differently and admins are also humans that sometimes make mistakes. Especially during holiday season there are frequently trolls running around with racist, transphobic or other offensive content. Sometimes they’re more obvious, sometimes they try to fly under the radar a bit by being less direct. In the end you’re at the mercy of the instance admins of the instance you signed up with and many instances will provide contact information to appeal bans.
Since this account was not a Lemmy.World account it’s not up to us to decide whether or not the user should be banned and whether their content should be removed.
If you’re referring to the post Ex Redditors of Lemmy what made you come on over? What happened at Reddit that you made the switch?
, their account was banned for trolling and all content associated with the account was removed.
They also had a number of other posts that seemed to be doing just fine, so it might be falling in the “stupid kid” category.
The post has since been restored by a community moderator, although the user’s account on lemmy.ml is still banned: https://lemmy.world/post/17593614
@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.
we’ve switched from using multiple federation sending containers (which are supposed to split receiving instances across workers) to just using a single one.
except it doesn’t work well for the rest of lemmy/the fediverse.
many other instances seem to be getting hit by this, but they don’t have as many activities generated locally for this to become much of a problem. additionally, this is mostly affecting instances with high latency to the instance that is being flooded by kbin, as lemmy currently has an issue where activity throughput between instances with high latency can’t keep up with too many activities being sent. the impact of this is can be a bit less on smaller instances with smaller communities often not having as many subscribers on remote instances, although we’ve seen problems reported by some other admins as well. this includes e.g. kbin.earth, which i suspect to have been hit by responses from a lemmy instance, while the lemmy instance was actually only answering the requests sent from that kbin instance.
during the last peak, when we decided to pull the plug for now, kbin.social was sending us more than 20 activities per second for 7 hours straight. lemmy.world can easily handle this amount of activities, but the problem arises when this impacts our federation towards other (lemmy) instances, as e.g. votes will get relayed by the community (magazine) instance, which means, depending on the type of activity being sent, we might have to be sending out the same 20 requests per second to up to 4,000+ other fediverse instances that are subscribed/following the community this is happening in. trying to send 20 requests per second, which lemmy does not do in parallel, requires us to use at most 50ms per activity total sending time to avoid creating lag. when the instance is in australia, with 200ms+ latency, this is simply not possible.
looking at the activity generation rates of some popular lemmy instances, anything that is significantly above lemmy.world is likely not just sending legitimate activities.
ps: if you’re wondering how i’m seeing this post, you can search for a post url and comment urls on lemmy to make lemmy fetch them, even if they haven’t been directly submitted through normal federation processes. this requires a logged in user on lemmy’s end.
for a magazine to show up on lemmy, a logged-in user needs to visit it first. afterwards, to ensure that new content is published to lemmy instances, someone from that instance needs to subscribe to the magazine. this needs to happen on every instance as far as i know. this is one of the reasons services like https://lemmy-federate.com/ or https://browse.feddit.de/ exist.
it is indeed mostly like related activities we’re seeing
fwiw, it does not appear to be triggerable from within lemmy at this time.
I’ve just tried this on another instance and lemmy complains
The webfinger object did not contain any link to an activitypub item
I suspect this currently can only be triggered from threads.
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.
hi, you’ll probably have a better experience here if you tag your post with the correct language or post in english.
note that this isn’t available in all interfaces/clients, but the default web interface supports this.
alternatively, you could see if there are any spanish gaming communities to participate in.
i don’t speak spanish, but this community looks like it might be better suited: !videojuegos@feddit.cl