In prep'ing for digital journalism workshops for our UW undergrads, I discovered that the Seattle PI has opened up at least some editorial board meetings to the public via "podcasts." (I challenge you to find the podcast archive/description via the masthead links, however.)
The NY Times Caucus blog reported Saturday that a Friday afternoon Indianapolis Star editorial board meeting with presidential candidate Barack Obama was "live streamed in real time." (The blog link to the webcast is now broken -- poor planning on the Indianapolis Star's part and a lead-in to the "tech incompetence" portion of this post.)
I question the merits of a live video stream: mid-afternoon on a Friday while most folks are at work? I like the PI's simplicity -- an mp3 of the session, with give-and-take. Video might be nice -- but doubtful, as there is no "motion", simply talking heads. And the mp3 is easy to download and listen to when disconnected from the website.
After a LOT of hassle (see below, blockquote), I found links to two Obama videos on IndyStar.com: opening remarks and a closing statement. The titles suggest that editorial board questions that happened in-between are not part of the tape-delay record. In fact, the presentation (search results) doesn't look like an editorial discussion but like something you'd see on Obama's website.
I click on the first link and wait. And wait. Finally I get a "player loading" status message. And wait some more. (10-15 minutes - no, I'm not kidding and I'm not on dial-up.) Suddenly, I hear horrible (a poor stream) audio of a woman's voice. I return to that tab and discover I'm on a page -- gannett.a.mms.mavenapps.net -- identified in the title as "Immersive Player." WTH? There are so many things wrong that I hardly know where to begin.
First, the search link from IndyStar.com does not work, ie, it doesn't take us to the video in question. And there is no easy way, looking at the interface, to find it. (Folks, search is a LAST RESORT as Jared Spool is fond of saying. If people are forced to search, they leave. I left.)
Second, the link in the URL bar reflects incredibly STUPID IT on the part of the newspaper industry (Indy.com is a Gannett property):
These people have not heard of SEO URLs or human-readable URLs, obviously.
Here's the original link, in all its glory -- it's no better:
Third, there is no easy way to make any video "viral" like there is with YouTube (easily embed in blogs, email). There's no way to highlight and copy the title or anything else on the page.
Fourth, there is no branding in the web page TITLE tag (which simply reads "immersive player" -- so it doesn't even brand whatever company it is that created it). We don't know if we are in "Indianapolis" or somewhere else in Gannett-land.
At this point, I'm dumbfounded.
I spent about 20 minutes trying to find a copy of the Obama editorial meeting referenced in the NYT blog post. Fruitless. Waste of time.
No wonder newspapers are losing the battle of digital convergence. Why didn't they simply post the videos on YouTube? Or Google Video? Or Blip.tv? Or Brightcove, if they felt like thay simply had to use a paid hosted service?
No, they're using a proprietary application developed in SHOCKWAVE. Why? WHY?
Finally, the video app from maveapps.net (whomever they are, that URL doesn't work) doesn't work for Linux folks. As I've said before, I don't have a problem with media forcing customers to use proprietary technology to view entertainment -- but I have a big problem when they exclude citizens from viewing news content.
Does commercial media have any understanding today of the "public" component of their mission? It certainly doesn't look that way to me.
Maybe they should simply roll-over now.
What do you think?
The following is the "email" that I tried to send to IndyStar.com when I got my first 404 error:
The NYT gave this link to Friday's stream with Barack Obama. After the streaming session, it would have been courteous (and prudent) to forward the above link to an archive of the editorial board meeting (one assumes it was recorded for delayed listening).
Well, this is not the only thing broken on the website. The Help Center "We're sorry" submit button [http://www.indystar.com/Article_not_found] is broken also.
Error - http://www.indystar.com/apps/xsendmail.dll
Initiating new verification scheme
Key verification is enabled - initiating
Validation key found - starting decode
Validation key life time set to 15 minutes
Invalid verification key provided!
Key verification FAILED
This article first appeared at WiredPen