Multiple Hosting Sources

Podlove Publisher
1

Has any one ever looked at multiple hosting sources?

In my experience a new podcast gets downloaded a lot and old ones, sometimes but not a lot. I was thinking that it might be of benefit to designate a class of podcasts, say <90 days, come from one source, i.e. buzzsprout, and anything older comes from a slower but guaranteed data source, like internet archive.

The day count might be tweakable by the user, but there is not much more to that idea than that.

(Note buzzsprout provide free hosting for podcast up to 90 days and then they delete them …)

2

We have discussed this a few times but ultimately other issues were always more important than this. You could probably set it up though as a plugin or module with the hooks available.

3

Sorry for the slight necropost, but I am bumping into this again.

I was wondering how hard it would be to allow a full http path be given on a episode page rather than just a slug. Independent of the http head.

I’d like to think it is easy, but I suspect there are quite a few dependancies built into the whole plugin that assumes http head plus slug.

I am trying to run ahead of the podcast namespace work as it relates to the upcoming alternate enclosure discussion.

4

Well from the top of my head it might work to hook into this hook (https://github.com/podlove/podlove-publisher/blob/beta/lib/model/media_file.php#L227) and return the full URL here instead of a URL template. Then you only need to add a form field for that URL and save it somewhere, maybe a post_meta.

I guess you still need to set a slug to not run into issues in other places.

May work, may not work, but there’s a start for tinkering around :wink:

5

OK I have opened an issue to track this request

And the work can be found in this branch

1 Like