One of the things keeping me busy periodically over the last few weeks has been integrating blip.tv with the embedded CCK video module. There's already a submitted patch for a basic version of the modules' output and blip.tv, but it ignores some of the best functionality that blip.tv has to offer (thumbnail generation and original file hosting).

I've been conspiring with Roland and the rest of the folks on Bryght on the best way to make this happen. One of the distinct advantages that blip.tv offers over its competitors is that they host your original media file, as well as generating a flash file for you to host on your page.
Having access to the original file has some really awesome advantages - original filesize + enclosures in rss = itunes feed. Want to push to feedburner? Include a link to the original file, and get an automatic videocast listing.
The big problem is getting this data out. Enter the blip.tv API.. a fantastic tool, but only fully defined in their wiki (the other references on the main site refer to a buggy import feature). They offer a wide variety of data formats for export (off the top of my head: RSS, OPML, Atom, JSON, and probably some others).
Now we hit the gotcha - out of the box, their RSS feed has enclosure, thumbnail, flash and original file info; their JSON format only has thumbnail and flash version. JSON is a lot more fun to play with within Drupal, so my biggest gripe is that they don't send the same information out in all the formats.
I'm just about done a hackish version of bliptv.inc, but it would be great to get a fully featured version (meaning I either have to restart with the RSS feed, resort to having the original file url/information entered by the user, or wait for them to upgrade).

I'll post the file as soon as we're done QA, and we've settled on using a custom solution for our particular client, but I hope that bliptv accepts my feedback and we can expand the base functionality.