pull down to refresh
277 sats \ 2 replies \ @rheedi0 25 Jan 2023 \ on: Nostr in Breez: call for Nostr devs nostr
I think it could go even further with the metadata for podcasts/music/etc being published out as Nostr events using the content field as a structured JSON for example (perhaps a slimmed down version of what we see in podcast 2.0 RSS feeds). Not sure if anyone else is thinking about this, too -- we definitely are. I imagine we could have media players that aggregate these media events for listeners/viewers and then allow users to publish comments, payments, or other reactions to that media event. Then any player would not only be able to present the content itself to its users but also gather and present all the reactions to it, regardless of where those reactions came from.
I suggested a metadata tag that references the episode URL (see #1) to have single source of truth. You can use this metadata to receive notifications, filter etc.
reply
Right. My thinking was that linking to a native Nostr event id would be cleaner and allow any downstream event to not only link to the content but also have access to whatever other metadata was included in the structured event.
reply