this post was submitted on 22 Apr 2024
20 points (100.0% liked)

/kbin meta

3 readers
12 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 1 year ago
20
submitted 6 months ago* (last edited 6 months ago) by testing@kbin.social to c/kbinMeta@kbin.social
 

Banning spam accounts on kbin.social is a cumbersome affair.

E.g., today @bayaz tried to ban several spam accounts. But that just did not quite work:

Instead of straight forward banning the accounts responsible for spam, those accs got unbanned.

How come?

If magazine owners ban a spam acc which prior went unreported, the ban button triggers an unban command.

To effectively ban accounts, they must be reported first. Approving the report will trigger a ban. I.e. magazine owners must report the account identified as spam to themselves to enforce a ban.

Therefore, pre-emptive banning of spam accounts does not work on kbin.social.

This is a serious problem which needs to be addressed asap.

you are viewing a single comment's thread
view the rest of the comments
[–] bayaz@kbin.social 1 points 6 months ago (1 children)

Okay, thanks for your patience. I think we've hit the limit of what we can do at this point.

Nothing changed with your downvotes or comments. Going through kbin.social/u/{user}, I was able to view and delete PellyNews's threads. I am unable to do anything with the other two users. Even though I can see they exist, the relevant threads do not show up for me under their profiles.

I'll file the issue and keep just deleting what I can until things are sorted out on the backend. Thanks again for your help on this.

[–] insomniac_lemon@kbin.social 1 points 6 months ago* (last edited 6 months ago) (1 children)

I was able to view and delete PellyNews's threads
I'll file the issue and keep just deleting what I can until things are sorted out on the backend

I still see them, eg https://kbin.social/m/food/t/982256 or https://kbin.social/m/food/t/982254
Also, here's another thread from a different user: https://kbin.social/m/food/t/982032
EDIT: Though perhaps it makes more sense to not remove all of the ghostly posts, to make sure the root cause can hopefully be fixed

Looking at the modlog, the ones you removed were posts (microblogs). Relevant to the issue?

I also see the modlog showing the unban command, much like mentioned in the thread description here.

[–] bayaz@kbin.social 1 points 6 months ago (1 children)

Looking at the modlog, the ones you removed were posts (microblogs). Relevant to the issue?

Nice catch!

With your direct links, I was able to see those threads. I attempted to delete two of them, and the modlog shows that I was successful. I've left the third for now as evidence for any developers who care to look.

Regarding "unban", I'm hoping that's just a bug in how things are printed. The ban does show up in the moderation log.

[–] bayaz@kbin.social 2 points 6 months ago (1 children)

The issue has been reported: https://codeberg.org/Kbin/kbin-core/issues/1377

Let me know (or post there directly) if I missed or misstated anything.

[–] bayaz@kbin.social 2 points 6 months ago

@insomniac_lemon It ended up being super simple -- my profile was hiding the 18+ posts by default. All I had to do was uncheck a box, and everything appeared again. Kind of a clever way by the spammers of getting around some moderation if it was intentional. It sounds like the kbin devs might consider changing the defaults on that for moderators to avoid this in the future.