The Introduction
Being that this is my first post to the PodShow developer blog, let me take a second to introduce myself. My name is Chris McIntyre. You may know me from Podcast Alley, the site I developed and still maintain or you may know me from my profile at PodShow (ferf.podshow.com), either way I am excited to be working on the developer community with Andrew and Adam! I have been in the podcasting world since November of 2004 (almost 3 years now, holy cow) and am still loving the changes that podcasters are making in the world and in new media!
What I Do Here
I will be driving the PodShow developer community and have the following goals in mind:
- To help advance the proliferation of podcasting and new media to the world
- To work work along side developers to create cool stuff
- To promote great tools, code, applications and websites that promote podcasting
- To help podcasters find their audience and to engage them
- To make it easy for people to use & update PodShow content from outside the network
- To have fun!
PodShow set out to create a place where there were no barriers to entry for people who were creative and who wanted to get their audio and video work to the world. This is still our mission, and the developer network will continue down that path. Any way we can help people interact with their audience, to find a new audience, to create great content and to have fun doing it… we want to promote that here. With that said, let me recap what we do have already and what is coming up.
What We Have, and What’s Coming Up
- Podcast Publishing API – (documentation)
Many people don’t know it, but PodShow has an Authoring API that allows you to build applications and services that will publish podcast episodes and related details (title, keywords, descriptions, etc) to PodShow. There are already a few applications that work with it too including: Castblaster, Vidblaster, Ubercaster and Ecto. - Module Creation SDK – (documentation)
This one is mostly complete, but not fully implemented yet. We provide an SDK where you can develop your own modules for profiles on the PodShow website. The SDK gives you everything you need to develop and test your modules. Submit them to us and once we review them we can release them for use on the PodShow site. - Channel API (coming soon)
Since collecting and sharing content is such a cool feature on PodShow, this will be one of the next areas we focus on. If you have comments on how you think this should work, feel free to email me (info@podcastalley.com) and let me know! - Lots of RSS & OPML Feeds
From the PodShow APIs page you can find links to lots of OPML and RSS feeds for Podcast Alley and the PodSafe Music Network. These feeds are updated all of the time and represent a good selection of content from those websites.
I guess that is a good start for now, so let me go ahead and rap this up :) I am excited to be working with you all and to getting a lot of cool new stuff going soon, with your help. As always, if you need help or have suggestions you can email me at developers@podshow.com.
Hey Chris, great to see some OPML on the API page, but I’m afraid two of them need to be fixed to use the Type=RSS instead of Type=Link attribute. Thanks.
Hi,
triggered by the Trinity project (from Adam’s DSC) I’ve created a Python script that can be used to either be used as a library for further developments or as a stand-alone program to upload media. And in time also to manipulate exisitng media.
it uses the XMLRPC interfaces and works nicely.
How can I donate my python scribbles? I’d like to help others in this.
I only have two rules for my code.
It should stay open source and if money is made with using it, I want a donation.
Oscar
from The Netherlands
ps: may I also suggest that the password would be hashed withmd5 or sha1 before it is use bare naked on the wire? in the XML RPC interface it now works with plaintext passwords
Hey Oscar!
Very cool. If you’d like we can host it, either on this site or perhaps in Sourceforge on the SDK project site.
The hashing is a good idea. The use of plaintext was to ensure comptability with existing blog tools like Ecto that support metaWeblog.newMediaObject. But I think it will be pretty easy to allow hashes in a backwards-compatible way. Great idea!
Hi,
We’ve already started something here: http://sourceforge.net/projects/podshow-tools/
I (okoeroo user) started on Python and roland worked on the Perl implementation. I can’t speak of his side of the story, but certainly the Python part maybe in thrown to the public.
Maybe it would be nice to have it all together. Just for easy delivery to other enthousiasts. So in your SDK is an option.
I think that the hashing would be just a bit better. It would rule out the very simple script kiddie attacks that sniff the wire(les)s. Does any API support TLS? It would be even safer if the channel is secured. Once a secure channel is connected, then the session will not be burdened with much computing overhead.
It would also increase the possibility to hold users liable for ‘wrong’ content being uploaded, since you can’t just say that somebody got hold of my credentials.
GEEKS!
and proud of it to be a geek ;-)
I’m testing Cheddar out. We is the best place to raise questions or enhancement requests. I looked on podcast alley but found no thread. I will start on but am I in the wrong place?
Cheers,
Mike
Podcast Alley is a great place to have the conversation if you like! Feel free to start it here… http://www.podcastalley.com/forum/forumdisplay.php?f=281
StudioRack now also supports the Mevio API.