I started a separate room about Deepsmoke (PR#1014) to keep this discussion from polluting CharcoalHQ and vice versa
2
I have been running with a couple of breaks since several hours now on all of Stack Overflow (including pt, ja, ru, are there others?) and the API is giving me a clean verdict for everything
this is still running on my laptop so it will break when I shut the lid or lose the network etc
I sent my SSH key to @Undo in response to his offer to host an experiment on Azure
I have invited @TajyMany here as well, in the hope that we could speed up communications compared to the slow trickle of comments to the PR ticket
if anybody from Charcoal would like to be added as a room owner here, just ping me (or one of the other room owners -- I added Undo and Art as owners already)
I would like to know what sort of timetable we can hope for for the Python-only implementation, and whether and if so when we can regard the API as stable
other pending questions are about the costs of running the thing on Bluemix (already covered in the ticket) and how to set up a host name for the current IP address (only discussed in chat)
I guess Art is the owner of charcoal-se.org so I'd like to ask him to add deepsmoke.charcoal-se.org for this service
I have two instances running now ... will turn off the one on my laptop at least for now
I think I managed to fix the Python 3.4 legacy issue (different json internal namespace in Python 3.4) to the point where it has scanned 166 messages without falling over
this instance for a little more than an hour, but I have been running this basically for 8 hours with just intermittent breaks and it has detected nothing
that's not completely out of line with expectations, there is not a large number of spam messages on SO and fewer still which are in some sense representative of what we see on other sites
chat.stackexchange.com/… shows about 20 from the time range and I could have had breaks when some of them were posted
but it's also not implausible that the model was retrained to avoid the false positives we reported before and is now just not very sensitive to contemporary spam
in any event, maybe I should simply run it on all messages, not just SO
gotta run now, will be back tomorrow unless there's something urgent ->