[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, pattern-matching website in body, potentially bad ns for domain in body, potentially bad keyword in body, +1 more (396): In the situation of the particular manboob by user56521 on worldbuilding.SE
@AjayBrahmakshatriya okay, I know this has taken longer than expected, but I had to restart the testing. After 1 week smokey used about 1.11 GByte traffic in, and 234 MByte out. Higher than I was expecting. Maybe an update of some sort ran that I wasn't expecting. ¯\_(ツ)_/¯
Fairly outdated (before perspective IIRC) and should probably be taken with a grain of salt anyway
Remember we've got status pings, websocket feed, HTTP requests to chat (multiplied by 3+ due to number of rooms), SE API, perspective API, plus misc command HTTP requests to MS, git data, and probably a few more which I'm missing
Status pings is like less than 1500 times a day and only a few KBs per ping, the websocket feed is tied to # of posts. HTTP requests to chat is far less than that because messages aren't heavy (and much less than posts in quantity).
I happen to be staring at a data point that might be useful: the JSON data from the SE API for a set of 3,700 questions was 10,285,887 characters (which may be transmitted as more than 1 byte/character). This data, includes the body Markdown, but not the HTML (which may, or may not be longer, depending on the data), and includes no information on the answers associated with the question. That works out to 2.8kB per post.
@Makyen That pattern looks like it's already caught by Potentially bad asn for hostname in answer, Blacklisted website in body, Blacklisted website in answer, and Potentially bad asn for hostname in body; append -force if you really want to do that.
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +6 more (691): evaherbalist.com/keto-6x/ by farikadol on wordpress.SE
[ SmokeDetector | MS ] Url-only title, bad keyword in body, bad keyword in title, body starts with title and ends in url, link at end of body, +4 more (690): drozdietblog.com/climadex/ by user884369 on askubuntu.com
@ArtOfCode will the system trigger on a post if there is a difference of only 1 in 'role total', or does it have to be e.g. 50% higher than the other feedback?
[ SmokeDetector | MS ] Few unique characters in body, mostly punctuation marks in body, repeating characters in body (186): numerical problem by Person on engineering.SE
@SmokeDetector I agree that this should not have been auto-flagged. However, just an image with filler garbage punctuation marks is something that's reasonable to be blocked by a system level block.
@EriktheOutgolfer That pattern looks like it's already caught by Pattern-matching website in answer and Pattern-matching website in body; append -force if you really want to do that.
[ SmokeDetector | MS ] Body starts with title and ends in url, link at end of body, pattern-matching website in body, potentially bad keyword in body, potentially bad keyword in title (296): Keto 900 FAQs About Birth prevention by GrenesBekhi on drupal.SE
@Glorfindel exactly, although I'm pretty sure AIM should behave correctly for both reports; I guess it doesn't know what is the correct report because the [MS] link isn't specific enough
@EriktheOutgolfer That's correct. The link in the SD report can sometimes refer to up to several different MS posts. I'm getting to the point where that will be resolved for both FIRE and AIM, but what I have still needs some work.
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@TetsuyaYamamoto That pattern looks like it's already caught by Pattern-matching website in body and Pattern-matching website in answer; append -force if you really want to do that.
Good day. This question is regarding the 'behaviour' of StackExchange.
The thing is, you see, that as we all know, StackExchange is a BIG site, and thus many new users come to it every day. However, seeing their first question being closed for 'improper formatting' and all that blah blah... It ...
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
> Pattern-matching website in body, pattern-matching website in title, pattern-matching website in username ---------- Title - Position 6-20: nutritions.com Body - Position 6-20: nutritions.com Username - Position 6-20: nutritions.com
Good day. This question is regarding the 'behaviour' of StackExchange.
The thing is, you see, that as we all know, StackExchange is a BIG site, and thus many new users come to it every day. However, seeing their first question being closed for 'improper formatting' and all that blah blah... It ...