Creek automatically creates podcast XML feeds that are compatible with iTunes. You can submit these podcast feeds to iTunes, and (after approval) they will show up in their directory.
The basics: Podcast info and XML feeds
- Podcasts in Creek come from the public broadcasts for each show. A broadcast = a podcast.
- Each broadcast must have one MP3 or AAC file attached in its media. Only one audio file per broadcast is recommended.
- The broadcast's list of music (the playlist) will automatically be included in the podcast description.
- The authors (DJs or hosts) are the display names of the user account's connected with the show. Podcasts supports multiple DJs/hosts.
- The podcast's image is taken from the show's featured image.
- See below for the podcast XML feed URLs.
- Podcasts are hosted on your own S3 storage service. Read more below.
Podcast XML feed locations
The XML output for podcast feeds is located at the URLs (below) for each show and station.
Note: Make sure to replace your-station.creek.fm and show-name. This might also be your own domain (since you can use custom domains with Creek, like BFF.fm does).
- Single show, good for iTunes:
- Global podcast feed for the station:
Submitting to iTunes
Many DJs have successfully submitted their shows to iTunes, and are now listed on the iTunes directory.
See Apple's iTunes submission tutorial for the complete guide.
You will need the following information from Creek in order to submit your podcast:
The URL to your podcast's XML feed:
These options properly set up for the show that you are submitting:
- Author names: These come from the display names of each host's user account. Make sure that your display name, along with any other co-host, looks how you want before submitting to iTunes.
- Explicit content: Check the explicit content box if this applies.
- Show description: This comes from the show's full description.
- Image: You will need an image for your show that conforms to the iTunes size guidelines (see iTunes tutorial).
Also, as mentioned above, podcasts must be enabled globally for your station (ask a manager, if needed).
- Hosted by Ben Ward and Simon Batistoni — Ben is a major contributor to the Creek project, and helped build our podcast system. He also works at Twitter, building their Widgets toolkit (wherever you see an embedded Tweet or Tweet button on the web, that's Ben!).
NWTC — The Campus Connection — Northeast Wisconsin Technical College:
- Navigate to a show, and then click the Feed Icon to see the podcast feed.
Data Hosting: S3
We spent a lot of time figuring out what is the best way to host your data. We wanted it to be both open, and flexible, rather than locked into servers "somewhere at Creek" — personally, we wouldn't want that, and neither should you.
So with Creek, your podcasts are hosted on your own Amazon S3-compatible hosting service. S3 is like Dropbox for web developers. ([Read more about it here.]) This means that Creek itself does not host your podcasts — you do. Sort of!
There are many advantages to this approach, including:
- Inexpensive: S3 pricing is less than $0.03 per GB, and will only get lower in the future.
- Complete data freedom: You can do whatever you want with the underlying data and files, liek accessing them through FTP-like client software, downloading all files to local storage, etc.
- Pricing flexibility: Choose your own hosting service, that costs the amount that you want (Google, Amazon, and DreamHost are always competing for the lowest pricing).
- Not locked to one hosting service: Migrate your files to another hosting service if one springs up that costs less than (currently Amazon S3 is the least expensive).
- Data security and ownership: You will always have your podcasts, even if Creek gets hit by an asteroid.
- No ads: Since data is stored at your own host, there is no way for us to inject ads — not that we would even want to, since we have a strict no-ads policy for stations that use our paid platform (unless you want to promote Creek with a logo on your website or something!).
- Possible to self-host the data at your studio! You can even self-host your podcasts at your studio using open source S3 platforms like Minio. Contact us if you want help setting this up.
If the two-week, DMCA-rule limit is enabled in Creek, then it is enforced in podcast feeds as well.
However, it is still up to you to use discretion when submitting podcasts that use copyrighted music. Creek cannot be held responsible for music usage in podcasts.
SoundExchange does not cover music in podcasts, since it counts as interactive streaming.
The feeds are also include Atom tags, to make them conform with Atom XML specs.