[ SmokeDetector | MS ] URL-only title, bad NS for domain in body, bad NS for domain in title, bad keyword in body, bad keyword in title, +6 more: quicksupplementfact.com/testro-t3/ by meeksvfab on askubuntu.com (@ThomasWard @quartata)
@JakeSymons not sure if the guidance will be the same across sites, I'd guess some will probably reject it as not helpful if that's the only thing you change (and usually with that sort of attention to detail in the title, there will be things to fix in the body too)
this one is not actually even a programming question as far as I can tell
regarding the rule, I guess we want to tolerate a bit of FPs for a while until we are reasonably convinced that the troll is not coming back and/or changed MO and/or the FP burden clearly outweighs the benefits
@JakeSymons This site of the SE network is for programming questions only. Your comment is not ***acceptable*** within the SE network. Please see our [help/behavior] police for details.
made it code formatted to not loose the linkage and formatting
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, +1 more: Alpha Pro Testobuild Trial Review by rogorilkia on askubuntu.com (@ThomasWard @quartata)
This is a userscript that provides a network wide flag summary for all Stack Exchange sites.
If you are logged into the Stack Exchange network and you have this script installed, you can visit the new flags tab in your Stack Exchange profile:
How does it work?
The script scans your netw...
@rene @Floern what I did to circumvent rate limiting was just changing line 293 to let delay = i < 25 ? 500 : (i < 160 ? 1000 : 3000); Haven't seen any problems since then.
@JakeSymons You are not a privileged user. Please see the privileges wiki page for information on what privileges are and what is expected of privileged users.
Body - Position 944-957: 2349051208634 Body - Position 187-193: HERPES, Position 378-384: herpes, Position 703-709: herpes Post - Keyword * Dr. * with email peterwiseherbalhome@gmail.com Post - Pattern-matching email peterwiseherbalhome@gmail.com
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) 2017-12-18 17:03:02.825117 UTC File "/home/smokey/SmokeDetector/chatcommunicate.py", line 327, in f result = func(*processed_args)
File "/home/smokey/SmokeDetector/chatcommands.py", line 1393, in autoflagged is_autoflagged, names = Metasmoke.determine_if_autoflagged(post_data[0])
File "/home/smokey/SmokeDetector/metasmoke.py", line 333, in determine_if_autoflagged data=json.dumps(payload), headers=headers).json()['items'][0]['autoflagged']
That's another interesting one. There was a point probably 1-2 years ago when we were having API backoff issues all the time. I had an issue theory, implemented locking to address said issue, and we stopped having backoffs. So I'm gonna say it fixed it
Here's the theory:
1. It's a multithreaded thing, with multiple threads trying to use the API at the same time
2. Those threads do respect the backoff
Buuuut, here's what I thought was happening: One thread receives a backoff, and sets the backoff timer. Then another thread sees the backoff timer and waits, say, five seconds. In that five seconds, we get a bunch of posts in that start more threads wanting to make API reqs
So, essentially, we would receive a backoff, wait the recommended time.... then send a whole bunch of queued requests all at once
which is not desirable, really
Locking is implemented so that we only send one request at a time, ever. Which means we don't hammer the API after a single backoff - we wait the backoff, send the next request, then respect the backoff before the next request (if we get a backoff)
[ SmokeDetector | MS ] Few unique characters in body, no whitespace in body, repeating characters in body, repeating characters in title: GSM mmmmmmmmmmmmmmmmm by hmn16 on electronics.SE
This is a userscript that provides a network wide flag summary for all Stack Exchange sites.
If you are logged into the Stack Exchange network and you have this script installed, you can visit the new flags tab in your Stack Exchange profile:
How does it work?
The script scans your netw...
