I'm not a developer on NIP-17. You should consider working with them to resolve your issues, making it more robust for everyone to use. I've already said I wished for you to work with them instead of deciding to make your application not compatible with other applications, throwing interoperability out. It's an open protocol, meaning anyone can build, but if we don't adhere to standards, then the protocol doesn't work if everyone starts to do that, right? 

 Under that post, I discussed extensively with one of the contributors to NIP-17, who is also a developer of 0xchat. You should be able to see the results of our discussion. 

 Good. Keep discussing. Hopefully you reach a consensus so you don't have to essentially fork the protocol. 

 What's up with the drama?

This should be a technical discussion, not an "omg I'm losing faith they didn't use my key" one. 

 User experience for the masses. A key feature of Nostr is interoperability and portability. Breaking that essentially breaks consensus. 

 Hard agree. Lots of negative language towards a project that actually produced something that people were asking for albeit with some tradeoffs