[ SmokeDetector ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching website in body: Bella Gold Serum by Naomi Pasko on drupal.stackexchange.com…
[ SmokeDetector ] Bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body: Alpha Fuel Testo by loocmei on drupal.stackexchange.com…
I'm debating how to design that right now. I'm getting the feedback stats out of the MS API; I've got the MS post ID. What I don't have is the chat message ID, which I'd need to post a chat message for feedback. The alternative is restrictive: only those with approved MS accounts can feedback.
@Magisch sure, I can't get to GH right now though. Maybe if @Ferrybig is around, he can do it?
Honestly, the best way would be to actually use the chat_message_id field. Have Smokey send the chat message ID to MS, then it'll be returned in the API.
That's currently not done because Smokey pings the stuff to metasmoke at the same time as it posts the message. It doesn't actually know the message ID until after it's sent the info.
(1) to continue sending the post packet to metasmoke while we post the message, then trawl for the message ID and send another request to metasmoke to update the post.
(2) delay sending; send everything at once after we've collected the message ID
@Magisch I could actually time it. Time how long it takes between receiving the results of the metasmoke API query and the POST to chat returning success.
Average it over 100 runs, add 50%, and we have a value.
