Mantas Mikulėnas

Looks like the compressor/decompressor works fine internally, the problem is with test/base64.js. When you use the provided module to base64-encode the compressed data, it treats the input as Unicode codepoints...

Thanks. Now `--mirror-only=@domain_users` successfully matches the users' primary group. It still doesn't work if I try to specify one of the users' additional groups (although they're shown by `id $user`...

(It seems I didn't need to use `--no-user-group-precaching`, since bindfs now seems to perform on-demand lookups in any case. That's good.)

> Without the new flag, it should still read through the entire user database at startup Well, that's only the local accounts – as I mentioned, the system itself does...

Ah yes, I completely forgot about `getgrouplist()` and just went with how the _getent_ utility calls it...

I don't see how it could break _anything_, assuming the server translates it to a regular `NOTICE #chan` but only routes to a specific user. It _has_ been successfully implemented...

@jevolk: If it wasn't IRC protocol before, it is now. In fact the ircd you're working on was the first to implement support for this syntax.

@Xenthys: Ah, it's mostly the _receiving_ side that needs CAPs – or rather, the server needs them to know whether the recipient needs the message to be down-converted to a...

@a-raccoon: Because they're nearly opposite. 005 tells clients that the server supports something; CAP lets clients tell the server that they support something (and agree to use it). It's STATUSMSG,...

For initial auth (during registration), I think some ircds already do this? Vague memories of adding "disconnect after 3 failures" to Charybdis several years ago.