if the missing NSFW mark is the only reason for removal we're generally open to restore content after that has been fixed.
we will not actively search out content that has been removed and then was updated to include the nsfw mark, but this would be doable on request.
Hi,
which community/posts is this about?
Comparing https://lemmy.world/c/kickasswomen?dataType=Post&sort=New to https://lemmy.world/c/kickasswomen?dataType=Post&sort=Hot I can still see both posts that were posted an hour ago, they're just sorted further down currently, but still on the same page.
Hello,
the post was removed by a Lemmy.World admin.
Since the post is not in a Lemmy.World community and your user is not on Lemmy.World either, this removal is only affecting Lemmy.World users.
Our AutoMod is only notifying you about this happening, but the wording should be improved to make it more clear what happened.
probably, yes. certain VPNs are currently blocked.
we've switched from using multiple federation sending containers (which are supposed to split receiving instances across workers) to just using a single one.
feel free to reach out to me directly via matrix at @mrkaplan:lemmy.world if you want
edit: fyi, mentions of @[email protected] will usually not be seen.
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.
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.
Hello, disposable email addresses are not allowed.
see https://lemmy.world/comment/8961882 for now.
we've been spending a bunch of time already during the last days to get a solution in place on our end that will allow us to selectively reject federated activities from kbin, such as allowing comments and posts while rejecting votes, which seem to be the main issue currently, but we're seeing some stability issues with this currently.
we're planning to unban the affected users from the communities once we have this stabilized, as we currently have to pick between
1-3 are all options we can do with existing tools, 4 and 5 require a custom implementation on our side. as 3. has the least overall impact of those we decided to go with 3 for now, which seems to work out rather well so far, except for the individual user experience of affected users.
4. has been our primary focus to implement currently, but it takes time to ensure this works as expected, as we're essentially building this from scratch. 5. may be implemented afterwards if we want to spend additional time on it.
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.