Nostr Web Client

Just merged https://github.com/nostr-protocol/nips/pull/1185, which introduces NIP 73 for external identities via the `i` tag. A different form of them is already in use in NIP 39, for linking external identities to user profiles.

NIP 73 IDs are instead fully-qualified, and include a second parameter which is a suggested URL, which allows clients to easily link out when they don't want to special case every ID type.

What's neat about this is that this will allow platforms like Fountain to reference podcast episodes in nostr comments, which can be displayed and linked out to by regular nostr clients, expanding the scope of the nostr-enabled web!

Reply to this note

Please Login to reply.

Discussion

Gigi 1y ago

👀

nostr:nevent1qqsdjt4nl5t4y0v8lzxn67z4mu5p5k37mfpxtd482us47zrnz8rf6cgpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtczyztuwzjyxe4x2dwpgken87tna2rdlhpd02va5cvvgrrywpddnr3jyqcyqqqqqqgsnhl9a

plebiANON 1y ago

Sick!

Derek Ross 1y ago

Podcasts, movies, books, music, etc. a lot of Nostr content can be expanded upon and improved by linking to external sources, making Nostr that much more powerful by bringing the existing Internet into the fold.

nostr:nevent1qqsdjt4nl5t4y0v8lzxn67z4mu5p5k37mfpxtd482us47zrnz8rf6cgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygyhcu9ygdn2v56uz3dnx0uh865xmlwz675emfsccsxxguz6mx8rygpsgqqqqqqskhu35k

bordalix 1y ago

LFG 🚀

nostr:note1myht8lgh2g7c07yd84u9thegrfdrakjzvkm2w4eptuy8xywxn4ssvc2wd0

NotBiebs and 69 others 1y ago

are there any clients that allow you to add nip-39 ids to your profile? i didn't even know about that nip. pretty cool. reminds me of keybase.

hodlbod 1y ago

I'm sure there are, but I don't know which ones

brugeman 1y ago

This is awesome!

NotBiebs and 69 others 1y ago

nostr:npub1yfg0d955c2jrj2080ew7pa4xrtj7x7s7umt28wh0zurwmxgpyj9shwv6vg can you add an `i` tag on zap receipts and comments on a song? spotify has this. you could just copy their format.

spotify:track:54KIAHa71rBTDubyUPwiks is the URI for https://open.spotify.com/track/54KIAHa71rBTDubyUPwiks

NotBiebs and 69 others 1y ago

This would allow anyone to easily query Nostr relays for all the events associated with a specific song

Joshr 1y ago

We started adding an `i` tag like this just last week, though it only applies to zaps coming from the mobile app. Have chatted a bit with nostr:npub1v5ufyh4lkeslgxxcclg8f0hzazhaw7rsrhvfquxzm2fk64c72hps45n0v5 about the format. Here's the mobile code: https://github.com/wavlake/mobile/blob/main/hooks/useZap.ts#L39

There is also the `a` tag that references the track/episode id, that'll likely change though once we update how we're publishing tracks as nostr events.

NotBiebs and 69 others 1y ago

Nice 🚀

NotBiebs and 69 others 1y ago

Looking at it now. You’re using the podcast prefix for songs. Wouldn’t it make more sense to make a new wavlake prefix since songs are not podcasts?

Joshr 1y ago

Yeah probably, I think this is so a client is able to locate the corresponding RSS feed for all the content metadata, which is within the podcast namespace. nostr:npub1unmftuzmkpdjxyj4en8r63cm34uuvjn9hnxqz3nz6fls7l5jzzfqtvd0j2 Does that sound right? https://github.com/Podcastindex-org/podcast-namespace

I suppose this is a transitional period until everything becomes nostr native in the future? Not sure how the RSS/nostr relationship will wind up looking down the road. Could wind up being redundant/parallel systems? 🤷‍♂️

Here is a fountain example using the same `i` tag format:

nostr:nevent1qqsvuu996n42u4swzgysp5sh6grgeladcvjrc8vm0kdzx4kre0aeraszyrrtam5st3nvh0kwwuupx7jj775dyyl42gx2cce9gzusslyx8qqf5lxcdvl