- Inside the Obama Numbers: Tiers of Engagement
- Is Change.gov Really Changing Our .gov?
- A Freed Change.gov Gets Wigitized, iPhone Apped
- Testing New Search Tools on Government & Campaign Information
- McCain and Obama Used Web to Persuade in Final Weeks
- Daily Digest: Hill Secrecy? "Just Absolute Lunacy"
- Daschle's Health Care Response Video: Interesting, Or Not?
- Daily Digest: Renewing the Push for Open Government by Law, by Code
- About that Rebuild...
- Bridging another Digital Divide: Local races and DLCCWeb
By Micah L. Sifry, 02/15/2007 - 8:27am
It's time for some editorial housekeeping. Last night, I deleted a post by a new user, Hasan Jafri. He had signed up and innocently discovered that users had permission to blog and/or post stories with digg-like voting attached to them. These are two features that can be enabled on the Drupal platform that we use to run this site, but it was not our intention to run TechPresident as an open site where anyone can post at will. (Comments are open and will stay open as long as people behave.)
So, I took the post down (it wasn't a bad one, by the way) and sent Jafri an apologetic email trying to explain. He rightly takes me to task here:
No sooner had I posted my last message than I got a damage control e-mail (note they did not engage me in an open thread) from TechPresident’s edtor Michah Sifry stating “unfortunately, I had to take your post (of the flubbed Romney video) down because we are not an open site.”
Not true. Why else does TechPresident give its members a blog function and a Digg-like form to link and introduce stories? Or at least it did till two hours ago. Sure, you don’t have to be open thread (as this blog is) but in that case you should at least include a note to users saying posts are moderated. Duh!
Three tips since this is obviously a learning curve for these guys (and I still like their site):
1. Fess up when you mess up.
2. Don’t make excuses.
3. NEVER try to control an open thread conversation, especially about a new product, through backdoor e-mails.
Hasan, I'm fessing up. We messed up.
That said, clearly more housekeeping is in order. Right now, TechPresident is a group blog with an invited group of contributors. These are people I know and trust, who bring a range of experience and expertise to the conversation. I've also asked them to follow two primary ground rules for their posts, which they are free to make without requiring advance clearance from me.
1. I've asked them to not use the site to electioneer for or against particular candidates. Yes to telling us why X's web strategy is great; no to telling us why X will be a great president. We all have other sites for that.
2. I've asked them to disclose any relationship with any of the campaigns, either as paid staff or consultants or as unpaid advisors. I've also asked them to make clear in their posts if they have a favorite in the race, even if they're playing no role in the campaign. I have no problem with our bloggers choosing favorites; it's inevitable that will happen. I just don't want it to be hidden. As these disclosures are made, I'm going to add them to our "About" page so we have a running record.
All that said, this episode with Hasan Jafri raises an intriguing question for me. Should TechPresident invite any user to blog? This could conceivably work if every post went into a moderation queue. The upside, no doubt, would be more interesting content. The downside, no doubt, would be more behind-the-scenes work for me and Josh Levy, our associate editor, making sure that people weren't using the site to electioneer.
Right now, I'm inclined to take this approach. If you want to blog here, ask me (micah-at-personaldemocracy-dot-com) and we'll talk offline about it. That's how Raven Brooks' great piece on YouTube and the candidates came our way. We are definitely open to adding more contributors. I'm also reading our comment threads (as well as people talking about this stuff on other blogs) and looking for other people to bring in that way.
But what do you think our editorial policy should be? I'm all ears.
more from Micah L. Sifry's blog | login or register to post comments
Recent blog posts
Recent comments
- Yahoo! was not the first
36 min 26 sec ago - Change on Change.gov - it is a start
1 hour 29 min ago - I find very interesting
3 hours 41 min ago - Baby Steps
6 hours 4 min ago - The time it takes to read 3,700 comments...
21 hours 16 min ago - Attention bias
22 hours 9 min ago - This is history in the making
1 day 2 hours ago - First off, link is broken
1 day 9 hours ago - diplomacy
1 day 19 hours ago - So very early in the going
2 days 7 hours ago

print
email
delicious
digg
technorati
$.02 on your web 2.0 effort
Good choice to fess up & ask for help, Micah -- very web 2.0 -- where integrity and humility are the keys to leadership.
The moderation management question has been readily answered by many web 2.0 efforts: allow the community to do it. Even in the short run, your community members will have far more time and energy to rein in partial and bad posts than you ever will.
So simply implement a content-voting mechanism (which there are many flavors of in Drupal), and use it to allow posts to be rating for two factors: 1) overall quality 2) impartiality. You could do it with 2 sets of 1-5 radio buttons all on the same line under each post/comment, with an ajax style form submission for minimal intrusiveness on user experience.
This would allow you to construct a calculated field by user which averages the community ratings of their posts for quality and impartiality. And allow for browsing content or authors by quality, impartiality or both. There are also contributed Drupal modules that do these as well.
Of course, in the early going, you'll want to have as many as people as possible as you know and trust to be good judges to commit ratings on as many posts as possible. But once people see the rating system pretty much works, adds a lot of value and is easy to use, it will take on a life of its own.
Keep up the good work!