nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 You're working on nostr:npub19hg5pj5qmd3teumh6ld7drfz49d65sw3n3d5jud8sgz27avkq5dqm7yv9p for Zap.stream, right? What are your findings about Nip-44 encryption?
I went down a rabbit hole about 6 weeks ago, trying to switch Rizful to the newer nip-44 standard, and implemented a bunch of code but then ended up reverting everything. You can see the issues in this discussion: https://discord.com/channels/1195419474166296576/1195419475751751862/1427800875778445352
Basically -- since (at least as of 6 weeks ago) many major clients don't support Nip-44, the only solution I think is to produce BOTH nip-04 and nip-44 events.. which negates any privacy benefits... but even when I did that, I ran into some nasty issues... I think possibly the issue was with Damus, which will show error messages (need to test this again) whenever it gets any nip-44 NWC event.
So the solution (again, six weeks ago..) was to completely give up and go back to Nip-04.
I also noticed (as I remember) that the only NWC service that was using nip-44 was Alby ... CoinoOs and the other ones only used nip-04.
