3 ms·
I’d suggest one additional heuristic: once your bad word detector has triggered, shut down the chat for 10 minutes. That way waves of assholes don’t monopolize
by JSR_FDED 2mo ago
I’d suggest one additional heuristic: once your bad word detector has triggered, shut down the chat for 10 minutes. That way waves of assholes don’t monopolize the chat, and when they move on to the next target the functionality returns to your site automatically.
- phoghed 2mo agoBut then one asshole can denial of service your chat very easily
- dylan604 2mo agoYeah, shutting down to that specific browser fingerprint would be the better way. Sometimes, being able to recognize a user has it's benefits for good /s
- lesostep 2mo agoOr just drop websocket connection to them. Refreshing pages to establish connection again is semi easy for someone who made a honest mistake (and Could make them more cautious), but if someone wants to trigger web-socket disconnect all the time, it would become cumbersome. Add something like fail2ban, and you're set enough against passing trollers, but not interesting enough to draw attention from people that like the challenge.
- Retr0id 2mo agoBut don't let them know they've been shut down, use a shadowban.
- effseven 2mo ago[dead]
- nickthegreek 2mo agoAgreed. I'd just have 2 chat pools, once you break rules, you get moved to the rule breaker pool with the other like minded individuals. Well behaved individuals wouldn't even know or care about the separation.
- operation_moose 2mo agoGreat way to get someone to create a bot that swears in the chat every 10 minutes and 1 second to permanently shut it down.