I don't think so ... a 'iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii' within the grace period might be something like this or a vandalizing of the answer which we usually would roll back ....
I'm not sure I follow your reasoning. If you want to be disruptive, you'd post something like rude comments or a long copy/paste (witness W*D*) whereas misunderstanding the GUI easily results in accidental copy/paste of the thing you're looking at or typing into the wrong box. The latter is an honest mistake, not actively abusive, and surprisingly common among people who are not awfully masterful with the mouse
I guess it doesn't matter much from the mods' perspective but we want to avoid being too aggressive against users who are just not very good with computers
(I don't mean to imply that moderators don't care what perception we give users, just that rude vs vlq doesn't matter much for achieving the goal of getting the thing deleted)
Now I have problems to follow how this should happen accidentally ... I'll try, for sure I agree with avoid "being too aggressive", which I would see on those vandalized answers
ctrl-a ctrl-c (click) ctrl-v enter ... if you've ever had a control key stuck because you had marmalade in your keyboard you'd have experienced this first-hand a lot more
maybe a few ctrl-r ctrl-g etc in between there which didn't do anything, it doesn't have to be precisely that uninterrupted sequence
@Mithrandir sure, repeat offenders are a thing, but I see no indication of that here
we've all had things like this happen to us when the computer was lagging because some job hogged the CPU, you clicked something and shifted focus and the click landed in a different window when it finally made it through the event queue
so not necessarily just clumsiness or poor dexterity
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, link following arrow in body, +1 more: Hydraxil Use some sunscreen by tammywatson on askubuntu.com
@bummi here is a question answered both by Moeez (who is the author of that blog) and suthanalley (that answer is deleted). I'm going to ask the SO mods to find matching IP/PII. Then we know for sure.
[ SmokeDetector | MS ] URL-only title, bad keyword in body, blacklisted website in body, blacklisted website in title, link at end of body: www.kesamuroa.com/ by ChrisBaldwin12 on askubuntu.com
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, +1 more: Pinnacle Garcinia by Linda N. Parham on workplace.SE
@Glorfindel They are now working for me. GreaseMonkey is broken in 57.0. I'm using ViolentMonkey instead. You have to reinstall the scripts. Someone else has said that TamperMonkey also works.
@tripleee That pattern looks like it's already caught by Pattern-matching website in body and Pattern-matching website in answer; use !!/blacklist-website-force if you really want to do that.
@Mithrandir That pattern looks like it's already caught by Bad keyword in body and Bad keyword in answer; use !!/blacklist-website-force if you really want to do that.
[ SmokeDetector | MS ] URL in title, link at end of body, potentially bad keyword in body, potentially bad keyword in title: videoder.zone/ by StevdDavis on drupal.SE
@Federico That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; use !!/watch-force if you really want to do that.
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, bad keyword in title, bad keyword in username, blacklisted website in body, +2 more: Testo Rev Trial Review by Testo Rev on askubuntu.com
halflife:2017-11-15 12:26:45,902:http://goo.gl/LFL8Wu redirects to http://www.scytek.com/products/33.35-BBS-2-Gram-Stain-Kit-(Modified-Brown-&-Brenn).asp
didja see that or did you do the same thing manually?
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, bad keyword in title, blacklisted website in body, repeated URL at end of long post: The Fastest Way to Reduce Wrinkle by sdfgfs on graphicdesign.SE
[ SmokeDetector | MS ] URL-only title, bad NS for domain in body, bad NS for domain in title, bad keyword in body, link at end of body, +3 more: vyantixrxtry.com/ by hxgjrqung on askubuntu.com
@paper1111 That pattern looks like it's already caught by Bad ns for domain in body, Bad ns for domain in answer, Pattern-matching website in body, and Pattern-matching website in answer; use !!/watch-force if you really want to do that.
[ SmokeDetector | MS ] URL in title, bad NS for domain in body, bad NS for domain in title, bad keyword in body, pattern-matching website in body, +2 more: vyantixrxtry.com/ by user263986 on apple.SE
[ SmokeDetector | MS ] URL-only title, bad NS for domain in body, bad NS for domain in title, bad keyword in body, link at end of body, +3 more: proshredtestoreview.com/ by vdqnkpwuy on askubuntu.com
[ SmokeDetector | MS ] URL in title, bad NS for domain in body, bad NS for domain in title, bad keyword in body, pattern-matching website in body, +2 more: proshredtestoreview.com/ by isla jovingn on astronomy.SE
What's the current best practice for reproducing spam links in chat to discuss spam? Might it be best not to have the actual spammed link linkified here in chat, where the transcript is indexed by search engines, and so forth?
Scenario:
There's a spam post that's lingering on a site.
Someone links to the post in a chatroom, to attract more spam flags.
The post gets hammered off.
But the onebox of the post remains in the chatroom. Possibly including a link included in the spam.
A moderator can delete the chat messag...
@tripleee That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body; use !!/watch-force if you really want to do that.