Category: Rant


Good friend and author, Scott Roche, is also a rather ambitious fellow. He’s recently launched an effort to catalogue the podcasts and podcasters out there, as an independent, community-driven effort. I’ve signed up, and maybe I can help — maybe you can too!

This effort is sparse, at the moment, but could grow, with effort and participation. It is the Internet Podcast Database (IPDB). (Scott has suggested that things will be moving soon to PodcastDatabase.com, so I’ll include that link as well.)


I’ve lamented continuously about the lack of real discovery and management tools we have for podcasts, so I won’t rehash that topic. Sadly, despite the break I’ve taken from publishing here, nothing really dramatic seems to have happened.

One thing I’ve never really talked about here is Stitcher, or the various other on-device podcatchers. Mostly, that’s out of ignorance and a lack of time to remedy it, but also because I confess a certain aversion to the concept of end-device podcast management. Some are quite happy to separate the collection of podcasts from their central home computer or laptop — mostly, I suspect, because it frees you from using the stagnated singular leading product in the market, iTunes. Given the growth in processor power and storage on portable devices, as well as their role in day-to-day activities formerly associated with desktop computer use growing (email, web browsing, messaging, gaming, etc), it’s a trend that’s likely to continue.

But it leaves power-users like myself a bit in the dust. I can’t possibly store the unheard episodes of the podcasts I’m already subscribed to on any portable devices on the market, nor would I want to subject myself to podcast playlist management on a screen barely big enough to handle my sausage fingers.

(Side note: bring back physical buttons, dammit!)

I also wonder about the history of a podcast being appreciated when you put in on a compressed device. There are podcasts I’ve collected for a “rainy day” of listening. Others which had their run, podfaded, and have now become complete volumes on my “podshelf”, to be brought down, dusted off, and enjoyed when I have a lull in other programs, much like I will pick up a book from my bookshelf that hasn’t yet been written. There are other podcasts which I will complete but not delete; rather, I put them back on the podshelf to enjoy again at a later date. This is particularly true of fiction podcasts, but there is a class of “timeless” podcast which includes non-fiction as well.

And finally, there is the biggest problem of all: podcasting silos, otherwise known (crudely) as the creation of a vertical marketplace. Each of these end-device applications has it’s own database of podcasts, which is created either through the googlescraping of podcasts and defunct directories, or must be submitted to by overworked podcast producters who have to somehow keep on top of every nickel-and-dime-store podcasting application creator’s product release.

So, instead of really solving a problem, for example, the issue of iTunes being a “walled garden”, you have, instead, the creation of a panoply of walled gardens, or the creation of the “podcasting walled garden” as a category of thing, and instances replicated throughout these applications.

So, I laud Scott’s effort for an independent body of knowledge, free of individual applications. It’s form is that of a wiki at present, and it is a community-driven effort, but I suspect it may transform into a form of directory at some point. With luck, it will survive the transformation with the lessons of the past failed and faded directories, and provide a resource that can automatable connections to software. With luck, we’ll see the offspring of such a project be the podcast directory service equivalent of what RSS is to podcasts; that is, an organizing principle which is metaphorically accessible and machine-readable.

Where’s My Remote?

You car radio can be randomly accessed; you can tune into any station along the dial, although you generally have a few favourites. Rather than wear your dial out, and to save on car accidents, car stereos developed presets. Now, in the digital age, we still tune in somewhere along the spectrum from one side of the frequency bands to the other, but we still float back and forth and jump to faves.

Television grew quickly from just a few channels to many. I remember the dial on my mother’s most advanced TV was still only rated for about a dozen channels. We propped a cable box on top and the little 2-number LED display could suddenly get all the way to 99 channels. Obviously, it made no sense to flip through the channels linearly, so it came with a number pad.

Even more significantly, it came with a remote control.

(Yes, this is eventually about podcasting..) View full article »

Been a while, hasn’t it? Sorry about that — life has become busy (as if four letters really encompasses it!).

Still, I remain committed to the open question which started me down this path: What should a podcast be?

Of course, in order to understand the desired future, we really need to understand the present, and that comes from understanding the past first. Fortunately, this is one of the few historical events where I can say “I was around during the whole thing”, and it’s still early yet.

So, let’s look a the present, shall we? I admit that my view might be limited, as I haven’t been as active myself in recent months, so if you don’t agree with my observations and have other data to add, I’d love to hear about it in the comments.

This was originally a post with several points, but after starting to elaborate on them, I discovered that each one is an essay. So, rather than bury you on my return, here’s the first of them:

Directories Suck (except iTunes.. maybe)

View full article »

Breaking (and Using!) the Chains That Bind Us

Due to my recent Internet connection issues, I won’t be able to publish any sort of podcast for the next couple of months. Naturally, this stalls the progress of this podcast, but I’ll try to capture my thoughts with a few more regular blogposts (and concentrate on the other work I need to get done!).

In this case, I’ve become acutely aware of the fragility of receiving and uploading podcasts, given that both aspects of it are being blocked by the fascist administrators running the IT department of my lodgings (in the name of “bandwidth management”; lots of bandwidth available when no content is delivered!).

(I’ll try to keep the vitriol to a minimum, but this issue has my dial cranked up to “really annoyed”. Hey: if I weren’t passionate, I would be less worthy of listening to, right? ;) )

So, back on topic: fragility. When libsyn.com got blocked, I was aghast: suddenly, I realized how much dependence I had on a single company, both for receiving podcasts and for producing them. When apple.com got blocked, I realized I depended on them for finding podcasts, or at least for finding out more information about podcasts.

This is a problem of single point of failure, an appalling heavy dependence that computer science graduates are very aware is a distinct form of sin.

Imagine if the power to your home were dependant on a single, easily-interruptable wire? It seems that way, ultimately, but it’s not easy to interrupt. And anyone who’s had a simple power outage knows that, while there might be temporary interruption, power is usually restored in short order, automatically, as the network reorganizes.

There are other podcast hosting providers out there, and podcast directories, too, but the market is still small. Rather, the ability to easily choke off the consumption or production of podcasts from a few rules seems improper — maybe even illegal.

I’ve tried to suggest that the blocking policies are incorrect and inappropriate, but I’ve met with no sympathy and no movement. Not knowing what avenues I have for recourse, I decided to think of it differently.

Is there a technological solution to this?

Some podcasts can be delivered by Bittorrent, which decentralizes the source, meaning that delivery is no longer dependant on a single place.

But Bittorrent can be blocked, and fairly easily. So we are dependant on a single protocol, as well! And while it can be used to bring podcasts in, it doesn’t (as far as I know) do anything for uploading podcasts.

It’s not just to defeat petty and/or moronic adminstrators that we need to think of this, either, but as a general robustness problem. A plurality of solutions is the way that the web survives — it is built into the very fabric of the Internet, in fact — and we should embrace that in every facet in order to fully be modern.

One method of avoiding these sorts of blocks is through proxies. Since HTTP is the only sort of general-use protocol that seems to be allowed on almost every Internet service, we should consider it our carrier. Since it is easy to block any given name or IP address by rule, we have to have the capacity for a large number of sites — both direct and indirect — that will simply be too big to block.

Alternatively, of course, we could “simply” have so much money that we pay the administrators not to block it, or find the political power to make such blocking illegal. (I, for one, would welcome a “Universal Internet Bill of Rights”, which properly casts it as the immoral act that I feel it is, and makes such blocking internationally illegal.)

But, short of that, consider this: what if your podcast host or web host participated? The power of podcasting seems to be in the community that it builds. What if we can make this not a problem of individuals, but a solution from the collective?

If every podcaster put up a proxy — somehow specifically for podcast transmission (up and down), at least in this initial context — then the number of avenues would grow immensely, and the blocking lists would not be able to keep up.

We would take the community to a whole new — and meaningful — level.

What do you think?

  • Am I just acting out of my own bitterness in my local situation?
  • Is this sort of thing feasible?
  • Is there a better solution?
  • Should the communication of podcasting be considered important enough that blocking it is immoral?
  • Are there technical reasons why this cannot be done?
  • Was I too emotional? I admit, having this particular problem has infuriated me, but also highlighted what must be — or could be — a very big problem.
  • Was this article meaningful? Have I strayed too far from my topic?
  • In case you are wondering, I’m looking into solutions like proxytunnel as a potential avenue for relief.
Powered by WordPress | Theme: Motion by 85ideas.