@iBug I just don’t want the folks on the list to be used for random translation tasks.
I suggest using a machine translator since they can sometimes/often give a result that’s good enough to determine whether the post is spam and if so, which keywords to watch.
Picked up an Apple Watch a few days ago. Despite being totally "not a watch person", it's completely awesome and I should have got one years ago
Took it off just now to charge it and had to actually type my password into my laptop like some kind of neanderthal. Just that feature alone is worth it
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 1-19: data-flair.training Body - Position 1-19: data-flair.training Username - Position 1-19: data-flair.training
@tripleee 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.
@tripleee That pattern looks like it's already caught by Blacklisted website in answer, Pattern-matching website in body, Pattern-matching website in answer, and Blacklisted website in body; append -force if you really want to do that.
@TetsuyaYamamoto 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.
Which best option should I choose to flag 'spam comment'? For example, user 'X' posts legitimate post, but includes spammy link as comment for his own Q/A.
@tripleee That pattern looks like it's already caught by Bad keyword in answer, Bad keyword in body, Pattern-matching website in answer, and Pattern-matching website in body; append -force if you really want to do that.
[ 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 keyword in body, +1 more: Legendz xl With tablets you will by user10378729 on stackoverflow.com
@Shree 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.
@Shree There are standards for under what conditions it's appropriate to blacklist. Please see Guidance for Blacklisting and Watching. That particular site only has 2 TP on MS, which is a bit soon to be blacklisting.
@undo FYI: I've started to get "Internal Server Error" with sub reason "Can't connect to MySQL server on '127.0.0.1' (115)" responses and timeouts on a variety of normal MS API inquiries. It appears to be load related. This might be a run-up to MS having CPU load related issues.
@Ferrybig Clicking multiple times isn't a good idea. Each time you click it fires off additional requests, which should just error-out, as you can't duplicate feedback (you can send different feedback, but not duplicate) and you can't re-flag. Thus, that just increases the number of requests which MS has to handle.
@Makyen I needed to click the last report 3 times for feedback, because FIRE kept saying that the request made an error (and the status of the request according to the network tab in Google Chrome is 'cancelled' after 10 seconds
@Ferrybig Ah, I misinterpreted what you were saying. I understood it as clicking multiple times in succession just because things were slow (i.e. without waiting for an indication that the requests actually failed). Your more detailed statement sounds reasonable.
@TetsuyaYamamoto We've just been talking about MS exhibiting that type of error. It's something that has been happening periodically since the change-over to MariaDB. It's a problem that's still being looked into.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching website in body, +1 more: phendora garcinia south africa by wefezoro on meta.SE
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at end of body, pattern-matching website in body, potentially bad ns for domain in body, +1 more: The Appeal Of Man Power Booste by amyfriends on askubuntu.com
@TetsuyaYamamoto That pattern looks like it's already caught by Blacklisted website in answer and Blacklisted website in body; append -force if you really want to do that.
@TetsuyaYamamoto That pattern looks like it's already caught by Blacklisted website in body and Blacklisted website in answer; append -force if you really want to do that.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, pattern-matching website in body: Ropaxin T The maker of the by goldarnolpnw on graphicdesign.SE
Title - Position 9-30: greenlifenutrition.org Title - greenlifenutrition.org NS suspicious dns2.namecheaphosting.com.,dns1.namecheaphosting.com. Title - Position 18-30: nutrition.org Title - Position 1-30: https://greenlifenutrition.org Body - Position 328-336: impotence, Positions 652-664, 728-740: jimdosite.com Body - Position 353-357: penis Body - Positions 470-491, 555-576: greenlifenutrition.org Body - greenlifenutrition.org NS suspicious dns2.namecheaphosting.com.,dns1.namecheaphosting.com.
@iBug 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.
[ SmokeDetector | MS ] Url-only title, blacklisted website in body, blacklisted website in title, pattern-matching website in body, pattern-matching website in title, +2 more: www.bluesupplement.com/legendz-xl/ by veilamera on askubuntu.com
@TetsuyaYamamoto That pattern looks like it's already caught by Pattern-matching website in body and Pattern-matching website in answer; append -force if you really want to do that.
