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.
calling other people pedophiles is not trolling.
such allegations can be life-ruining and should not be done lightly.
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.
Hi,
this was unfortunately an error on our end.
Please bear with us while we work on resolving this situation.
deleting a community: right side, click the trash icon:
communities disappearing from your subscribed list typically mean that you have been banned from that community.
subscribe pending can have different reasons. it might be that this includes getting banned from an instance, but it can also be the result of some other technical issues.
it was a significant part of the brand of a spam/advertisement campaign several months ago
it's removed from our slur filter now
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.
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
- defederate from kbin.social (and other kbin instances when they are affected)
- reject all inbound activities from affected instances
- temporarily ban affected users in the communities associated with the issue
- drop all activities with certain characteristics, such as votes, when coming from a specific instance
- drop all activities with certain characteristics, such as votes, when coming from a specific instance and exceeding a rate limit
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.
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.
view more: next ›
!superbowl@lemmy.world