Proposal: <podcast:follow> tag and JSON spec #609
nathangathright
started this conversation in
Spec Proposal
Replies: 2 comments 11 replies
-
I’d really love to see this proposal make it into Phase 7, but that’s not going to happen without more hosts expressing interest in adoption. Otherwise, I’d appreciate any feedback or concerns that are dealbreakers. @snookfin @albertobeta @mijustin @bmaluijb |
Beta Was this translation helpful? Give feedback.
9 replies
-
Also happy to support this as we already have the info in Podhome, although the usage of this will of course be very limited.
Sent from Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Sam Sethi ***@***.***>
Sent: Thursday, April 11, 2024 7:32:46 PM
To: Podcastindex-org/podcast-namespace ***@***.***>
Cc: Barry Luijbregts ***@***.***>; Mention ***@***.***>
Subject: Re: [Podcastindex-org/podcast-namespace] Proposal: <podcast:follow> tag and JSON spec (Discussion #609)
Happy to support it as we already have social links in our user settings and if we can read them from the RSS feed it makes populating the fields easier. I think we will need to this for the new ActivityStream work. So +1 for TrueFans. I also reserve the right "Developers may choose to ignore links that don’t suit their use cases." ;-)
—
Reply to this email directly, view it on GitHub<#609 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AD6C7Y2PH6GYZ5ERLHFPRJDY43CL5AVCNFSM6AAAAABDD4LF52VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TAOBXGA2DG>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Purpose
Matching feeds to their corresponding URLs in third-party podcast apps can be tricky. The
follow
tag would allow podcasters to verify their presence on various platforms by providing an array of URLs in a linked JSON file. This is particularly useful for locating shows on platforms with no public lookup methods or identifying shows with common names like “Real Talk” in platforms that only provide a search API.This tag will be of little use for most podcast apps, but podcasters that want to take advantage of universal link services (like episodes.fm) wouldn’t need to create accounts just to fix an incorrect link or add a missing one.
Parent
<channel>
Count
Single
Attributes
Example
JSON Format
This is the initial spec for a JSON format that can be referenced in an RSS feed using the
<podcast:follow/>
tag. This file can reside on any publicly accessible URL. This file should be served with a Content-Type ofapplication/json
and a Access-Control-Allow-Origin header set to*
.Permissible Link Guidelines
This spec does not restrict permissible domains or multiple links to the same domain. Keeping it flexible allows new use cases to emerge without modification to the spec. Hosts may choose to only permit familiar domains, and developers may choose to ignore unfamiliar or repeated domains. For your convenience, here’s a repo of common podcast link patterns.
JSON Keys
Examples
Basic Example
Multiple links to the same domain
Hosts may choose to permit only a single link per domain. However, if a feed contains multiple links to a platform, they should all point to the same "show," such as separate audio and video feeds. Developers may choose to ignore duplicate domains.
Social links representing the podcast
While the intention of this tag is primarily to provide links to podcast apps where a user could "follow" the show, that technically includes social destinations as well. Developers may choose to ignore links that don’t suit their use cases.
Beta Was this translation helpful? Give feedback.
All reactions