[ SmokeDetector | MS ] 418 Few unique characters in body, no whitespace in body, repeating characters in body, repeating characters in title, title has only one unique char: ooooooooooooooo ✏️ by iBug on android.SE
@Makyen Yeah. When MS is down then there's no ned to know about feedbacks and autoflagging, but reason weight can still have some value (probably also time-to-deletion, but there isn't a good way to indicate that)
@ArtOfCode Potential AIM breakage?
I think it's better before the colon: aaa, bbb, +1 more (999): [title]
I also was thinking that the end, or just before the link would be better. Having it first, and in bold is a bit jarring. I'd also probably put it in parentheses, as has been edited.
Given that it shouldn't be that much processing to fetch them, keeping them up to date doesn't sound like that big of a deal. I'd do it at least every 24h, or if you want to be more in sync, then every 8h or 4h. The shorter terms just limiting the maximum that you could be behind MS.
@iBug You said that you aren't actually scheduling it for a certain time, just updating after some elapsed time. That means that the maximum that you can be behind is just shorter than that elapsed time. Thus, the shorter elapsed time results in a shorter maximum that you could be behind.
Note: You may, or may not, need to adjust the value of any timeout that exists for the request with larger per_page values. For example, if you're getting posts, my experience is that the default timeout (30s) is insufficient for per_page=30, and very intermittently for per_page=20.
[ SmokeDetector | MS ] Bad keyword in body, bad pattern in url body, blacklisted website in body, body starts with title and ends in url, link at end of body, +2 more (587): bloom" once more, by hdowsroff on askubuntu.com
@iBug looks like: <br>, <hr>, <u>, <p> are missing, and that FIRE's regex may be a bit permissive. And now that you mention it, <kbd>. Looks like I'm going to need to go through the whole permitted list and double check.
@iBug That was my impression on first looking at it, but I hadn't gone through it in detail, tag by tag.
@iBug Yeah, but I need to have it correct and more restrictive in FIRE, due to having to reconstruct the HTML from what SD does to it. Without a more restrictive list it's possible to mangle the post and/or permit inappropriate content.
@tripleee That pattern looks like it's already caught by Mostly non-latin answer and Mostly non-latin body; append -force if you really want to do that.
worldpostalcode.com/india/delhi lists nine codes so that would average 2 million people in each ... more than the population in some countries near where I am
@tripleee That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
Is there a way to report a user based on their profile? I found a user whose profile description is clearly promoting a strip club as is their profile pic.
I'm looking to report them based on their profile not just on a question they posted. Is there any way to do this?
@AJ just exploring really, I was hoping to find an easy way to plot the addresses graphically but without a sense of proportions the map is only halfway there
@AJ I'll be happy to add you to the code group, hang on
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, potentially bad ns for domain in body, repeated url at end of long post (394): Between the eyebrows If the by user48752 on rpg.SE
@tripleee You can't really verify the company address just via the address shown in the whois data. For example, this organization has different address than what is shown on its site
@AJ no no, of course, but when you have enough registrations at least you can try to form a picture, even though it will be incomplete and contain noise and stuff
@Shree That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@Shree Already watched on line 3388 of watched_keywords.txt
[ SmokeDetector | MS ] Bad keyword in link text in answer, blacklisted website in answer, pattern-matching website in answer, potentially bad ns for domain in answer (249): objectivec: fb post comment error by Ammy Watsan on stackoverflow.com
@Shree The reasons "Potentially bad keyword in body" and "Potentially bad keyword in answer" mean that what you are trying to add is already watched. The reasons "Bad keyword in body" and "Bad keyword in answer" mean that what you are trying to add is already watched. Please don't force a new entry when that's the case, unless you really have checked out what's going on. Usually that would entail looking at the files and finding what exactly matched.
@Glorfindel I'd say that's personal preference. I certainly find it easier to pick it out of a consistent location. I also like to still be able to see it on older reports.
@Makyen @Shree I failed to fully edit a copy & paste: It should have been: 'The reasons "Bad keyword in body" and "Bad keyword in answer" mean that what you are trying to add is already in the blacklisted keywords.'
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, pattern-matching website in body, pattern-matching website in title, +2 more (491): supplementfordiet.com/praltrix-au/ by ouewcoew on graphicdesign.SE
@tripleee 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 ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, potentially bad ns for domain in body, +2 more (396): Pro Keto RX lose weight by user48754 on rpg.SE
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, potentially bad ns for domain in body, +2 more (396): Keto X Canada dvfds df df dffd by kfbshsad on apple.SE
[ SmokeDetector | MS ] Bad keyword in title, body starts with title and ends in url, link at end of body, pattern-matching website in body (392): Groves vs Smith Live by user402784 on meta.SE
@TetsuyaYamamoto 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 ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, pattern-matching product name in body, +2 more (589): Bellaire Skin Cream by gentwetlre on stackoverflow.com
Is there a way to report a user based on their profile? I found a user whose profile description is clearly promoting a strip club as is their profile pic.
I'm looking to report them based on their profile not just on a question they posted. Is there any way to do this?
