@Mr.YouKnowWhoIAm Perhaps, but that doesn't justify plagiarism. In addition, they have linked to the same site in their most recent answer on SO. Their other two answers on SO link to a different site, but one that sounds like it would fit in with those we commonly see as spam.
My guess is that he thought that the question asked is somehow referring to search engines like Google, Yahoo, Bing, etc. and the main cause of traffic to Stack Exchange sites. (I think my guess is wrong, but that is the best I could come up with.)
@SmokeDetector While this might be in a format we would want to block, "no" is a potentially valid answer to the first question asked. However, it does not cover the additional portions of the question.
@Mr.YouKnowWhoIAm I certainly wouldn't call it a good answer. However, I'm more inclined to leave it up to the site's users to handle than for us to get involved. I agree that "no" is quite generic, but it is generally considered an answer, if the question allows for it as an answer. Personally, I consider the problem to be more the question. I may be missing some specific definition of "successive sequence", but I don't see anything that would disqualify any sequence from being valid.
@Makyen 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.
@Makyen That pattern looks like it's already caught by Bad keyword with email in answer, Potentially bad keyword in answer, Potentially bad keyword in body, and Bad keyword with email in body; append -force if you really want to do that.
@bmike Ahh... I had already pushed an update to one of the existing watches prior to coming back to the room and seeing this. Sorry about that. As a result, I'm going to just close the PR, but the posts will be caught.
@Mr.YouKnowWhoIAm We don't know. The reasons for a suspension are always private between the user and moderators. The only way such are know are either by the user saying why they were suspended, or based on what was seen by other users of that user's public conduct prior to the suspension. The only information we have is the minimal note that they were suspended to cool down.
@Mr.YouKnowWhoIAm If you mean why they would have created this MS post, they did so as a vandalism of their post, which, prior to the edit, was a valid question. Users usually do that because they want to delete the content, but their post does not qualify for the system to permit the user to delete it. Alternately, because they don't know how to delete it, most commonly because the delete button exists only in the webpage version not in the app.
@Undo So, in the actual post, where it says "'Click here for our <a href="https://example.com/daily-specials">Daily Specials</a>!'", "...it is already pointing instead to <a href="https://staging.example.com/daily-specials"></a> and displays...", and "any relative URLs (i.e. <a href="/daily-specials"></a>)", the links are actually shown in metasmoke.
@Mr.YouKnowWhoIAm Yes, the preview does not render that correctly.
The preview renders it as it is in the HTML which metasmoke receives, but that HTML has already been processed by SmokeDetector. The processing that SmokeDetector does to the HTML makes it impossible to accurately recover the original HTML in some cases. However, in the specific case of that post it can be recovered such that it displays correctly.
@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.
@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.
@SmokeDetector ^Spam seed, if you go into the profile of the user who posted that question, you can see that his profile also has a link to the spam domain that "his buddy" posted in the answers to that question
Post 1: Could not find data for this post in the API. It may already have been deleted. Post 2: Could not find data for this post in the API. It may already have been deleted.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad pattern in url body, blacklisted website in body, body starts with title and ends in url, +4 more (780): Livepure Forskolin by eslieanchez on drupal.SE
@SmokeDetector f Although interestingly, it appears that an edit was approved (!!!) which added in code from an unknown source (unless if it was from an answer which was deleted, but I can't see that)
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, pattern-matching product name in body, pattern-matching product name in title, potentially bad ns for domain in body, +2 more (396): Vital Max Keto! Buy Now by kokkhoh on drupal.SE
