@js I believe that it’s not really scalable to only use url to identify a host.
“the intent is to identify the podcast host the podcaster would say they are dealing with.”
If you ignore the other meta data, and only select url, it means Castopod has to share all the custom URLs for all their customers, with each new customer needing another entry. (Continued…)
Posts
-
New data! My ranking of top podcast hosting companies based on the 1.9 million new eps in May 2024 -
New data! My ranking of top podcast hosting companies based on the 1.9 million new eps in May 2024@js yes, there is no doubt the generator tag is not ideal as there is no standard on how it should be used and the format it should take. We are working to get this into a PC2.0 or PSP standard though (see the discussion on GitHub about the host tag.)
In the meantime though - how do you handle custom URLs and self-hosted media files? -
New data! My ranking of top podcast hosting companies based on the 1.9 million new eps in May 2024 -
New data! My ranking of top podcast hosting companies based on the 1.9 million new eps in May 2024@js @benjaminbellamy @Castopod using the media url breaks down when you have self hosted media. In my case the media host is a subdomain on my own TLD. How do we match all those custom URLs to a host?
Again, this is where the generator tag (or a podcast:host tag) should be used. -
New data! My ranking of top podcast hosting companies based on the 1.9 million new eps in May 2024@aslakr @benjaminbellamy @[email protected] @js @Castopod it’s using the url of the enclosed media, so if you’re serving media from s3 or Cloudflare, I’m not sure how it appears in the host stats - there is another chart for CDNs.
-
#activitypub It seems like we will need to define a Podcast ActivityStreams object type. I’ve been trying to see if we can just transmute a podcast into an Audio or Video object type. But the loss of fidelity is so high. I think a dedicated object type...@js @dave yes, I was thinking “are we trying to replace RSS here?” Why do we need to bring in the PC2.0 features into the object? Don’t we just point to the RSS feed or the base url to get all this info?
The only stuff needed in the object would be how to find the podcast, and anything needed for promotion like images, clips, etc.
It needs to almost be AP native, so it can interact with any AP client without them doing any extra work, right?