Allowing <podcast:socialInteract> in the <channel>?

[daveajones]

If a podcast has a social media account, it would be nice to be able to set that at the level so that it can pass through to clients. I'm building the PI-AP bridge so this is something I want for that purpose. But, as developers start to leverage ActivityPub/BlueSky/Nostr/etc more, it would be good to have that available.

I'm thinking it could be something like:

<podcast:socialInteract 
    protocol="activitypub" 
    uri="https://social.podnews.net/@podnews/110401010985487762" 
    accountId="@[email protected]" 
    accountUrl="https://social.podnews.net/@podnews"
/>

The uri in this case would be a link to a sticky post perhaps, or some other post that is a good intro post. Or whatever works for the podcaster. The accountId and accountUrl would be the most important thing for discoverability.

[johnspurlock]

I believe @benjaminbellamy had something like this as part of his initial spec: https://github.com/Podcastindex-org/podcast-namespace/blob/main/proposal-docs/social/social.md

[daveajones]

Yes, I remember this now, thanks. In his proposal it was a different tag: <podcast:social> that identified things at that level. I'm not sure we need a new tag for that. Thoughts?

[nathangathright]

Could you clarify why it would require an accountUrl, a URI and a accountId? That feels redundant without whatever context I’m missing.

[daveajones]

They were required in Ben's proposal, but not in the <podcast:socialInteract> tag final spec:

If we stick with just allowing <podcast:socialInteract> in the <channel> it would come with those requirements intact, which seems ok to me. But, it actually doesn't address my intended use case here.

I think this should probably be adopted, but my initial idea isn't really what this solves, which is fine.

[jamescridland]

I'd support this - and, indeed, would expect this to be the default for most podcasts that don't get enough chatter to justify one in the <item>