[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, pattern-matching website in body, potentially bad ns for domain in body (294): Praltrix Australia by kfbshzas on apple.SE
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, pattern-matching website in body, potentially bad keyword in body, potentially bad keyword in title: Thermo GYN Keto Trial Reviews by rimeriyeci on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, pattern-matching website in body, potentially bad keyword in body, potentially bad keyword in title (296): Thermo GYN Keto Trial Reviews by rimeriyeci on stackoverflow.com
@Mithrandir I find the weight in the message useful, I have a script that shows messages of smokey in my notifications area, and the weight allows me to prioritize my work vs looking at the post, so on moments with no work I can handle everything, but on moments I'm really busy I might for example unconsciously filter out almost all messages. Having to get the weight from MS would make my US more complex and delays the showing of the dialog in case of MS errors/slowdown
@ArtOfCode Or MS should only remove smokedetectors from standby if they did atleast 3 pings in X minutes, so if it has problems, it is less likely to get the required amount of "good" pings to make them move out of standby mode
@iBug If ms wouldn't receive pings from any smokedetector (inbound to MS), none of the smokey's would pass the "3 pings in X minutes" threshold, so none are suited for promotion to the "online" smokedetector status