Dan Boger

Tracking nick changes is really a 'best effort' kind of thing, since unless we only look at registered nicks, we cannot possibly hope to keep up. honestly, not sure what...

I think I'd be for stripping control chars everywhere. If we want to be fancy, we can limit that stripping from the trigger side, and still allow it on the...

I can see the argument saying 'literal ' should be an alias to 'literal[*] ', but I wonder how many false positives we'll hit there. Another option would be to...

Yeah, that seems to be a bug, no reason to ignore actions in PM. On Mon, Sep 19, 2016 at 1:47 AM dgw [email protected] wrote: > While he is happy...

I think what you are suggesting here is a permission system, that can be independent of the current one (that is enforced by ircd?) I can imagine that, an API...

callback would be a function reference, that we can store in a hash. Let's say we only allow one callback per type (that is, AllowACLAppend is false). RegisterAcl('foo', \&my_callback) ->...

Yeah, I'd implement both cases as arrays, and just check during registration -- if we're not allowing more than one callback, return failure when trying to add to an existing...

That sounds almost like a useful feature, so careful. Relying on bucket as the source of truth for anything is a bad idea.

Yeah, accepting flags is one way, and that would be fine with me. Perhaps, for simpler use, we could follow the example of `tail`, and just do `/twitter_follow -accB Foo`?

It's not that we need to shorten the urls ourselves, but we should just adjust the counting so that we assume the current length of t.co urls (23 characters, currently).