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.

▲

operation_moose 12 hours ago | parent | next [-]

Great way to get someone to create a bot that swears in the chat every 10 minutes and 1 second to permanently shut it down.

▲

phoghed 12 hours ago | parent | prev [-]

But then one asshole can denial of service your chat very easily

▲

dylan604 12 hours ago | parent [-]

Yeah, 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 12 hours ago | parent | next [-]

Or 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 12 hours ago | parent | prev [-]

But don't let them know they've been shut down, use a shadowban.

	▲	nickthegreek 10 hours ago \| parent \| next [-]
		Agreed. 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.
	▲	effseven 11 hours ago \| parent \| prev [-]
		[dead]