@SmokeDetector This is exactly the type of answer which the question is asking for. The question is from a 4.7k rep user and does not appear to be spam.
@TetsuyaYamamoto @Cthulhu Please re-evaluate this postMS. While it does resemble a promotional post, it's actually exactly the sort of thing the question is asking for. The user has 4 other answers, none of which link other sites (a user objected to a "signature", but that was just their username). In addition, the user that asked is 4.7k rep and it doesn't appear to be a span seed. The
SD is now not reporting which user provided the first feedback of each type. Some context (and further discussion), some additional concerns: here through here, notably including this. You can still get user⬌feedback info on MS or from AIM.
[ SmokeDetector | MS ] Url-only title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +7 more (989): evaherbalist.com/androdna/ by Wkpzriya on askubuntu.com
@Cthulhu If you're going with this name, it would be helpful for you to also change your username on MS, so that the reported feedback matches and you can get pings from MS (e.g. FP on autoflagged post).
@Makyen The question itself is clearly not a spam seed, but I obliged with the answer itself. I kept on TP but retracted the flag, in case the opposite view wins.
@quartata While the user information in the in-chat report might help in that case for the first feedback, usually there's more than one feedback per post, so you have to get the info some other way in many/most cases.
@SmokeDetector 10k'er able to see if this post was deleted by OP? Just curious to see if he may have edited spam in during grace period (and that he is currently suspended)
[ SmokeDetector | MS ] Bad keyword in answer, blacklisted website in answer, pattern-matching website in answer, potentially bad keyword in answer, potentially problematic ns configuration in answer, +1 more (328): how to transfer IOS to router cisco by Tech HelpLine on askubuntu.com
I've noticed that the people who edit in spam after the initial post have plagiarized the post first to make an answer appear legitimate. The answer is sometimes from a completely different programming language too - and it's always been done on 1+ year old questions that will likely not be caught for a while
The number watch really should automatically handle the optional 1 on US numbers. We should only need to watch one of 1-888-621-0339 or 888-621-0339, not both.
An XSS vulnerability and a data validation bug exist in Stack Overflow Teams that can be used together to trigger a XSS against teammates. This isn't very exploitable in practice.
When you are joining a new team, the "Full Name" field isn't subject to the same character restrictions as it norm...
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +7 more (986): evaherbalist.com/androdna/ by Wkpzriya on drupal.SE
@K.Dᴀᴠɪs 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 ] Bad keyword in body, blacklisted website in body, link at end of body, pattern-matching product name in body, potentially bad keyword in body (395): excess weight It again by alinehing on drupal.SE
[ SmokeDetector | MS ] Url in title, body starts with title and ends in url, potentially bad ns for domain in body, potentially bad ns for domain in title, repeated url at end of long post (295): getmagnetiques.com/sera-chews/ by notfg jamu on 3dprinting.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, pattern-matching product name in title, +3 more (593): kingofsupplement/max-keto-burn/ by Mia on graphicdesign.SE
@K.Dᴀᴠɪs 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 ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching product name in body, pattern-matching product name in title, +2 more (592): Therma Trim Weight Loss by mamdooad on apple.SE
@TetsuyaYamamoto 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.
@TetsuyaYamamoto That was already watched. That's what "That pattern looks like it's already caught by Potentially bad keyword in {}" means. Please don't !!/watch-force when you see that detection reason when you try to !!/watch.
@Makyen Usually it raises warning "already watched in line XXX in watch_keywords.txt", but for some reason not showing up. The force is just a test to see if the watch mechanism working as intended.
@TetsuyaYamamoto Unfortunately, the checking for "already watched in ..." only looks for exact matches to the entire regex being added. The watch that already included eventbrite\.com also has a (?#comment), which makes the exact match fail, so there's no "already watched in ..." rejection, even though it's already detected. Having that test ignore comments is already a feature request on GitHub.
but even then there are variations like \W* vs \W? vs \W+ which easily allow you to submit effectively a duplicate even if it is nominally slightly different
in the general case you can't really figure out if two regexes are equivalient
and the near-equivalent case makes it even harder
so we don't even try particularly hard
you should probably avoid -force unless you can argue why exactly the checks should be bypassed
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, pattern-matching product name in body, pattern-matching website in body, +1 more (491): Alvera Tone Cream Australia by ZoraJames on wordpress.SE
@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.
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 0-26: spycheatingplayingcard.com Body - Position 0-26: spycheatingplayingcard.com Username - Position 0-26: spycheatingplayingcard.com
An XSS vulnerability and a data validation bug exist in Stack Overflow Teams that can be used together to trigger a XSS against teammates. This isn't very exploitable in practice.
When you are joining a new team, the "Full Name" field isn't subject to the same character restrictions as it norm...
