Updated: 3/23/2005; 11:58:17 PM.
Berlind's Media Transparency Channel
If you're looking for my podcasts, please read What to do if you're looking for my series of podcasts on IT Matters. Otherwise, read on.

This blog is now a part of my experiment in media transparency. The premise is that if the media can broadcast polished edited content through one channel like ZDNet, then why can't it also broadcast a parallel channel that's full of the raw materials (thus, this "channel"). For a much more detailed explanation, be sure to check out the following:In case you're interested, maintaining a simplistic transparency channel like this one has so far involved a significant amount of heavy lifting. The core technology may exist, but it's my opinion that a decent UI for publishing a transparency channel does not. So, one outgrowth of this experiment might be a complete specification for such a system -- Something I call JOTS.
        

Wednesday, February 09, 2005

In a recent e-mail discussion with Dan Bricklin regarding how the automatic publishing of e-mails from PR folks was making people nervous, and how, in the name of getting my job done, the need for ultimate transparency will have to be balanced against a source's right to privacy, Bricklin compared the situation to what happens when a video camera with a blinking red light is unexpectedly thrust into the face of a source. He makes a great point about offering veto power before publishing, but how that runs the risk of not getting the coverage altogether. Here's what he said:

From: Dan Bricklin
Sent: Friday, February 04, 2005 3:53 PM
To: David Berlind
Subject: Re: media transparency channel, further developed

David,

Good stuff!

In video there is the red light when the camera is rolling which kind of reminds you. But, that sometimes makes people clam up, like when you hold a mike in their face. Perhaps the "asking after the fact" thing is better. Show them what you'll make available and give them veto, but if they do, then they veto the story and some parts are explicitly not vetoable (the stuff when the "red light is on"). Things in a public podcast, for example, are available for transparency and timecodes into it are always OK like links to a website (or screen captures of something that was on a website).

The email editing is tough because of the time, but providing it is making reporting consist of producing more material which is good for readers. As publishers need less to do (with distribution not needing all the printing and shipping logistics) there can be more expense on reporting. :)

DanB

8:34:24 AM    comment [] RadioEdit

© Copyright 2005 David Berlind.
 
February 2005
Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28          
Jan   Mar


BlogRolls
 New Media Thinkers
 Media & PR Transparency
 Vendor Blogs
 Tech Guru Blogs
 Tech News Sites
 ZDNet Blogs
 Other Cool Peeps

Click here to visit the Radio UserLand website.

Subscribe to "Berlind's Media Transparency Channel" in Radio UserLand.

Click to see the XML version of this web page.

Click here to send an email to the editor of this weblog.

Technorati search

Top 10 hits for media transparency on..
Google
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Help link
 3/23/2005; 11:21:16 PM.


Categories and Current Editorial Projects*