nostr:nprofile1qyvhwumn8ghj76r0v3kxymmy9ehx7um5wgcjucm0d5hszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0qy88wumn8ghj7mn0wvhxcmmv9uq35amnwvaz7tmjv4kxz7fwwpex77red4skucfwdejhgtcqyztuwzjyxe4x2dwpgken87tna2rdlhpd02va5cvvgrrywpddnr3jynnn8vu Hey, question on Coracle.
When sending DMs, a warning shows stating the usage of legacy DMs. Is this simply an FYI warning, is there a way to enable NIP-44 messaging, or is development required to implement this?
If you see the warning, you should be able to click "send using NIP 44" and have it work. Support for nip 44 is not everywhere yet, but is slowly being rolled out to signers and extensions.
Figured it out!
I was logging in with an extension, so mainly just pub key was used with signing done on a per-need basis.
Once I logged in with private testing key, I was able to test Nip-44 DMing.
Would it make sense for Coracle's messaging to request the private key specifically for this purpose? I thought the "Decrypt messages from peers" permission that nos2x-fox asks for would be included, but seems it's not.
Newer versions of nos2x will/do have support for NIP 44, I'm not sure if it's released yet. I don't request the private key because that's poor security practice. So right not it's all a little wonky, but hopefully will be resolved soon.
Nsec.app now supports Nip44, and it works with Coracle, you can try it instead of the extension.
Oddbean new post about login | logout 