search

Podcastindex-org / podcast-namespace

A wholistic rss namespace for podcasting
Creative Commons Zero v1.0 Universal
389 stars 116 forks source link

Proposal: <podcast:block> #179

Open PofMagicfingers opened 3 years ago

PofMagicfingers commented 3 years ago

<podcast:block [id="[platform_id]"]>[yes|no]</podcast:block>

This tag allow to specify at channel if a platform is allowed to index this podcast.

This aim to clear the mess we're in with multiple clients using multiple tags : right now, if you use googleplay:block you block Google, but if you use itunes:block you block Apple but also block Google as well.

Platform id is the same as podcast:id tag.

If you do not specify the platform, it should be considered as default value, for platform not specified.

ie: this podcast is only allowed on Spotify

    <podcast:block>yes<podcast:block>
    <podcast:block id="spotify">no<podcast:block>

If there is no default tag, it is inferred as not blocked. Here everyone is allowed : 

    <podcast:block id="spotify">no<podcast:block>
    <podcast:block id="google_podcasts">no<podcast:block>

Here only Google Podcasts is blocked :

    <podcast:block id="google_podcasts">yes<podcast:block>

We can discuss if this should be available at item level. If I recall correctly, itunes:block is available at item level.

This could also serve the same purpose as <podcast:private> proposed on #167

This is a transfered proposal from our former project podCloud/podcast-ext. See #173 for details.

coldacid commented 2 years ago

I'd like to suggest that podcast:block should be supported at both channel and item levels, similar to itunes:block, and with similar semantics (telling a service to not list the blocked episode, either globally or by service slug).

swschilke commented 2 years ago

In the serviceslugs.txt are podcast hosts and apps or services included. In theory you could also block another host, right?

E.g. you host on buzzsprout and block acast (in case of they offern an directory or allow listening / playing podcasts from other hosts).

On Thu, Aug 4, 2022 at 5:38 AM Dave Jones @.***> wrote:

@PofMagicfingers https://github.com/PofMagicfingers Does this look good now? Block Tag https://github.com/Podcastindex-org/podcast-namespace#podcastblock---discuss

— Reply to this email directly, view it on GitHub https://github.com/Podcastindex-org/podcast-namespace/issues/179#issuecomment-1204718765, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADE66AT4MFZF2IEKXTJGRVDVXM3MNANCNFSM4W65MKLA . You are receiving this because you commented.Message ID: @.***>

theDanielJLewis commented 2 years ago

I'd like to suggest that podcast:block should be supported at both channel and item levels, similar to itunes:block, and with similar semantics (telling a service to not list the blocked episode, either globally or by service slug).

I agree with this. But we should expect it will completely block the episode from even being consumed on those platforms. That's how Apple Podcasts works since iOS 14.5 because they now use their own feed proxy.

In the serviceslugs.txt are podcast hosts and apps or services included. In theory you could also block another host, right? E.g. you host on buzzsprout and block acast (in case of they offern an directory or allow listening / playing podcasts from other hosts).

This is what the lock tag is for since migrating a feed is an "opt-in" act and not something that gets discovered or automatically imported like podcast apps would do.