this post was submitted on 03 Dec 2023
18 points (100.0% liked)
/kbin meta
12 readers
1 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm not entirely sure any of that would be effective in controlling visibility of spam accounts from other instances. I'm quite sure that up/down voting does not always federate perfectly. Those steps would all be effective in handling malicious accounts on the same instance they're registered with, as long as their malicious posts and comments are also on that same instance; the effectiveness would certainly fall off sharply for content posted at other instances.
I wonder if there needs to be some kind of "governance board," like the NATO or EU of the fediverse, where major instance admins meet and set agreed upon standards of instance behavior.
We don't need to depend on federated downvotes to judge what does or does not belong on kbin. In fact, I think it's probably better if we don't. People are downvoting the bots here. I have yet to see an account with negative rep. on kbin that wasn't a spammer.
Regardless, rate-limiting incoming posts will limit the damage and annoyance to us.
I'm not sure that would help with this particular issue -- and there's already a fair amount of bad relations between instances so I don't think a wider fediverse board is likely to succeed even if it could help somehow... I guess instance admins that do agree on general moderation principles could help co-admin each other's instances to cover better for when they're offline (maybe some of them already do?), but we shouldn't have to depend on remote admins being responsive to deal with an issue affecting our instance.