Elizabeth Myers
Elizabeth Myers
I'm presently writing an IRC library and am gathering up lots of numerics from lots of places and documenting known conflicts. When I finish this work I will make a...
@jillest STATUSMSG is so little used I don't think that's much of a concern. Clients will have to be fixed at the same time, I guess.
This is really quite a mess. Here are my ideas: 1) disabling STATUSMSG by default without CAP. This disables statusmsg for clients, even if it already works with it (I...
Sure, but it still needs to be documented and standardised then. I'm for opting-out as sort of an anti-CAP.
They're also using pidgin Note, that's what shows up in *my* debug log
I deliberately broke the macOS build because their crypt really sucks and it's not worth the trouble.
I will remark my "workaround" for this is that I temporarily removed PermissionsEx support from my build of the plugin (as I do not use it) but this is not...
Okay, I dug through the history and docs, and saw that it said: >"Note: This function is not available for Apple platforms. On those platforms, group membership management should be...
I know I'm just a rando, but if I may make a suggestion, perhaps you could namespace breaking traits as a stopgap? It's less maintainership burden, doesn't involve the burden...
Here is some sample output: ``` [world] testing something [w[[sroracle]][[sroracle]][[sroracle]]d] [[[[sroracle]][[sroracle]][[sroracle]][[sroracle]][[sroracle]][[sroracle]][[sroracle]][[sroracle]]]] ```