There was a slight tick in PEP as it was released that at times could cause it to think it wasn't handling proper XML from Prodigem's API. It turns out that when doing an HTTPS 1.1 POST, the chunked-encoding returned could at random times
include hex mixed in with the server response. By tweaking the PEP script to use HTTPS 1.0, it's resolved. So you can either search for "1.1" in your script and change the one occurance to "1.0" or just download PEP with the fix.

On Friday it was reported that BitTorrent Inc. has taken in 8.75 million in venture funding. Certainly this is good for the technology, though I do see them coming in shortly and offering lots of similar types of services as seen on Prodigem. It will be interesting to see how exactly it is packaged, the role of DRM, and what is and is not hooked into their code-base.

But there is lots of content to go around, and I look forward to keep on going after it, doing what I'm doing while continuing to build community web efforts.

Rocketboom, perhaps the most popular video blog on the internet, has installed PEP into their setup allowing them to automatically have torrents created for each video blog they produce. Check out Rocketboom's Prodigem user page and RSS torrent feed.