added nostr as a podcast:socialInteract (with working test feed)

[ChadFarrow]

added nostr as a podcast:socialInteract (with working test feed)

I’ve got a working implementation of nostr as a socialInteract protocol and wanted to put it in front of people for feedback. The idea: use a nostr note as the canonical “root post” for an episode’s comment thread, the same way the spec already does with activitypub. There’s prior nostr-comments discussion in #569, but that was about a different (discovery-side) mechanism — this is specifically about the socialInteract tag itself.

TL;DR

• <podcast:socialInteract protocol="nostr" ...> pointing at a nostr nevent as the canonical root post for an episode.
• The root post is just a normal kind 1 note, so it renders correctly in any nostr client.
• Live, parseable test feed you can point tooling at (link below).

The feed

Test feed (episode 3 is the one wired up):
https://raw.githubusercontent.com/ChadFarrow/lnurl-test-feed/main/public/lnurl-test-feed.xml

• podcast:guid: 9fe51a32-e08d-5ab7-9540-22a25c6bc2bf
• episode 3 item guid: c4dac22d-173f-4442-9b3b-5d89b20b26e6

The root post (kind 1 note)

Nothing special — a plain kind 1 note that becomes the thread everyone replies to:

{
  "kind": 1,
  "content": "To boldly go where no #podtard or #hobbyist has gone before. \n\n#socialinteract #PC20 #BOT\nhttps://podtards.com/121e299b13082e77e827058beb71dc0c9a2d3700fc96d212627d7dbe6895223f.jpg"
}

(The live note also carries the usual hashtag t tags and an imeta tag for the attached image — omitted here for brevity since they’re not relevant to the socialInteract mechanism.)

The feed tags

I’m offering two socialInteract tags by priority — the nostr: URI as primary (carries relay hints, lets nostr-aware apps fetch the event directly) and an njump fallback for apps with zero nostr support:

<podcast:socialInteract
  protocol="nostr"
  uri="nostr:nevent1qqswule05m8jh90e237m3dhju893q0qmmk5v4wrs62nevxuy9mallkczyrmey2s2mvl6fhd9am92vtm00mnpt8ml2hsgqdngd35wpquzcdrcsqcyqqqqqqgpzemhxue69uhkx6rpv3nzumn0wd68yvfwvdhk6naud4n"
  accountId="npub177fz5zkm87jdmf0we2nz7mm7uc2e7l64uzqrv6rvdrsg8qkrg7yqx0aaq7"
  priority="1" />
<podcast:socialInteract
  protocol="nostr"
  uri="https://njump.me/nevent1qqswule05m8jh90e237m3dhju893q0qmmk5v4wrs62nevxuy9mallkczyrmey2s2mvl6fhd9am92vtm00mnpt8ml2hsgqdngd35wpquzcdrcsqcyqqqqqqgpzemhxue69uhkx6rpv3nzumn0wd68yvfwvdhk6naud4n"
  accountId="npub177fz5zkm87jdmf0we2nz7mm7uc2e7l64uzqrv6rvdrsg8qkrg7yqx0aaq7"
  priority="2" />

I went with njump for the fallback specifically because it’s client-agnostic — it hands users off to whatever nostr client they already have rather than pinning them to one app.

Open question for the group

Sharing this here incase anyone finds this interesting.

Related prior threads: #569 (nostr comments), #623 (cross-app comments, 2024), #502 (podcast:chat, origin of protocol="nostr").

[ChadFarrow]

You can preview this here if you click "discussion" on episode 3.

https://www.boostmebitch.com/?podcast=9fe51a32-e08d-5ab7-9540-22a25c6bc2bf

[ericpp]

It looks like it's already listed as a social protocol https://github.com/Podcastindex-org/podcast-namespace/blob/main/socialprotocols.txt