[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, pattern-matching website in body, potentially bad ns for domain in body (391): practice frame. It in like course by amak fame on android.SE (@AndrewT.)
> Potentially bad ns for domain in body, potentially bad ns for domain in title ---------- Potentially bad ns for domain in body - shipa1.com NS suspicious ns2.inmotionhosting.com.,ns1.inmotionhosting.com. Potentially bad ns for domain in title - shipa1.com NS suspicious ns2.inmotionhosting.com.,ns1.inmotionhosting.com.
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body, Potentially bad keyword in answer, Mostly punctuation marks in answer, and Mostly punctuation marks in body; append -force if you really want to do that.
@thesecretmaster I'm interested in making a comment bot for meta stack overflow. Is your IPS version open source?
I'd be willing to host it and if necessary make adjustments to the source code to get it working. It'd be for pure archiving purposes. In light of this current discussion at MSO, I think that an archiving of all comments could provide crucial extra transparency and your IPS comment bot model seems to be almost tailor made to achieve that.
I ran the numbers and it looks like even posting every comment on MSO seems to very much stay within chat's rate limits and API quota limits. I've also gotten tentative approval to run something like this from a SO mod.
@Magisch Yes, it's open source (on mobile, but I'll send you the GH link when I get back to a computer). Also, happy to help with hosting and/or modifications.
@Makyen I mean, even if I end up modifying it myself, all I'll pretty much have to do is strip out some extraneous parts. It'll still be 100% @thesecretmaster 's code.
a "all of this belongs to thesecretmaster under cc by sa 3.0" should suffice with source links
Thats all it needs to be. Comments that get deleted don't get auto removed from chat
I've run the numbers, even with the most conservative assumptions on bloat, we're not looking at over 800 comments per day
Most days see 250-300 undeleted comments on weekdays and 100-150 on weekends. Even assuming 50% deleted comments (shog's estimate on main, where more get deleted, is 10%), thats nowhere near the 10000 per day api quota or any chat rate limits,
@Magisch Well, that's not how to think about the API quota. The bot polls the comment endpoint every n minutes, so that's how you'd calculate quota usage.
@Magisch My numbers are saying 188/day undeleted in the last month; assuming a high 50% deletion rate, that's going on 400/day - still good on rate limits.
@Magisch Alright, you have a (tentative) greenlight. We're still waiting on a staff's reply, but I have at least one other moderator willing to give this a shot and keep an eye out. Regular disclaimers about bots (you should stay close to make sure nothing funky is happening, it may be shut down by mods if it goes haywire or tries to take over the world, etc.) apply.
I have no experience with ruby whatsoever so I'd probably just try to make it work with all the moving parts stripped out, but if y'all want to give it a go, any version works
I was thinking that I should make another account. I would prefer to be the one who creates the account, because getting chat notif emails is kinda handy sometimes.
We'd also need to get the bot 20 rep somehow (suggested edits are prolly easiest), which is kinda annoying.
Wanna make a room on chat.SO and we can move over there?
IIRC the reason for the recommendation is that API responses are cached for 1 minute, so hitting the same endpoint with the same parameters will always return an identical result until the cache expires
@thesecretmaster If possible, it would probably be beneficial to have the IPS and SO bots on different IP addresses. The backoff response is expected, and definitely enforced, to apply to all requests to the same endpoint, per IP address. Both bots will be accessing the same endpoint, but with different parameters. This will make backoff responses more common, and SE will expect them to be honored by both bots, regardless of which got the backoff.
Not complying with backoff can definitely get the IP blocked from the SE API for an unspecified period, which can be minutes to, at least, hours. It's probably...inconvenient to have the bots communicate backoff state between them, so separate IP addresses might be easier.
@thesecretmaster That would be nice. It's what I'd expect to be the case. Sometimes that seems sufficent. Unfortunately, my experience is that there are times when that hasn't appeared to apply. Unfortunately, I haven't tracked the issue I've seen down. It certainly doesn't matter once the rate limit block is active.
It's possible that what I've seen has resulted from issues arising from the interaction of multiple instances of multiple scripts, but the times I seen the problem, it hasn't appeared that way.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad pattern in url body, link at end of body, pattern-matching product name in body, +4 more (684): Ezytone Detox Review by jeenalobby78 on askubuntu.com
@Makyen That pattern looks like it's already caught by Bad keyword in body, Pattern-matching website in answer, Pattern-matching website in body, and Bad keyword in answer; append -force if you really want to do that.
@Makyen 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.
@Makyen 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.
