It's a draft: https://github.com/nostr-protocol/nips/pull/686. Looks like our NIP number got ganked.

nostr:nprofile1qqs99d9qw67th0wr5xh05de4s9k0wjvnkxudkgptq8yg83vtulad30gpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9nhwden5te0v4jx2m3wdehhxarj9ekxzmny9uq3kamnwvaz7tmjv4kxz7fwdehhxarjwpkx2cnn9e3k7mf0j4msr2 it is a thing, I think 6+ clients support it already. We're just waiting for NIP 44 encryption to get finalized.

Reply to this note

Please Login to reply.

Discussion

The priesthood secretly hates protocol.

What's your protocol?

Oh, sorry, added a pronoun where there wasn't one. What do you mean?

This hasn't been my experience.

Not married to it but any sort of protocol seems unwanted. No request for change, just no.

https://github.com/nostr-protocol/nips/pull/560

And note the lack of a reply to a reasoned argument.

https://github.com/nostr-protocol/nips/pull/895#issuecomment-1820369636

Anyway, I prefer competition to argument so thinking about creating a new protocol initiative.

That link is not better than "nip24". Where can I see details?

What's missing? Look under files changed, that's the whole enchilada. There are implementations in coracle, amethyst, snort, 0xchat and others.

Sorry. Your link had a . in the end and that lead to some confusion.

nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s how does gift wrap relate to the auth method you had in mind?

giftwrap is much more complicated, harder to query, breaks current nip04 integrations (bots, nostr build logins). auth is much simpler and hides metadata from public, just not from relays.

…auth you say? 🙏

nostr:note16uq7khxagsyrccm3c5fv4w5x5zcapuh4gsrseegvt955h2racyks9arjka