Given SE's response to my last report of these "the quota_remaining property was not in the API response" issues, and them not seeming to care that the errors had increased by over an order of magnitude, it's unclear to me at what point I should be posting yet another report of these.
@Makyen Their reply said "if you're seeing the API fail more frequently than it used to, we'd be interested in looking into what might be happening there ... Feel free to reach out ... if any of the above seems to be happening". I looked at the messages re "quota_remaining" posted by SD here in Charcoal HQ, and if I looked correctly, they appear to have gone up by over 75% since May. Of course, if a messed up the numbers, then disregard this
You appear to have missed that they said in a comment "this is still status-bydesign" after my comments telling them that A) I'd already pointed them at the frequency data (so they could have determined the frequency themselves), and B) that it's at least '11.78 times higher than "normal"' (as of mid/late September vs data back to 2016).
In other words, I already reached out, again, in comments, and they don't care.
@cocomac Messages/reports from SmokeDetector in Charcoal HQ are generally kept as records. If you really need to delete a message, please use sd delete-force. See this note on message deletion for more details.
Thoughts on placing a bounty there? I wouldn't expect it to get fixed as a result, although drawing attention could potentially be useful especially as it is getting annoying
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, potentially bad ip for hostname in body, potentially bad keyword in body, potentially bad keyword in username (195): what is java virtual machine? by kosmik tech on superuser.com
[ SmokeDetector | MS ] Bad ip for hostname in body, blacklisted website in body, body starts with title and ends in url, link at end of body, pattern-matching website in body, +1 more (487): 7zip password recovery software by kirti jaswal on superuser.com
The quota_remaining property was not in the API response. Error: no method found with this name at 08:03:45 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/723200
The quota_remaining property was not in the API response. Error: no method found with this name at 08:05:17 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/24720;24721
The quota_remaining property was not in the API response. Error: no method found with this name at 08:05:42 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/28747
The quota_remaining property was not in the API response. Error: no method found with this name at 08:06:19 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/67519
The quota_remaining property was not in the API response. Error: no method found with this name at 08:06:34 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/138516;138517;138518;138519;138520;138521;138522;138523;138524
The quota_remaining property was not in the API response. Error: no method found with this name at 08:06:53 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/614302
The quota_remaining property was not in the API response. Error: no method found with this name at 08:07:24 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/138501
The quota_remaining property was not in the API response. Error: no method found with this name at 08:09:09 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/70144
The quota_remaining property was not in the API response. Error: no method found with this name at 08:10:16 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/723206
The quota_remaining property was not in the API response. Error: no method found with this name at 08:10:42 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/138501
The quota_remaining property was not in the API response. Error: no method found with this name at 08:10:58 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/723206
The quota_remaining property was not in the API response. Error: no method found with this name at 08:11:46 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/388890
The quota_remaining property was not in the API response. Error: no method found with this name at 08:14:44 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/388912;388913
The quota_remaining property was not in the API response. Error: no method found with this name at 08:15:32 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions/388890
SD is partially working. You can watch for SD reports in Charcoal Test SO
6
SD currently can't communicate into chat.SE, but the chat.SO and chat.MSE rooms should now be working. I've changed Charcoal Test SO such that it will receive all reports, similar to what Charcoal HQ normally sees.
If you just pulled to main branch, it likely will not respond here. Makyen is using a mutilated form of rooms.yml to make Charcoal Test SO the "main" room since at the time that was all that SD could log into (I think)
The quota_remaining property was not in the API response. Error: no method found with this name at 16:46:46 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
@SmokeDetector No evidence of affiliation, but is suspicious given it's the only hit on SE, and the user's other answer posted 10 minutes prior is plagiarized.
