@dorukayhan You are not a privileged user. Please see the privileges wiki page for information on what privileges are and what is expected of privileged users.
> Blacklisted username, offensive body detected, offensive title detected ---------- Title - Offensive keyword: *fucker* Title - Position 1-5: fuck Post - Offensive keyword: *fucker* Username - Position 1-7: fucker
> Bad keyword in body, bad keyword in title, bad keyword in username ---------- Title - Position 1-11: skin serum Title - Position 1-11: skin serum Body - Position 1-11: skin serum Username - Position 1-11: skin serum
> Would not be caught for title, body, and username.
[ SmokeDetector | MS ] Bad keyword in title, bad keyword with email in body, blacklisted website in body, repeated URL at end of long post: ONLINE ORACLE ADF TRAINING by Aakarshan5544 on stackoverflow.com (@dorukayhan)
[ SmokeDetector ] URL in title, bad keyword in body, bad keyword in title, link at end of body, link following arrow in body, pattern-matching website in body, pattern-matching website in title, repeated URL at end of long post: newhealthsupplement.com/garcinia-slim-fit-180/ by blanchedonald on workplace.stackexchange.com
@ArtOfCode how are the tokens only vulnerable for only 10 mins? Isn't the same token used for all subsequent flags even 10 mins after the token was retrieved?
[ SmokeDetector | MS ] URL-only title, link at end of body, link following arrow in body, pattern-matching website in body, pattern-matching website in title: elevategffacts.com/soleilglo/ by gilliamtyb on askubuntu.com (@ThomasWard)
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body, repeated URL at end of long post: Right of approaching Weight Loss by tamolvin on askubuntu.com (@ThomasWard)
@DrMcMoylex Body - Position 1024-1039: itutorindia.com
fp- by tripleee
[ SmokeDetector | MS ] URL in title, link following arrow in body, pattern-matching website in body, pattern-matching website in title, repeated URL at end of long post: phytolyft.com/soleilglo/ by rolumuda on puzzling.stackexchange.com
[ SmokeDetector | MS ] URL in title, bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body, pattern-matching website in title, repeated URL at end of long post: musclegainfast.com/max-testo-xl/ by nerita786 on drupal.stackexchange.com
@tripleee with that one I said fp, since you could remove the swear word and you would still have a post. Maybe NAA, but still not red-flaggable. I would have said edit it
[ SmokeDetector | MS ] URL in title, bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body, pattern-matching website in title, repeated URL at end of long post: t-rexmuscleadvice.com/max-testo-xl/ by hailey28 on drupal.stackexchange.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, link following arrow in body, pattern-matching website in body, repeated URL at end of long post: The Best Weight Loss Product by JudyBewoody on graphicdesign.stackexchange.com
tpu- by Glorfindel
Backoff received of 10 seconds on request to questions/269228;268176?site=electronics at 09:07:57 UTC
meeh I have decided to not report anything, since I'm working with the NatoBot, that is not a spam bot, but I still like to help you guys to feed your bot.
I'd be happy to give them to you here if you like. You've brought up quite a few spam posts before, and it would probably be a lot better for you if you were able to report them yourself.
We like to keep a very low profile for NatoBot know, hence moderators are always involved in what it reports (NAA and VLQ flag) and if spam we involve this chat room, I hope you do not mind
it whould we useful if Smokey could display different notifications for "hand blacklisted" (known troll etc) vs "coincidentally blacklisted" (somebody clicked "true positive" and the user got blacklisted as a precaution)
Over the last several days, we've been seeing a novel trolling attack on Super User: a flood of answers containing plagiarized content posted by a user called "Marlin Woods":
The user creates a new account for every post; however, the same Gravatar appears on each post so it's apparent that it...
@tripleee well, usually 'hand-blacklisted' users are done by filters (like the one above - username was blacklisted rather thant user), whereas the tpu- blacklists are per-user and are not carried between Smokey hosts (whereas usernames are). You can tell which it is by the reason - Blacklisted user for tpu- etc, Blacklisted username/keyword/website if it was hand-blacklisted
Of course, you can blacklist a user manually, but that is pretty rare
On an unrelated note, I think this line from smokey really demonstrates how fluent python can be: if site in sites and reason not in specialroom["unwantedReasons"]:. It reads like english.
I'm currently facing an interesting situation. While I personally don't mind facing the risk of seeing a well-oiled dude holding some pills, I'm currently at a public place, screen facing the passageway, with kids roaming occasionally.
@angussidney not the tokens, the 7-digit codes. The tokens are permanently sensitive, yes - but they can only be fetched using the 7-char code, and that can only happen within 10 minutes of their creation - hence, the 7-char only presents a token-access vulnerability for the first 10 minutes
@tripleee MySQL flavor
@JanDvorak and yes, yes we are
because they don't actually reveal anything important
TypeError: Cannot read property 'getElementsByTagName' of null
at p (onloadwff.js:1572)
at onloadwff.js:1573
at HTMLDocument.<anonymous> (onloadwff.js:1573)
Over the last several days, we've been seeing a novel trolling attack on Super User: a flood of answers containing plagiarized content posted by a user called "Marlin Woods":
The user creates a new account for every post; however, the same Gravatar appears on each post so it's apparent that it...
