Mantas Mikulėnas

I imagine both would be part of the same spec; e.g. targets: `foo/!bar` or `!bar@foo` or whatever: deliver to a specific nickname, but ensure that it's logged into that account...

> @edk0 @ilbelkyr that's what I'm saying, we have account names already so we could just add an indicator that they cannot be changed - which hopefully would be the...

> What other reasons are there for changing the account name other than not wanting to be tracked? As that's flawed since you can track users in other ways anyway,...

> I am strongly against loading images on IRC. Part of the giant interest in IRC is lightweight, scalable, even with old or weak hardware. It also makes doing flood...

The configuration is still potentially useful when the institution doesn't have CAT activated, or didn't keep it up-to-date. But with manual configuration, at least the `ca_cert=` should be configured to...

I'm not sure I'll ever get around to this project, but: Please post the raw contents of the event log from `/sys/kernel/security/tpm0/binary_bios_measurements` if you can. And, if you have a...

> should the canonical form of subcommands be capitalised? IIRC, all verbs in IRC are uppercase, so imho this should match existing specs (CAP uses uppercase and iirc ACC does...

> unsetting via a null tag makes sense Sigh, I just remembered that the message-tags spec says "specifications must not assign different meanings to empty and null" for compatibility reasons....

Well, I like the idea of separate auth tokens but the description doesn’t sound like OAuth2, if you just get the token from the same server you’re authenticating to. (But...

> they might have been thinking of Google's XOAUTH2. https://developers.google.com/gmail/imap/xoauth2-protocol#the_sasl_xoauth2_mechanism > > However, this protocol is only half of OAuth2 -- the actual obtaining of the OAuth2 access token is...