Both !infosec@kbin.social and !science@kbin.social are being spammed constantly with opioid ads and other non-sense.
It’s quite annoying if you want to use the all-feed. I’ve blocked at least 6 spam accounts just today.
Just wanted to bring that to your attention. Thanks.
As someone on kbin.social, I’m not seeing it. I saw a comment in a similar thread saying that moderation done on Kbin doesn’t federate to Lemmy instances, and I think that’s the culprit here. @ernest (the Kbin dev) is working towards a full release, and I hope that it might fix this issue—or at the very least, that it’s dealt with shortly after.
EDIT: Yeah, I looked at @science from lemmy.ml, and my God is it awful. This really needs to get fixed ASAP.
This week, I’ve been dealing with cleaning up instances from spam. Several hundred accounts were removed, along with several thousand posts - these were massive operations. It’s possible that due to the volume of requests, other federated instances hit rate limits. I see that some of them are still in the queue with a “fail” status. I will gradually resend them after some time. Along with the update of kbin.social and the first release of kbin, new modeartion options will be available, including spam blocking (such as global blocking domains), a new reporting panel for moderators, and improved federation between instances. I will also address abandoned instances and ensure that each one has at least a few active moderators. I know how urgent this issue is, and it’s my top priority. I just need a bit more time as Piotr and I are preparing for the update.
It looks like all the spam I’ve seen are from newly registered accounts. Perhaps this is something you’ve already considered, but would shutting off registration on kbin.social and pointing people to other instances until things are more manageable help?
Can you also add moderators to those magazines? I volunteered for the science mag, but have not gotten a reply. Active mods will help with your workload too.
lemmy.world has removed a lot of kbin.social content: https://lemmy.world/post/5289864
You’re not taking action. This spammer is still posting, even though I reported him nearly an entire day ago.
For all the time you have to type excuses, you could be smashing the ban button, but you don’t. This does not look like a “top priority” from this end. Stop making excuses and just ban the spam accounts. If you have communities without moderation, then close them. You’re managing this very poorly.
Edit: Unbelievable! This spammer created yet another account. You’re not vetting applications at all, are you? This is totally on you. Fix it.
I understand this is a frustrating experience dealing with so much crud in your feed. Admins and mods for many instances of Lemmy and Kbin are trying to work with the tools available to stem this. Attack the problem, not the person. Bee nice.
Please don’t lash out at those trying to help you and the community. We certainly do appreciate your reports as well, hopefully we’ll find a solution that won’t require so much of your report efforts.
Of course, I’m taking action, and on kbin.social, those posts have been removed, which you can verify. However, for some reason, it doesn’t always federate with Lemmy. It used to work before, but practically after every Lemmy update, there’s something to fix in the code, or it could be related to API limits because some requests receive a “fail” status in the queues. The same applies to spam from Lemmy instances - I had to manually clean up hundreds of posts from other instances because they didn’t always send AP requests, which I verified in the logs.
Do you seriously believe that it’s a matter of individual accounts, and banning a user solves the problem?
Am I taking crazy pills? Ban the user, or they’ll keep posting spam. Vet your applications like a valid instance instead of letting any spambot create an account.
You are not taking action if all you’re doing is removing posts. You are handling this in an entirely inadequate and incompetent way, and you’ve made kbin a blight on the fediverse. Get your shit together.
Do you seriously believe that it’s a matter of individual accounts, and banning a user solves the problem?
It’s certainly better than allowing these accounts to continue to post harmful spam. Then when people sign up, there should be some red flags in their application that you can watch for. It’s not like these spammers are highly intelligent. They’re pretty blatantly spam accounts, especially when they have literally just a number’s difference in their username.
By the end of September, kbin.social will receive an update that will address some of the issues. For now, I’m banning spam accounts, and registration is disabled. Additionally, external links are marked as “nofollow.” I just want to emphasize that this is not solely a kbin issue - I had to manually remove spam posts from Lemmy instances as well because moderation didn’t federate, which doesn’t happen with, for example, Mastodon.
For now, the admin of your instance can choose to defederate or remove communities, as the admin of lemmy.world did. Once I’ve dealt with the update, I will reach out to other admins and discuss the possibility of restoring valuable posts.
The problem is that at this scale and with this infrastructure, hotfixes are no longer as straightforward as they used to be - when I could solve these kinds of issues in a matter of hours.
Yeah, I think that might explain it.
It’s very annoying. All the spam is originating from kbin, too.
It’s not even “can easily be overlooked and move on” type spam either, it’s things like “hey kid, wanna buy some oxy?” Kbin admins don’t seem to be doing shit about it because these spammers keep coming back with new accounts, and I have yet to see a post removed from the kbin side of things.
It’s getting to the point that I hope my instance defederates from kbin because it’s just full of trash.
There’s a bug going on that prevents Kbin moderation from replicating over the fediverse - what happens is they will nuke the threads but it will not reflect across the rest of the federation which is a huge bug. A lot of instances are either blocking their communities en masse to avoid defederating, or just flat out defederating.
Are you sure it’s a bug? To me, it sounds like just how it works. This is one reason beehaw is considering leaving the fediverse (and to be honest, I’d be thankful if we did, based on my recent experiences)
Yeah the more I learn about the tech and design around these systems the more I question the philosophy and logic of the whole setup.
The massive vulnerabilities from cached and redistributed (federated) CSAM content, the inability to operate at scale due to various attacks from malicious actors, the lack of moderation tools to deal with the aforementioned issues. It’s just a pile of problems that other systems have literally already solved.
We should go back to forums. This format is overrated, we’re only clinging to it because we’ve been addicted to reddit for a decade and we can’t fathom going back to something as regressive as forums, even if they are logically the better solution for a majority of instances.
Sadly, I just filtered the whole science instance, as it’s nothing but spam
ive had the same experience. i think a remote moderation ability may help spread the moderation load around… that possible?
Yes, I think it’s possible to moderate a community on another instance.
