{ "id": "e10c0974e2b57e64b895e3b9c1eebb8baf822da35126523fc9ec11545a57f08d", "pubkey": "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d", "created_at": 1703078049, "kind": 30050, "tags": [ [ "d", "implement-a-nostr-protocol-for-distributing-podcasts-in-antennapod-1e9227650ada" ], [ "title", "Implement a Nostr protocol for distributing podcasts in AntennaPod" ], [ "s", "open" ], [ "reward", "5000000" ], [ "c", "sats" ] ], "content": "The details are not yet fully thought, but the idea is that we'll standardize a way to distribute podcasts through Nostr that can be easily implementable in apps like AntennaPod and others (AntennaPod is the only open-source podcast app that I could find that works well and I use it).\n\nI assume that AntennaPod (and I presume other podcast apps) currently work by having each podcast be identified by an HTTP URL that returns an RSS or Atom feed with the podcast episodes and metadata. The idea is to allow for a new kind of URI, a \"nostr:nprofile1...\" URL with relay hints in it.\n\nThe v1 implementation could just require that at least one relay hint is in the nprofile, then connect to that relay via WebSockets (AntennaPod already uses OkHttp, and that seems to have WebSocket support) and fetch events of, say, kind 54 which will contain text (in whatever format they already support for a podcast episode metadata) and a tag with a URL to a media file. The implementation can just trust the relay and not check the event signature or anything -- that is in order to make the integration easier and more mergeable by the AntennaPod people.\n\nIt should also fetch kind 0 profile metadata in order to display a nicer name and a picture as the podcast metadata.", "sig": "2899d2fdd62c2a3165c23c80579233b7746f24effed45a1bbfa2bbd461875f4c712076d234f7c63ded3761521f56efc1bf0100b06f293c6f6ee61c1fb6255501" }