the public documentation generally avoids mentioning them by name but you should easily find dozens if not hundreds of similar posts in Metasmoke just by searching on the user name
@tripleee Wow! Thanks. I'll pay more attention to this user. Actually, I believe they appeared on Academia SE many times. I remember I caught them at least 3 times.
His signature is "Give me the bounty by x days" comment, then delete the account right?
@Makyen That pattern looks like it's already caught by Potentially problematic ns configuration in answer and Potentially problematic ns configuration in body; append -force if you really want to do that.
@scaaahu the number is small enough that you can just download the JSON from the Metasmoke search page and process it locally if you want to analyze it further
though I'm sure we could arrange with Blazer access for you as well if you think it would be useful
[ SmokeDetector | MS ] Url-only title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +8 more (989): nutritionless.com/zederex/ by zvnnddjr on askubuntu.com
@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.
@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.
@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.
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially bad keyword in answer, Pattern-matching website in answer, Potentially bad keyword in body, and Pattern-matching 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.
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +8 more (986): timesnutrition.com/trialix/ by ecyddemee on ebooks.SE
tpu- feedback received
[ SmokeDetector | MS ] Url in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +8 more (986): nutritionless.com/zederex/ by zvnnddjr on drupal.SE
@TetsuyaYamamoto 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 ] 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, +2 more (490): Nutra Surreal Keto by KarenMorrow on wordpress.SE
@tripleee The URL above this line causes an error for me, I have had that problem a few times. If it's caused by not having "Blazer access" may I have it enabled too.
@Rob the privileges are intertwined but I don't suppose there is any reason to give you access ... lemme look it up because I don't remember off-hand which privilege includes this
@tripleee 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.
@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.
[ SmokeDetector | MS ] Url in title, bad keyword in body, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, +4 more (659): www.jbngroups.com by bairons nainc on graphicdesign.SE
@tripleee The ability to: "Access to the SQL and JavaScript data explorers" and "... add/edit domain tags" looks useful; I'll read up on these features in the days ahead.
@JohnDvorak not sure what you mean, we could probably quite easily come up with something like "English words without grammar" but do we have many posts like that?
a good selection of tagged samples would be an excellent start
@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.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, body starts with title and ends in url, link at end of body, +6 more (789): Keto ultra diet south africa by weri menoi on meta.SE
@Rob we have a procedure for that but I'm not sure I recall exactly ... try stackoverflow.com/users/… but I' not sure what the precise requirements are
IIRC it will create a temporary email address where it receives the ack and then you can get it from there via your Metasmoke account
@Shree not yet spam IMHO, it could just be a misdirected newcomer ... and what benefit do they expect from spamming links to a well-established free service?
@tripleee - It says: "To confirm access to Charcoal, we need to verify that you have an email address from one of the following domains: @charcoal-se.org, @channel-verify.erwaysoftware.com" --- Do I have such an email address (news to me) are they assigned by default (I can look at my MetaSmoke profile, somewhere)?
@Rob the second one is the ticket but I'm hoping somebody else can fill in on how exactly you use that ... there's a limited set of addresses in that domain so it gets assigned to you temporarily
@TetsuyaYamamoto That pattern looks like it's already caught by Potentially problematic ns configuration in answer and Potentially problematic ns configuration in body; append -force if you really want to do that.
In the deleted as spam post the link to the revision history is bold styled:
You can check this one for an instance.
Is there a background to make such a link bold or merely an oversight?
BTW, if I recall correctly such links were underlined ever before changing the link style globally ...
@tripleee 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.