@aspaghetto I'm not particularly a fan of multiple accounts if you are talking about how to get Smokey to behave under heavy spam load, I made some comments on the Github issue but the more I think about it, the more I seem to prefer doing something really simple with the existing websocket
in fact I was thinking the existing PulseMonitor could quite easily be set up to monitor how Smokey keeps up with reports and post something to alert us if it's lagging behind by more than just a few posts
if we make that a regular thing our userscripts could probably pick up the PulseMonitor notifications instead of attempt to parse the human-readable reports that Smokey posts here
which would eventually mean that many spam messages will already have been closed by our regulars by the time you see the report from Smokey
... but one thing at a time
Manish merged by contribution to Chatexchange so now I should be able to make Halflife a lot snappier by merging adjacent chat posts whenever possible
this could be used by SmokeDetector as well, of course
but chat messages with formatting can't be merged to multiline messages
if we can cope with the response in a timely fashion the need to report to other rooms diminishes but of course there's also a limit to what's humanly possible
but in other words a spam wave during active hours will be easier to cope with if we get reports in more or less real time, and a spam wave which exceeds our capacity (because it's so big, or because it's during hours when nobody is here) it probably doesn't matter that the reporting to other rooms takes time (as long as we eventually catch up!)
if you switch between clients you need to keep state somehow anyway
not sure what could be done with socketscience but the client can't easily pick up its old messages to itself after a restart, can it? (I guess it could actually, the chatexchange code apparently just scrapes the room)
[:49916225] Blacklisted user - blacklisted for //puzzling.stackexchange.com/questions/81727 (https://metasmoke.erwaysoftware.com/post/170581) by the metasmoke API
