@Vickel I think @tutanota\.com is fine; an email address should always have a word boundary there, and that's what we're looking for. It's stuff other than emails that isn't spammy.
Also, for performance reasons, you don't want to start a pattern with a backreference
@RyanM seems to me to be happening in the {!r} of the formatted string. That conversion to a "repr" thing is new to me, but it looks like it's interpreting an email-looking string as something that should be mangled a bit. github.com/Charcoal-SE/SmokeDetector/blob/master/… Line 1744 ish
@Makyen It appears that commands containing strings that look like emails are broken.
For bisect, it seems as though it's actually searching the string [email\xa0protected] (the latter of the bisects above is something you watched recently, so I'd expect a hit).
@JeffSchaller (you probably meant line 1716, but...) I don't think so; Python itself does not, as far as I'm aware, have any features to protect emails from appearing in output
Python 3.9.6 (default, Feb 3 2024, 15:58:27)
[Clang 15.0.0 (clang-1500.3.9.4)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> print("{!r} is not caught by a blacklist or watchlist item.".format("[email protected]"))
'[email protected]' is not caught by a blacklist or watchlist item.
@Makyen This double-detects what's already detected by an existing blacklisted keyword: (?:\w*hack[\W_]*+(?:\w+[\W_]*+)?(?:at[\W_]*+)?|\w+(?:@|(?:at[\W_]*+)))tutanota[\W_]*+(?:dot[\W_]*+)?com(?#XXX)
@Makyen 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.
@Makyen 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.
> Bad keyword in body, bad keyword in title, bad keyword in username ---------- Bad keyword in body - Position 0-8: VO2P1RYP Bad keyword in title - Position 0-8: VO2P1RYP Bad keyword in username - Position 0-8: VO2P1RYP
@RyanM Yes, that's what's happening. To get the, supposedly actual, contents of the message, rather than the contents which might be adjusted by the chat system, we use the ChatExchange's .content_source property of the message. To get that content, ChatExchange fetches and scrapes the message's history page. Cloudflare is, currently, applying their email protection. The HTML is delivered with the email address masked. They then use JavaScript to unmask the email addresses. Given that we don't, obviously, run Cloudflare's /cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js, the email addresses aren't unmasked.
That Cloudflare does this makes me wonder what else they might be doing to the message content and under what conditions.
OK, being logged out suddenly sucks. I don't even get why/how it's happening. I got logged out yesterday. And again just now. Just moments before I was logged out I even refreshed a tab for chat where I was logged out. Refreshing did show me logged in. I came here to CHQ and tried to give feedback through FIRE only to get logged out again.
Logouts have been happening more frequently "recently" (hard to determine exactly when but at least half a year). Before that I also can scarcely remember being logged out.
It might be complete conjecture but seems I get even more logouts even more recently. Last couple of weeks or so.
Before that I'd get logged out maybe once a month. Maybe a bit less. So, it happened, not often. But twice in two consecutive days is new.
I, also, have been logged out more frequently recently. I keep a lot of tabs open with various state information, both chat and main/meta pages. I don't like having to reload the pages after being logged out. It's been sufficiently often lately such that I've been considering writing a userscript that would pass the appropriate information to the older tabs once I've had to re-login.
@Nick In order for a "number" to make an exact match, the pattern must begin with a digit or up to two of +,(,[, or { immediately followed by a digit. Append -force to the command word(s) if you really want to add the pattern you provided.
[ SmokeDetector | MS ] Bad ns for domain in body, bad keyword in link text in body, blacklisted website in body, potentially bad keyword in body, potentially bad keyword in title (268): What is BR Softech? by Lohitaksh Verma on superuser.com
