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.
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.
Discussion
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