search

nostr-protocol / nips

Nostr Implementation Possibilities
2.39k stars 582 forks source link

Deprecates note1 #1586

Open vitorpamplona opened 2 days ago

vitorpamplona commented 2 days ago

No one should be using note1 bech addresses for anything.

arthurfranca commented 2 days ago

Agree, there is no pubkey hint nor relay hint.

staab commented 2 days ago

I agree with this, but I have a lingering doubt. note1 entities are the same as npubs, in that they're referentially transparent in a way nprofiles and nevents aren't. People use npubs all the time to identify their accounts. Identifying events in a human friendly way is less common, but could still be useful. I do think this is a net improvement though, because embedded note1s are evil. I would actually like to see nevent go away too in fact in favor of naddr, because the don't include a pubkey, which long term is going to be a more durable hint than a relay url.

Edit: forgot that nevents can have pubkeys. Ignore that part of my comment.

alexgleason commented 2 days ago

note1 is necessary as the canonical ID of events in systems where URIs are used, eg ActivityPub bridged to Nostr.

This is because a stable identifier is needed, and it has to be a URI.

vitorpamplona commented 2 days ago

You can keep using it internally (I also have other nostr URIs that I use). I just don't think it needs to be an interoperable standard.