@SmokeDetector Approx 150 hits on SE, and also catches a legit website. Replacing with a pattern that catches only the hashtag phrase that was originally found in spam, and avoids catching the website.
@SmokeDetector I can't find any affiliation, but user has posted several links to the blog on Quora in the last few weeks quora.com/profile/Munish-Yadav-55. Watching the domain in case it shows up again.
@tripleee That pattern looks like it's already caught by Blacklisted website in answer and Blacklisted website in body Append -force to the command word(s) if you really want to add the pattern you provided.
@tripleee I don't have too much of a problem with making it easier for you or other humans to post "still alive" messages (although, I have disagreed with red-flag nuking a few of the posts which have gotten "still alive" messages in the past). OTOH, posting such messages does move us closer towards being a voting/flagging ring. Given the typical post content, I don't think most people will have a problem with that, but it is a general concern.
I do, however, have concerns with having such messages posted automatically. My primarily concern is that it's relatively difficult to programmatically determine which posts should receive such additional attention with 100% accuracy. If such messages are coming from SD or MS, then it seems to carry substantial additional weight wrt. other people making the decision to red-flag it, or not, particularly if we permit posting repeated messages.
Thus, the criteria for which ones to post automatically would need to be fairly sure to have a very high accuracy for choosing posts that really should be red flag nuked.
As to making it easier to post "still alive" messages: If you're interested, the following is a bookmarklet I use to create "still alive" messages. To use it, click "reply" to the SD message containing the report for the post you're wanting to post a "still alive" message for and then activate the bookmarklet (i.e. activate the bookmarklet when there's just the ":<chat message id>" text in the chat input area):
Overall, I'd rather focus on getting the MS recent posts page to where it's possible for users to filter it to, effectively, display such posts (e.g. those reports that have gotten TP feedback with no FP feedback, are unedited, and aren't deleted, along with other filtering options).
While that might not be as effective as posting a "still alive" message in chat for a particular post, it feels like it would be a bit further from being a voting/flagging ring.
Yeah, many of the changes I've made to MS over the last while have been intended to make it easier to have lists of posts on MS, like the recent posts page, be more "alive" and simplify sorting and filtering. There's still a considerable distance to go, but there has been some progress.
The quota_remaining property was not in the API response. Error: no method found with this name at 14:53:52 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
The quota_remaining property was not in the API response. Error: no method found with this name at 14:53:56 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 14:54:12 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 14:54:27 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 14:54:41 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 14:54:56 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 14:55:17 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions?site=stackoverflow.com
!!/report superuser.com/a/1471033 "The owner of the company is promoting his own product. linkedin.com/company/docuclipper linkedin.com/in/jorgemarsal - Sergiy Tytarenko, no disclosure"
@tripleee That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
@Mast why do you think it is spam? I thought so too at first at quick glance, but it's a support question, after the initial "we are launching a business and urgently need" blah blah
@SmokeDetector User has posted 11 answers in quick succession promoting this project, which they look to be affiliated with. I've custom flagged it (since it's probably semi-relevant to not malicious)
@Ethan To avoid SmokeDetector reporting posts too slowly, you can report at most 5 posts at a time. This is to avoid SmokeDetector's chat messages getting rate-limited too much, which would slow down reports.
@Ethan The !!/blacklist command has been deprecated. Please use !!/blacklist-website, !!/blacklist-username, !!/blacklist-keyword, or perhaps !!/watch-keyword. Remember to escape dots in URLs using \.
@Ethan The regex contains an unescaped ".", which should be "\." in most cases. Append -force to the command word(s) if you really want to add the pattern you provided.
