@ArtOfCode BTW: I did poke @Floern (not pingable here) in SOBotics to see if he had a chance to try again to get Generic Bot running in SO Socket Science. I have not heard back as of this point.
@gparyani Probably are. They have talked in here, so I could reply to a message, but I've already pinged them in SOBotics, so didn't feel it was important to do so here too.
@gparyani From this project's POV, NAA is FP. It exists because it's easier on the humans to be able to provide that feedback, because we do differentiate answers as such. Other feedback types were not originally incorporated to account for questions. IIRC, it's been stated that it would be quite a bit of work to add additional feedback types. My expectation is that the issues would be in how things were queried from the database in many spots, because MS will record arbitrary feedback types.
If I recall correctly, the other issue is that there are many past posts which would need to be reclassified if a new feedback type is added (since all of our feedback types have existed since the start of the project)
That could certainly be an issue, particularly if the feedback was going to be used for something other than just a block/not-block decision that is strictly about spam/R/A. If we had people categorize things with OT/closable it might be data that could be used in the future, but it would take considerable extra work to actually use the data, even if we had it.
[ SmokeDetector | MS ] Url-only title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +3 more (787): thepilpedia.com/provexum/ by thrina12 on askubuntu.com
So, this question should maybe be locked, given the edit war or whatever we want to call that (I assume there must be edit history I can't see because otherwise the OP's obscene posts seem totally out of the blue with literally nothing having happened to trigger them), but I don't think the moder...
@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.
[ SmokeDetector | MS ] Blacklisted username, offensive body detected, offensive title detected, potentially bad keyword in body, potentially bad keyword in title, +2 more (255): fuck you idiots by fuck on gaming.SE
@double-beep 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.
PR#3120 ("double-beep: Watch thenationalskincentre\.com") opened by SmokeDetector
@double-beep That pattern looks like it's already caught by Blacklisted website in body, Bad keyword in body, Bad keyword in answer, and Blacklisted website in answer; append -force if you really want to do that.
@Machavity While the website legitimately should be blacklisted, a current blacklisted website already catches the website and the term is on the blacklisted keywords. Those need to be cleaned up first. In general, we prefer not to have the same exact thing caught by entries in both the blacklisted websites and blacklisted keywords. Basically, those need to be cleaned up, and the pilpedia\.?com limited, prior to blacklisting thepilpedia\.?com.
@Makyen That last entry should have been thepilpedia\.com. I haven't looked at why the current blacklisted website is pilpedia\.?com instead of pilpedia\.com, but that will need to be determined too, prior to making changes.
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, body starts with title and ends in url, pattern-matching product name in body, +3 more (588): vitalcrown.com/keto-fuel/ by rayonehoe on wordpress.SE
@Makyen That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; append -force if you really want to do that.
