@RyanM That's good to know. Please submit a PR to Sam's repo which fixes it. Using .innerHTML is rarely the correct choice in a usescript to modify existing page content, as it's destructive of existing JavaScript interactions with the page. Sometimes it is necessary, but it should be avoided, if possible. When used, it should be applied to the minimum possible. I don't use Sam's Chat Improvements, because it does things I don't like and conflicts with other userscripts I use.
As to that particular code, the way that's being handled there is ... inappropriate and nearly guaranteed to have conflicts. Basically, that script should be walking through the text nodes within the .content and replacing only #text nodes to wrap the text in a span, rather than replacing the entire .content element. If you want it, I have examples of code which do such replacements it in a manner which isn't destructive.
To do it right, you have to use basic JavaScript, as jQuery doesn't handle #text nodes all that well. To walk through the nodes, a document.createNodeIterator() or document.createTreeWalker() should be used.
The examples include code in the Request Generator, Archiver, FIRE, MagicTag2, (look for handleTextNode and/or createNodeIterator) and a few SO answers.
@Spevacus The pattern is a blogspot watch but keeps the TLD, in most cases this should be removed. Append -force to the command if you really want to add the pattern you entered.
Just FYI: I've moved my backup SD instance, Makyen/EC2-linux, from a low-end AWS lightsail instance to an EC2 (currently a t4g.nano) instance. This should have a couple of advantages for it as an SD instance: more CPU capability (2 vCPU instead of 1), and the amount of CPU credit available isn't hard limited (i.e. when/if failed-over to it should be able to be used indefinitely, rather than for only a moderately short period of time). The metasmoke SD instance was moved at the same time.
Yeah, the overall savings for going to a 36 month "all upfront" reserved t4g.nano instance vs. the lowest end Lightsail is 50% (note: disk cost is included in the calculations, but isn't paid up front, and could be somewhat reduced for even more savings). The savings for just the t4g.nano CPU instance comparing on demand vs. 36 month reserved is 60%.
There are differences comparing the t4g.nano to the Lightsail instance, but the things which you get more of with Lightsail (i.e. disk space; 20GB included in the lowest end Lightsail, but I assumed 8GB in the t4g.nano, as SD really doesn't need even that much) are things which SD really just doesn't need.
IMO, the big disadvantage of Lightsail, which I wasn't aware of when starting to use it, is that you can't purchase more CPU credits. You get only what accumulates from the unused baseline, and, like all of the AWS burstable instances, you can only accumulate up to 24 hours of accumulation.
That pattern may be a North American number. If it is, please use a format which starts with an optional `1` followed by possible separator text and has the main number in the format `735-848-2220` where `-` could be a single alpha character or any `[\W_]*+`. Alternately, you can add the comment `(?#IS NorAm)` to the end of the pattern to force also using the alternate normalized form, or `(?#NO NorAm)` if it's not a North American phone number and it's incorrectly recognized as one. Perhaps try
[ SmokeDetector | MS ] Bad keyword with email in answer, potentially bad asn for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer (88): Direct Message Selenium Instagram by jojo on stackoverflow.com
@Ollie That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command if you really want to add the pattern you entered.
Not much I can say about that, other than that the message exists and has never been edited. Sometimes, stuff happens. "meh" Now, you've seen it and have the information. :;
@Ollie Anything that qualifies as this "support number" nonsense can be deobfuscated and jump right to the blacklist. Given the unprecedented nature of the spam wave, immediately throwing them onto the blacklisted numbers list is the way to go.
@Ollie While I'm not going to object to that being put on the blacklist, the post it's from doesn't appear to be part of the "Support Number" spam (i.e. it's substantially different from those, so is likely from a different spammer/group of spammers).
@Ollie Yeah I wasn't paying close enough attention to the number you were referring to. That's also not something I would consider part of the support number spam wave. I was talking more so about this kind of spam.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, link at end of body, pattern-matching product name in body, potentially bad ns for domain in body, +2 more (461): viagra tablet price in pakistan,karachi by Osman Ali on superuser.com (@Ollie)
Hmmm... 41.6 times as many unchanged posts were encountered as the number of posts scanned. That's impressive, but not all that surprising, given that we fetch all "recent" posts.
teward/Osiris: In getting MS post information, recovered from requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='metasmoke.erwaysoftware.com', port=443): Read timed out. (read timeout=10.0)
reactnavigation.org is now the domain for the official documentation for react-navigation. Is there some way to keep smokey from catching every post which links to it?
@HenryEcker i think there's a whitelist mechanism, but a link anywhere will trigger a low-score warning I believe. It doesn't mean it's actually spam though, the site isn't blacklisted unless someone manually blacklists it so
