I think in terms of security it might not be the worst idea to go with a new key for now. (I don't know, it's new and all). Overall I agree that taking your identity with you is one of the killer features of nostr.
well, that was a quick uninstall. i had high hopes for nostr:npub1h0uj825jgcr9lzxyp37ehasuenq070707pj63je07n8mkcsg3u0qnsrwx8 as they talked a big game over the past few months. however, they don't allow you to sign in with your existing nsec. maybe in the future when they allow you to use your portable digital identity, i'll try it again. keep building!
Discussion
They also talked about using a modified NIP-17, essentially making their app not compatible with other NIP-17 clients in the future. This is against the entire point of using a protocol standard. I'm losing faith in them, very fast. I hope they work with other developers and come to a compromise or NIP-17 update so things are interoperable.
You should directly address our concerns about NIP-17, rather than assuming we are deliberately not complying with NIP.
nostr:note1fy2yam6h0cm628rjlyzra06t5azxuru0q88hegjxtpz5uwstztnqmy0csl
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.
