-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tellable should respond to private messages #374
Comments
Btw, looking at A valid PCRE for valid nicks not including Unicode extensions is:
And the Unicode extensions (which should be pretty easy to add in Raku) are shown here. |
Actually, that last comment doesn’t belong here. I’ll promote it to its own issue. |
Yes, tellable6 should start responding to private messages. It's blocked by default here because there are all kinds of damage you can do via private messages (in case of tellable it can be something stupid like sending a message to each user on the channel resulting in annoying bot spam). Better safe than sorry, but in case of tellable6 we should probably be a bit more permissive. As for normalize-weirdly, it's designed to be that way. For example, it's so that when you send a message to |
I'm pretty sure this is now working (some bots will start responding to private messages after they're updated). Tests needed. |
Since you have to mention the nick if you want to
.tell
, if the user leaves themselves afk on the channel, you take the risk of setting off a sleepytime notification in simply mentioning them in the.tell
. So I’d suggest either:irc-privmsg-me
so that you can/MSG tellable6 tell nick@channel …
; ornormalize-weirdly
to strip out tildes (~
), which are not allowed in nicks. Then you can do.tell trey~harris
or some-such to keep the channel from ringing the user.I’m capable of submitting a PR for either if you want to just select one. Thanks!
The text was updated successfully, but these errors were encountered: