> Some legacy clients requires to have the bundle "voice-v1" in "ext".
That's not even legacy, that's just plain wrong. Personally, I wouldn't invest any time or effort in being compatible with those, as it discourages fixing bugs. That aside, you can just add 'ext=voice-v1', and return an empty disco if someone asks for it. Clients that work with any version of the caps protocol (and as such will query the node) will already have your capabilities from the (hashed) version string, and the other buggy client you are describing will also think you have whatever it thinks is in voice-v1. cheers, Remko
