Some ideas for anti-spam measures that might help:
block users who post flood -- e.g. if an account makes 10 posts a minute, it's a spammer
block accounts that end up massively in the negative shortly after they start posting -- e.g. an account at -50 within 15 minutes of making its first post is probably a spammer (exact thresholds may need some tuning). Note that this is different from blocking new accounts that go into the negative since people can register accounts in advance of an attack and wait until later to cause disruption.
block users who post repetitive comments/links excessively -- e.g. if the same link is in 10 comments/posts from the last hour or they've submitted the exact same comment a dozen times, the account is probably a spammer (again, thresholds may need tuning); that won't catch all the bots (one of them added a bunch of random words) but will catch some of them. More clever filtering could catch the other bots.
block new posters who are reported many times by established accounts in good standing -- at least until an admin can check what is going on
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 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.
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.
Thanks for the feedback, I've contributed sorting of the magazines and actually "the other four are under the hot tab" is not the case. They're not in any specific tab, they just sort by number of threads/comments/posts/subscriptions. I've done it this way to be backwards compatible with newest/hot/active tabs that were already there before introduction of sorting by clicking on table headings. Nonetheless, I agree that the Magazines page needs more polishing after recent changes and your suggestions are good.
These points are not a priority, but relatively easy to achieve. They will gradually appear on the instance in between working on significant things. It's worth following https://kbin.social/m/kbinDevlog
Now I just need to find a convenient way to save this piece of code and copy-paste it whenever I need it 🤔
Honestly, I'd just suggest to add a button for it in the editor after the code one? I think it's a common enough thing to use to warrant it. For every other formatting maybe a little link for a pop up or expandable that shows the remaining formatting rules, similar to how it was on old.reddit.
I'm poking around at it now. I'm guessing it's probably something to do with JavaScript -- which I block by default via NoScript. (That's kind of odd though since I thought it was generating a <details>/<summary> HTML block server side, but maybe it's doing it on the client and I just happened to have JS unblocked when I saw it before?)
Edit: It looks like it is coming from this webpack'd JS file currently which I think is built from this JS source file; there is a handleSpoilers function defined which manipulates details/summary elements. Oddly, there is also PHP code for manipulating details/summary like I thought.
@ernest can chime in on if that's a temporary thing or what, but yeah, it seems to not work for me because I block JavaScript.
Yo, that is so good to know!
Wish there was a link to some quick stylesheet guide that kbin supports when you write a comment. Haven't seen this feature before.
of all these beautiful features, gotta say the CSS styling on the mags is my FAAAAVVEEE. i love doing it. i kinda go overboard and need to reel it in, but the ability to personalize your mag is so fun. though, people should have an option to toggle mag styles off, they can be distracting or the best part about the mag lol (ㅅ´ ˘ `)
Been having a problem recently (and intermittently) where when I upvote a comment it goes to a page that says Error and I have to go back to the previous thread, refresh it, and then the upvote works.
No, kbin.cafe is not run by the same person that runs kbin.social; here's a post by the owner of kbin.cafe and @ernest is the owner of kbin.social and the main developer of kbin. As you mentioned, kbin works similar to an email service, so different kbins (and lemmys and mastodons) can communicate with each other.
kbinMeta
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.