@DavidPostill I think this post on RPi SE is probably spam. It does seem related to the question, but they proceeded to spam their site one minute later, so even though it was related, that makes me think it is more spam
@SmokeDetector This was voluntarily removed but I'm pretty convinced this and their other answer are both spam as it is the only thing they promote and they (blatantly, IMO) spammed it in a dedicated question and then tried to hide it
@cocomac 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.
PR#7220 ("cocomac: Watch google(?:\.[a-z\d]++){1,2}/url\?q=https?://(?!(?:www\.)?(?:google.com|(?:(?:[a-z\d]++\.){0,2}(?:stack(?:exchange|overflow)|superuser|serverfault|askubuntu|stackapps)\.com|mathoverflow\.net))[/\s"'<])") opened by SmokeDetector
@Makyen HTTPSConnectionPool(host='api.github.com', port=443): Max retries exceeded with url: /repos/Charcoal-SE/SmokeDetector/pulls/7219 (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f6a09963bb0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))
PR#7221 ("cocomac: Watch google(?:\.[a-z\d]++){1,2}/url\?q=https?://(?!(?:www\.)?(?:google\.com|(?:(?:[a-z\d]++\.){0,2}(?:stack(?:exchange|overflow)|superuser|serverfault|askubuntu|stackapps)\.com|mathoverflow\.net))[/\s"'<])") opened by SmokeDetector
[ SmokeDetector | MS ] Bad ip for hostname in body, bad keyword in title, potentially bad asn for hostname in body, potentially bad keyword in body, potentially bad keyword in title, +1 more (201): Whatsapp marketing services in chennai by viria India on stackoverflow.com
[ SmokeDetector | MS ] Bad ip for hostname in body, bad ns for domain in body, link at beginning of body, potentially bad asn for hostname in body, potentially bad keyword in body (237): Belkin Router Login Process by Belkin Router Login on stackoverflow.com
@JeffSchaller That pattern looks like it's already caught by Blacklisted username Append -force to the command word(s) if you really want to add the pattern you provided.
@cigien That pattern looks like it's already caught by Blacklisted username Append -force to the command word(s) if you really want to add the pattern you provided.
@cocomac @RobertLongson Congratulations! You are now a blacklist manager. You should run !!/amicodeprivileged to verify and force SD to update its cache of permissions. You may need to do that on each SD instance, depending on when each SD instance updates its cache of those permissions.
Fully adding you as a blacklist manager is a bit of a process. A portion of the privilege is additional access on GitHub. You will need to accept the GitHub invitation to the Charcoal-SE/SmokeDetector repository and OAPs group which I've sent to the GitHub account you have publicly linked on Stack Overflow. If you prefer, you can have us use a different GitHub account, but you'll need to tell me.
After you've accepted, I'll need to make another couple of changes, so please ping me once you have accepted that invitation. Accepting the invitation and joining the Charcoal-SE organization on GitHub isn't required, but is necessary for some functionality on GitHub.
I've also given you the Core role on MS, so you'll see a bit of additional functionality on MS. This is mostly in the "core" dropdown menu from the topbar.
Quick question: some watches can be done easily and tend to not have much debate (say, a website that has one TP and no FPs). Those I can just do. For ones that are more subjective (like regexs to match complex things), and I want a second opinion is it better to ask here? Or manually send a PR on GH and discuss there? Or something else?
@cocomac Yes, all of the above. Which route to take for more complex regexes is going to depend on how much discussion you feel they might need and how complex they are. Obviously, if they are too complex to fit in a chat message, then they have to go through the PR process.
I'm glad that you are still planning to have more complex regexes discussed and would appreciate that you continue to do so.
@Mast The pattern is a blogspot watch but keeps the TLD, in most cases this should be removed. Append -force to the command word(s) if you really want to add the pattern you provided.
@Spevacus BTW: we normally watch blockspot domains without the TLD, because Blogspot has a domain named "blogspot.*" in almost every TLD, which can be used to get to the user's subdomain. So, this would normally be: !!/watch- drabu7demonspells\.blogspot. It's not a big deal. It's just something to keep in mind. It took a few reminders for me to start remembering to do it. :)
I'm going to link to the following, so want a copy of it that's more generic:
We normally watch Blogspot domains without the top level domain (TLD), because Blogspot has a domain named "blogspot.*" in almost every TLD which can be used to get to the user's subdomain. So, watch/blacklist entries for blogspot subdomains would normally be: !!/watch- <subdomain>\.blogspot, where <subdomain> is the spammer's site/subdomain. It's not a big deal, but we do prefer it, so it's something to keep in mind. It took a few reminders for me to start remembering to do it. :)
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 18:20:10 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 18:20:47 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 18:21:02 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions
The quota_remaining property was not in the API response. Error: Violation of backoff parameter at 18:21:16 UTC. Backing off on requests for the next 12 seconds. Previous URL: https://api.stackexchange.com/2.2/questions
@Papershine Just FYI: In updating your GitHub username with respect to your blacklist manager privilege here, I noted that your SO profile links to a no longer existing GitHub account name. If that's what you're wanting, there's no need to change it. I just figured you'd want to know, as I would want to know if it was my profile.
