Although looking at the view code, it doesn't look like there's anything which would cause that to happen by default, which suggests that there's some sort of issue with the helper code which automatically detects which category a page is categorised under
@SmokeDetector This is suspicious. There are a total of 8 hits for this domain on SE. 7 are on SO. 6 of those are by this same deleted user. The other one is an answer this deleted user edited, but didn't add the domain when they edited. The 8th is by a deleted user on SharePoint. That post is at best link-only NAA. All of these are from a short period of time, really 4 discrete times in 2016: 05-24(1), 05-25 (5), 06-03(1), 06-19(1).
I have not yet checked to see if the site is still active. Nor have I checked if there is plagiarism, although I wouldn't be surprised.
@Shree There's side-channel communication on Keybase.
@Shree 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-only title, bad keyword in body, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, +6 more (792): newsletterforhealth.com/rapid-slim/ by jurgenlowe on askubuntu.com
@SmokeDetector f Looks like a legit question, especially since the link has an SSL error (a spammer would make sure that the website works before you try to spam it).
@angussidney The answers appeared relevant to the questions they were on. All but the one on SharePoint appeared to be actual attempts to answer. Some were significantly upvoted. The one non-deleted user claims ownership of the site in their profile. Given that the users who posted all but one of the answers have already been deleted, I chose to treat the links like the dead links they are and just go through and remove them.
Normally, I'd change dead links to archive.org versions, which do exist for at least some of these, but it seemed better to just remove them in this case.
A mod flag is probably a good idea. They could keep an eye on the user that's still in existence. Given that the deleted user edited the existing user's post, I suspect the deleted user was deleted due to sock-puppetry.
[ SmokeDetector | MS ] Bad ip for hostname in body, bad ip for hostname in title, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, +3 more (400): order4trial.com/keytone-diet/ by laohlim on graphicdesign.SE
[ SmokeDetector | MS ] Bad ip for hostname in body, blacklisted website in body, body starts with title and ends in url, link at end of body, potentially bad ns for domain in body, +2 more (399): Keytone Diet t agent is useful in dissolving by helamaxk on askubuntu.com
[ SmokeDetector | MS ] Url in title, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, pattern-matching website in body, +3 more (691): healthprouds.com/omegagro-hair/ by user166986 on wordpress.SE
[ SmokeDetector | MS ] Url-only title, bad keyword in title, blacklisted website in title, potentially bad ns for domain in title, potentially bad keyword in body, +1 more (300): awaretalks.com/ez3-keto/ by karinsleshsa on askubuntu.com
tpu- feedback received
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, body starts with title and ends in url, pattern-matching website in body, potentially bad ns for domain in body (391): So with the help of KetoGenic Enlivening by sdfjfdy on puzzling.SE (@Mithrandir)
tpu- feedback received
[ SmokeDetector | MS ] Bad keyword in body, body starts with title and ends in url, pattern-matching product name in body, potentially bad ns for domain in body, potentially bad keyword in body, +1 more (295): Amalfitana Cream by LiceNike on wordpress.SE
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, potentially bad ns for domain in body, potentially bad keyword in body (197): Wifi unavailabale error by Holistic91 on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad keyword in username, link at end of body, pattern-matching product name in body, +6 more (684): What is Purefit Keto uk? by Purefit Keto UK on askubuntu.com
[ SmokeDetector | MS ] Bad keyword in body, pattern-matching product name in body, pattern-matching website in body, potentially bad ns for domain in body, potentially bad keyword in body, +2 more (295): What is Purelife Keto Reviews? by Pure life Keto reviews on askubuntu.com
tpu- feedback received
@Videonauth Post 1: Already recently reported [ MS ]
[ SmokeDetector | MS ] Url-only title, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, link at end of body, +4 more (695): livesmartt.com/keto-flex-diet/ by hattichkau5 on askubuntu.com
[ SmokeDetector | MS ] Url-only title, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, link at end of body, +4 more (695): livesmartt.com/keto-flex-diet/ by hattichkau5 on askubuntu.com
@TuringTux Registered question as true positive. If you want to blacklist the poster, use trueu or tpu.
@TuringTux Registered question as true positive. If you want to blacklist the poster, use trueu or tpu.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, potentially bad ns for domain in body (294): keytone diet Diet! by nommkom on drupal.SE
@double-beep That pattern looks like it's already caught by Bad keyword in body, Bad keyword in answer, Pattern-matching website in body, and Pattern-matching website in answer; append -force if you really want to do that.
[ SmokeDetector | MS ] Url-only title, bad keyword in body, blacklisted website in body, blacklisted website in title, body starts with title and ends in url, +6 more (891): livesmartt.com/keto-flex-diet/ by eritn201 on askubuntu.com
@Makyen Unsure when and how I changed it, but instances died on their own should generally recover themselves in 6 hours, unless something else prevents them from starting (e.g. host or container died altogether).
They're usually not really "dead", but still running standby, failing to ping MS, at least for my EC2 one.
