Thanks for testing.
Please note, this is still in the early stages. We will later make an incompatible upgrade to the shared key group, replacing NIP-4 with NIP-17 or a modified version of NIP-17. View quoted note →
Login to reply
Replies (6)
These are our concerns regarding NIP-17. We are not sure whether to modify NIP-17 together or if our concerns are misplaced.
View quoted note →
Please don't use modified NIPs. NIPs are there for having standards that enable communication between different clients without compatibility issues.
I know about this, and I even answered you with a suggestion.
The point of a protocol is to have standards. These standards allow interoperability, right? It sounds like you should consider working together with those working on that NIP. It would be the best for the protocol and for your application.
We agree with your statement. This is our first time delving deep into NIP-17, so we initially posted an explanation of our views on NIP-17.