@K.Dᴀᴠɪs this time around I was forced to enter my login info into the config file, which I grudgingly did... turned out I had mis-remembered one of the parts of the password -_-
[ SmokeDetector | MS ] Url-only title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +8 more (1,088): evaherbalist.com/paltrox-rx/ by Qzhfgozg on askubuntu.com
Is it applicable/viable/considerable to raise 6 autoflags for spam posts with reason weight > 1 K threshold to nuke them in seconds? Also I didn't found any search option for reason weight yet.
@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 While that might be reasonable, I think that, politically, we're still quite a ways from having that happen. My expectation is that we'll move to five flags, at some point, on posts that are 99.(some # of 9s)% likely to be spam. Once that's been in place for a while, people might consider moving to 6 flags. However, there's a lot of resistance to moving closer to being completely automated. There's been a lot of resistance to moving to 5 autoflags. There was a bit less resistance to 4.
@Makyen I proposed these measurement thresholds: 180-300 = 3 autoflags, 301-500 = 4 autoflags, 501-999 = 5 autoflags, 1000 or more = 6 autoflags (auto-delete, only if contained blacklisted websites). I know there exists some resistance effort to nuke spam posts by completely automated flags i.e. in status quo, also considering false positives which autoflags should be retracted.
@tripleee 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.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, body starts with title and ends in url, pattern-matching product name in body, pattern-matching website in body, +1 more (490): Jubile Skin Cream by KittyPaul on wordpress.SE
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching website in body, potentially bad ns for domain in body, +2 more (395): Keto One Reviews by aplozmajdsa on superuser.com
You get banned for throwing in links to unrelated stuff and so you post new questions with links to the same unrelated stuff ...? You really need to review the help center or simply find a different site if you don't like the rules here. In the meantime, I removed the spammy link. This is probably still too broad and possibly off-topic. — tripleee16 secs ago
I'm keeping my flag on it regardless. Will see what happens.
He did acknowledge that that he's doing something wrong because he was banned. And then his repo on github is crapExchange - so he has something against the site anyway
they are alluding to a third account as well, the sock puppetry was already evident but sock puppets are fine as long as they are not found to be upvoting themselves
[ SmokeDetector | MS ] Blacklisted website in body, pattern-matching website in body, potentially bad ns for domain in body (198): Elixir De Beaute UK by qapsamas on apple.SE
tpu- by Tetsuya Yamamoto
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching website in body, potentially bad ns for domain in body (393): Normal dietary supplements by Hnwwdcwk on drupal.SE
@tripleee 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.
@tripleee 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.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching product name in body, +1 more (516): Testo drive 365 canada by user370032 on meta.SE
@tripleee 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.
@Makyen well, Ubuntu 16.04 -> 18.04 on a 4 year old laptop can be a headache
i couldn't do in-place upgrade because it exploded
so i had to blast it and start over
and worst case i could've restored the .img directly to disk
but it's working well now
over 8 hours of work to restore data though
and the full disk image is from the 6th but there isn't any 'new' data between the 6th and 8th that was ultracritical or missing that I can't recover lol
@ThomasWard Sluggish response to commands is one of the symptoms we've been seeing of the most recent spat of problems. OTOH, it can just be chat rate limiting.
