@EliahKagan That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
[ SmokeDetector | MS ] Few unique characters in body, no whitespace in body, no whitespace in title, repeating characters in body, repeating characters in title (391): ekekdkdkfffffffffffff ✏️ by michael on ell.SE
@EliahKagan That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@EliahKagan That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@EliahKagan That pattern looks like it's already caught by Potentially bad keyword in body, Pattern-matching website in body, Pattern-matching website in answer, and Potentially bad keyword in answer; append -force if you really want to do that.
@Machavity That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@EliahKagan That pattern looks like it's already caught by Blacklisted website in body and Blacklisted website in answer; append -force if you really want to do that.
@EliahKagan Matched by (?:customer|tech|technical)-?(?:support|service)(?<!photographerstechsupport)(?<!vbtechsupport)(?<!paypal-techsupport)\.com on line 1489 of blacklisted_websites.txt
IP address shuffling will be done in the next 7 days (through Feb 21 at the latest), at which point Metasmoke might blip out while DNS and other things are fully configured and propagated. Stay tuned for additional info.
Note: The issues we had with Travis CI failing for a day and a half appear to have been that the caches on Travis had become corrupted. The problems stopped when I manually cleared all the cached . If that needs to happen another time, I found it necessary to log into Travis as SmokeDetector, and delete all the caches on this page.
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, pattern-matching product name in body, potentially bad ip for hostname in body, potentially bad ns for domain in body, +1 more (296): Best Male Pills 2020 by mariaking113 on askubuntu.com
@Makyen That pattern looks like it's already caught by Pattern-matching website in body and Pattern-matching website in answer; append -force if you really want to do that.
@gparyani It will be difficult for SD to determine that the browser will render the title with zero, or very little, width. From SD's POV, that title has 27 characters, which it did include in its message. In order to determine that the link is not going to be displayed with enough width to be clickable, SD would need to know all possible ways for someone to include characters which will render with little of no width.
It's possible to know some of the more common ways that the OP might do this with titles, but a complete solution is difficult.
OTOH, it's relatively easy for a userscript to determine that the width of the link is "too narrow" (i.e. below some threshold). I already have something prototyped which does this for MS. It would be not that much work to have it done by FIRE or AIM. Would a userscript solution be acceptable?
Hmmm... That should probably be on the GitHub issue...
@Makyen from Python's perspective, though, we can have it check if the title contains only nonprintable characters (and replace the title if that's the case), and if it has interspersed nonprintable we can probably leave it as long as the length is longer than 0 displayable characters.
and we can add that to the Post class as part of how it needs to render/parse
@ThomasWard What was used in this case was a conditionally printable character, a soft hyphen. So, you need to know not just what is there, but also the width of the display area used for the message content. Yes, we can figure do better, but we would need to either find a module that does it for us, or take a swag at it and guess at what characters will be printable in the font the user happens to be using on that machine/OS/browser (all of which affect display-ability of different characters).
Yes, we can pick off some of the trivial titles (e.g. a title which is all soft hyphens), but a robust solution is definitely non-trivial to do outside the browser.
