The quota_remaining property was not in the API response. Error: no method found with this name at 13:27:07 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions
@RyanM That pattern looks like it's already caught by Bad keyword in answer, Potentially bad keyword in answer, Potentially bad keyword in body, and Bad keyword in body; append -force if you really want to do that.
@Makyen Can I please have the Core role again please for GraphiQL queries? (Sorry for changing my mind about this again but I just found out the existence of the fire_extra.user.js userscript)
@Xnero That will happen if there are fewer non-core users with matching flagging conditions than there are core users with matching flagging conditions. Thanks for pointing that out. It's something we should change.
@Makyen Yes, since if there are 3 autoflags (2 go to users, 1 to Core & 1 to non-Core) and there are less non-Core users who are eligible to flag compared to Core users the probability of autoflagging is greater for non-Core users. In my case as my flag conditions are very lenient I tend to be the only non-Core user who is eligible to flag and hence I flag.
Interesting... Well, hey, then I think it's technically helpful given that you're more active and thus more likely to respond to an autoflagged FP than a non-core flagger that's not been in CHQ for a long time. Thanks for showing me those.
[ SmokeDetector | MS ] Few unique characters in body, no whitespace in body, no whitespace in title, repeating characters in body, repeating characters in title (396): xxxxxxxxxxxxxxxxxxxxxxx ✏️ by rlt on graphicdesign.SE
