There’s a clash of constantly updating specs with dozens of apps using the older versions.

Maybe it was nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn who said it: (paraphrased) do not count on spec deprecation on nostr. Therefore account for this in your app’s code.

Reply to this note

Please Login to reply.

Discussion

Yeah, I think in practice nip 04 is usually still used, but I believe highlighter accepts nip 44. The best approach seems to be to accept both, but choosing which to publish is trickier.

> // TODO how should replies to 'nip04' encrypted messages be handled?

I'll probably have to support both in my project for compatibility, but that's not ideal.

Well get support for both! And any future versions. As long as things don't get too out of hand, noscrypt's encryption API was built to handle this.

nostr:npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7 thinks big, builds solid tools, but forgets to share links. Here’s one.

https://github.com/VnUgE/noscrypt

Very grateful to have all of you guys helping me out! Just about everyone in this thread has been a real one throughout my nostr building adventure!

I know, it's so fun. 😂

I love how we’re all on the same page…

Just pushed this PR today, to implement NIP44 for NDK signers … using Coracle as a model … which has a nifty little “check” during decryption to see if Nip04 is needed.

https://github.com/nostr-dev-kit/ndk/pull/233

Ooh I'm working on remote signing right now, I'll take a look at that proposal.

that check is annoying af

i haven't updated it but the initial implementation of NIP-44 for Go did not correctly decode or encode the HMAC

so imagine me, trying to test a chatbot that was planned to be an administrative CLI fro my relay

stop it... don't push nip-44 on everyone like this, nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn this made me hate you a bit also

You can turn the toggle off and it won't bother you for that conversation

it turns itself back on all the time, it's annoying af, i would want to be able to disable it at all

but i am not using coracle these days, and i wrote an in-chat verification process that is like nip-42 except the user has to copy and paste a string, and then after all the fun of the nip-42 fiasco i quit trying to make an ACL for that time

I'll make sure the setting is remembered