The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 04:19:10 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 04:19:27 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 04:19:50 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 04:20:28 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions
[ SmokeDetector | MS ] Bad ip for hostname in body, link following arrow in body, pattern-matching website in body, potentially bad asn for hostname in body (291): How Much Does MaxPhone Cost? by MaxPhone on stackoverflow.com
[ SmokeDetector | MS ] Blacklisted website in body, pattern-matching website in body, potentially bad asn for hostname in body, potentially bad keyword in body (195): why we can use Best Minoxidil? by Pallavi on stackoverflow.com
@tripleee It doesn't really matter what name you use, as they can edit that field (as I realized after I asked the same question the last time someone wanted an API key). :;
@RyanM I'm interested in hearing what you're planning/thinking about. I would have expected updating/improving/adjusting the existing tools would be easier, unless you're wanting to operate on multiple posts at a time (e.g. all posts in a list after a search), but it doesn't feel like it would be a good idea to operate on all such posts without looking at each one individually (where adjusting the existing tools seems like it would be reasonable).
As far as possible changes for the existing scripts, for SIM, I've been considering adding a button for moderators which undeletes, unlocks, reports, waits for the report to show up in MS (report existence detected via the MS WebSocket), and then spam or R/A nuke the post again. I've also considered giving the user the option to add an MS write token, so the report can be sent via MS, rather than through chat, if the user chooses.
@Makyen I'm looking to bulk check search results for whether they're in MS. It's possible that would be best as an improvement to AdvancedFlagging; not sure. Beyond that, a button like you describe is exactly what I was thinking (though I hadn't thought of using the websocket since I wasn't familiar with its capabilities, and I was planning to use an MS write token instead of trying to figure out chat). I'm not at all familiar with SIM, so I'm not sure whether tweaking it instead would make sense.
The main thing that is slow is opening every red-flagged post to see if it's in MS or not.
Plus, it'd be nice to have a one-click reporting solution, since my current technique is very approximate, and trades off between either deleting before the report is properly created, or leaving the post up for a bit and potentially confusing people.
@RyanM I can certainly see that that would be helpful. OTOH, due to the load on MS, I'd prefer that such data not be fetched for every search you or others using the userscript do, so would prefer that it be something they have to trigger. Fetching it when you're specifically looking for that is fine, it's just not something we'd like to see happen all the time for every search results page.
@RyanM Yes, it has seemed like it would be helpful to have that, even at the relatively low volume I've reported.
Ideally, we'd be able to just report the posts while they are deleted, but that, at a minimum, would require scraping all of the needed data from the page and pulling in data from at least the edit page. Given SE's lack of semantic CSS, that's something that's quite frustrating to write and easily broken. I use to do it for the Rumba Forecaster, but I basically gave up when SE started changing their HTML/CSS so often.
@RyanM Given the possibility of wanting it for other use cases, I'd probably go with a button. Although, if you're almost always wanting it when you're doing a search with those specific parameters, then it's reasonable to have it happen automatically under those limited conditions.
