@ari @piku

IRCv3 is fully backwards and forwards compatible, capabilities are negotiated upon connection -- and you can say "for capability X, you need Y and Z", so the whole mechanism is meant to allow new features while also semi-transparently handling older clients as well

so tech debt isn't an issue i'd worry about, and as someone looking into ircv3 and meaning to write my own clients, the main thing missing right now is just, people, writing software and getting involved with writing/reviewing the protocol extensions