nostr:npub1unmftuzmkpdjxyj4en8r63cm34uuvjn9hnxqz3nz6fls7l5jzzfqtvd0j2 how might we spec this?
I’d request nostr native bookmarks that that take me to a specific time (e.g. 21:21), and optionally end at another time (e.g. 21:21 - 23:01)
Wouldn't it be great if nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc's and nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft's new podcast could be referenced directly inside Nostr? That way I wouldn't have to just allude to its existence and could make clear what I'm talking about instead of hoping the reader of this tweet will search for some vague name in a centralized canonical index of all podcasts.
Discussion
Zaps can go to specific segments of the podcast. This way the observer can see the most zapped moments of the podcast.
Comments are tagged to specific segments of the podcast. This way the observer can see the most commented moments of the podcast.
NIP-84 includes the idea of targeting audio; essentially a highlight where the range is time-based instead of text offsets.
Meaning; you could create a highlight of an MP3 from second x to y and zap/comment/repost that.