
News and ideas compiled for reference by new media design educators and professionals from spring 2001 to fall 2005 can be found in the previous blog.
OJR | CNET | morph | CyberJournalist | Poynter | Hypergene | J-Log | Lost Remote | MediaSavvy | Silicon Valley | Holovaty | Small Initiatives | Yelvington
Featured links from the CNET Blog Network
Apple's "Brick" manufacturing rumors--not so revolutionary?--Rumors are buzzing that Apple has been working on a manufacturing process involving lasers and waterjets and solid blocks of aluminum for the upcoming MacBooks.
AMD to spin off manufacturing--Company is expected to announce a long-expected restructuring of its manufacturing operations.
The hole in Cisco's collaboration story--If Cisco is gunning for Microsoft they need more ammo--in the form of content.
Mozilla: The right attitude for the Web's gatekeeper--Mozilla has a dream of winning, but not in the traditional free-market methodology.

Around 2:15 Pacific Time, CEO Russ Wilding, will be on the TechCrunch 50 stage to launch our latest project. Anyone will be able to kick the tires of this new thing immediately after the talk.
Watch live coverage:
Django, a project I have helped nurture for more than four years (including some time as a proprietary project when I worked at the Lawrence Journal-World) has today reached a milestone: we've given it a "1.0" status. In the world of open-source programming, this means it's stable, well-tested and generally a strong piece of software that its developers are proud of.
Given the milestone, I was reminded of an early Django memory that has stayed with me for years. Soon after we casually open-sourced the framework in July 2005, a Web developer, somewhere many time zones away from Chicago, posted a screenshot of his Django-powered Web site. It was the Django admin login page, and I remember feeling a strong sense of astonishment.
What? Some random guy halfway across the planet, whom I'll most likely never meet, actually took the time to learn and use this software that we'd built? And, what's more, he actually found it useful?
I was quite struck by that. Obviously, we'd intended this to happen -- the whole point of releasing code under an open-source license is to make it available to as many people as possible -- but it was an amazing feeling, nonetheless.
Over time, I've grown accustomed to the fact that, yes, people use Django -- so seeing a screenshot of the Django admin doesn't faze me much anymore. But the cool thing is: Bigger and bigger things are happening, and I still get amazed, time and time again.
A print version of a Django book that I cowrote is actually sitting on the shelf in the bookstore down the street from my house? And, what's more, readers actually pay money for it, given that we released a free version online? People take the time to record a weekly podcast devoted to our community? We formed a non-profit foundation? Google supports Django in its App Engine product? And there's a Django conference this weekend?
It all continues to amaze me, and it all continues to inspire me. Here's to a fantastic community and a great piece of software. Thanks for the experience so far.
We've just added two cities to EveryBlock: Charlotte and Philadelphia! I've written more over at the EveryBlock blog.
Warning: Seriously geeky request ahead!
I'm looking for a way to render arbitrary Web pages -- including CSS and JavaScript -- and access the resulting DOM tree programatically, i.e., in an automated/headless fashion. I want to be able to ask the following questions of the resulting DOM tree:
<div>, <table>, etc.?The rendering must be state-of-the-art, handling advanced CSS that Firefox, Safari and IE handle. It should work on Linux. Bonus points if there's a Python API for this magical DOM tree.
This is all stuff that standard in-page JavaScript could accomplish, but the catch with me is that I need to be able to do it in a completely automated way, on arbitrary pages, on a headless server.
I know Gecko and Webkit provide this, but I'm not sure where to start with them. The docs and articles I've read seem to be focused more on embedding the full browser window in a GUI application than embedding the rendering engine itself and manipulating the resulting pages.
Help! If you have any clues, I'd be grateful if you left a comment or got in touch with me.
Radiohead is holding a "contest" called Radiohead Remix, in which they're inviting fans to remix the song called "Nude" from their latest album. They've released the raw tracks -- separate, isolated audio clips of vocals, guitar, percussion, etc. -- and are encouraging people to remix the tracks to create something different, then upload it to radioheadremix.com. I put "contest" in quotes because there's no prize other than a guarantee that the band members will listen to your remix. But that's still kind of a cool prize.
I listened to a bunch of the submitted remixes on Wednesday and was kind of disappointed that none of the ones I listened to did anything interesting musically. Most of them retained the same techno/electronica feel of the original song, kept the song's melody intact and added a couple of drum beats. So tonight, I gave a shot at making my own remix.
For context, I'd suggest listening to the original song first. You can find it on the "In Rainbows" album or listen to this remix to get an idea of the song's melody/mood.
My remix is called "Nude (jazzy acoustic)," and you can listen to it on the site or using this embedded player:
It uses only Thom Yorke's vocal track from the recording, which means I was able to change the song's chords from the classic Radiohead melancholy to something a bit happier/jazzier. It has four guitar tracks -- two rhythm, one bass and one fingerstyle melody part for the extended fadeout. I cut up the vocal track in six places to fit the rhythm better, but they're in the same order as on the original recording, including the extended wordless vocals at the end.
It's kind of soulful, in a weird falsetto-Eddie-Vedder-ish way, especially compared to the original recording (which is also soulful, but in a much different way!).
If you like it, please vote and tell all your friends to vote! I'd love for Radiohead to hear this. :-)
Attention Python screen-scraping experts! We're looking to hire another full-time developer at EveryBlock. Our site, which just launched a few weeks ago, compiles a wealth of granular geographic data and publishes it on a block-by-block basis. We offer a distinct Web page (plus an RSS feed and e-mail alerts) for every city block in Chicago, New York and San Francisco. We're expanding to more cities and more data sources. And we have a ton of fun features and projects up our sleeves.
This position involves contributions to all of our site's technology and data, with a concentration on screen-scraping public data from government Web sites. Some specifics we're looking for are:
Experience with Django is a nice-to-have.
For more on EveryBlock, check out our launch announcement and this recent interview.
This is an opportunity to work on an exciting and important project with a talented and experienced Web development team. We're currently only four people, so you'll have a lot of freedom and opportunities to make a difference.
This is a full-time, salaried position, on-location in our modest downtown Chicago office. We're a startup, funded by a grant, trying to make the world a better place. Please contact me if you're interested or have any questions. Tell me about the gnarliest site you've ever scraped.
Paul Fahri is right in so many details as he recounts how he deck is stacked against America's newspapers, yet so wrong in concluding that journalism doesn't share the blame. Journalism should share the blame, and journalists are not powerless.
He seems to have a notion that there is some sort of objective standard of quality that has been maintained during the long and painful descent of newspapers from the position they once held at the center of American life.
There is no such standard. Quality of journalism has much to do with relevancy and relationships, and those are moving targets.
The right question is whether newspapers are practicing journalism that's relevant to the lives and the needs of the community. And there lies the problem. The needs of the community have changed. Newspaper journalism, by and large, has not.
I could go off on a rant about how newsroom mossbacks have actively interfered with innovation, especially online innovation, over the last 15 years. There's no point; that's water under the bridge, and even the few remaining curmudgeons recognize that the world has changed (however little they want to deal with it).
The deck is stacked against the newspaper, but newsrooms are not powerless victims in the grip of some irreversible cosmic force. There is still high demand for effective local mass advertising solutions. Newspapers can be that solution -- in fact, they could be the last mass medium standing.
But you can't do it with a 20 percent market penetration, and that's what you'll have if you continue producing a 1968 newspaper in 2008.
Interactive engagement with the community transforms journalistic behaviors.
Transforming journalistic behaviors can lead to vigorous growth in readership.
I've been talking about this for years, using the Bluffton Today readership story as an example. But here's a more recent, and smaller, example.
The Florida Times-Union is a "big old" conventional full-service daily newspaper published in Jacksonville. Like most big dailies, its brand is powerful -- and tarnished in some quarters. To the blogging community, it's just another MSM sellout.
To the twentysomethings, it's just another irrelevancy produced by old people, for old people. I won't even get into the opinions held about the paper by crackpots and political kooks, of which there are plenty in Florida, just as there are everywhere. It's in pretty much the same boat as every other large daily newspaper in the United States.
But something is going on.
A couple of weeks ago, police raided a popular local dance spot and shut it down. That's not a story that most old-people newspapers would regard as important, but Jonathan Bennett, who with Joe Black runs the newspaper's Jaxdotcom Twitter channel, picked up on a Twitter reference to the raid. He "retweeted" it.
A couple of followers immediately responded that they'd been in the raid. This led to some information-gathering and a "just in" story, which of course was "tweeted." A local blogger provided a photo. Before long the raid story had become the #1 most-read story of the day for Jacksonville.com, with hundreds of comments and a real buzz sweeping through the local networked community of twentysomethings.
An old-people newspaper, on top of young-people news. Imagine that.
Rich Ray, director of digital media at the T-U, said "This non-traditional approach has garnered high praise (while strengthening bonds of trust and respect) from prominent local bloggers who usually view T-U efforts with a very cynical eye."
What should you take away from this story? Try this: There are some problems you can't solve. There are some that you can solve.
Newspapers can't survive if journalists throw up their hands and blame everything on mysterious forces. Get back to work and use the tools that are sitting in front of you to connect with the community. Have a conversation. Learn from it. Discover what people care about. And accept that journalism needs to adapt to new social realities.
Newspapers, which replaced the town crier with what became to be known as print journalism, are slowly awakening to a second function that's ideally performed on the Web: the town square. But there's a third role that's being overlooked, and that's the role of community memory.
I've begun using that term lately in discussions of how we need to expand our journalistic processes. We need to move away from exclusive reliance on episodic storytelling and toward the creation of "living resources" that are updated whenever they need to be. I touched on this concept briefly in earlier posts about obituaries, which in many cases ought to be life stories of the living.
Neither the production nor the consumption of news today is necessarily tied to a schedule. We're no longer limited by the daily print cycle or the six o'clock newscast. Most journalists see that as a "publish it now" opportunity, but miss the "maintain it forever" implications.
Jeff Jarvis takes on this topic today in a declaration that "the building block of journalism is no longer the article." He continues: "I want a page, a site, a thing that is created, curated, edited, and discussed. It?s a blog that treats a topic as an ongoing and cumulative
process of learning, digging, correcting, asking, answering. It?s also a wiki that keeps a snapshot of the latest knowledge and background."
As it happens, we're building this capability into the site management system we're stitching together for the various Morris newspapers, beginning with Jacksonville.com, which we expect to relaunch in November. It's a concept we hope to see used in both editorially crafted and community-driven contexts, the latter taking shape along the lines of a local Wikipedia.
As in all cases, though, it's not a matter of technology but one of human behavior. Will old-dog journalists learn new tricks? Will community members contribute to a locally focused "memory?"
Community memory, by the way, was the name of the world's first public computerized bulletin board system, which was operated 1972-74 by a group of hippie ur-geeks in Berkeley, Calif. I love the name.
I'm back in the USA, somewhat the worse for wear. After dodging the infamous "Delhi belly" for nearly two weeks, it hit me just as we boarded Delta 17 for New York and I've been in a stupor ever since.
Worse yet, when I went to the doctor Saturday, Visa had blocked my credit card because I'd used it once at a Mumbai hotel, and of course I had no American money. Half an hour on the phone to Commerce Bank (mostly listening to on-hold messages) fixed that, but I was not happy to be standing there with a 102+ fever.
Driving back from the airport was a strange experience. The roads were nearly empty, like you might see on Christmas morning. The gas stations had 00.9 signs and darkened windows, signifying they were out of gas and closed.
I knew all the "news" about the financial crisis, of course, from watching BBC, CNN-IBN and CNBC India. But the fuel shortage thing was a shocker.
On our first day in India, we overslept, ate Paper Dosa Masala, got caught in the monsoon, missed going to Elephanta Island, found the Gateway of India on foot, fell victim to the ear wax scam, danced in a Ganesh festival parade and covered with red dye powder and white confetti, and had my Nokia phone knocked out of commission by a Bluetooth virus.
Tomorrow we head back to Mumbai's thoroughly awful airport to fly to Goa, a former Portuguese foothold down the west coast.
I'm about to go off the grid -- mostly -- for a couple of weeks. Friday morning I'm pulling Paige, my 15-year-old daughter, out of school and heading for the airport, where we'll board a flight to Atlanta. From there it's on to New York, then a long flight to Mumbai, India, where we'll arrive after 10 p.m. Saturday.
By Monday we'll be in Goa, the old Portuguese settlement on the western coast, where I'm speaking at a publisher and CEO conclave organized by Ifra. After the congress we'll fly back to Mumbai, then take an overnight train to New Delhi, where we'll stay five days. We'll hit the obvious tourist attractions, including the Taj Mahal, but we'll also do what we can to experience local culture.
The Internet, collapsing space as it does, has transformed India into a source of low-priced labor for everything from call centers to software development. However, that doesn't translate into affordable mobile phone and Internet service, so we'll be limited to occasionally connecting from hotels and cybercafes. To save on weight, I'm not even taking a laptop. We'll make do with my Nokia N800, which gives me email, the Web and Skype when I can find a wi-fi signal, but it'll mostly be turned off.
The trip will be good for my daughter, whose worldview will undoubtedly be broadened by the experience. She'll have to write an extensive report for school about what she sees, and self-publish a photo book through Shutterfly.
But it also will be good for me. I can no more turn off the pseudo-news channels on cable TV than I can pass up a Chick-Fil-A sandwich. And neither one is particularly healthy. The U.S. presidential campaign has, sadly, deteriorated into the same lopsided barrage of lies that we saw four years ago. I've noticed that yelling at the TV doesn't seem to make it any better.
Jeff Jarvis is back, and observes that the Newark Star-Ledger put out an edition without any AP content. Tim McGuire writes that Politico's move to syndicate not only content, but also advertising, "could create a marketplace for ad hoc solutions to the newspaper?s need for supplemental material."
It's clear that we're coming to a major fork in the road, one that could profoundly reshape the way nonlocal journalism is created and distributed in America. What's not so clear is what's down that road, or even how many forks we're going to face.
Doing without AP isn't as radical as it sounds. I did it in the early 1980s in St. Louis, when the Globe-Democrat went ex-AP to cut costs and survive a little longer. The Globe was a 220,000 circulation metropolitan newspaper, but it was overwhelmingly focused on local news. "Making do" with UPI, Reuters and a couple of inexpensive supps wasn't all that much of a hardship.
The issue isn't so much whether paper X or paper Y can get by without the AP. It's really a matter of whether the AP can continue to be a positive force in a world in which it's moved beyond its old newspaper base.
And what kind of journalism will it -- and the various "ad hoc solutions" -- support? Hard news? Breaking news? Analysis? Long form? Short form? AP traditionally has been the primary provider of news that's as dull as oatmeal, middle of the road, not particularly deep, and offensive to as few as possible.
What I've seen coming from the AP Washington bureau recently has been painful to watch as the AP lurches around trying to figure out how to do meaningful analysis and instead churning out amateurish opinion.
And what's right for newspapers to run? There's not enough conversation about the question of whether printed newspapers ought to focus on long-form "sink into this warm tub and soak for awhile" journalism or chase the bright-short-timely model. My own preference is for the former -- but if I were in the UK, I'd be reading a national broadsheet and not a "red top" tabloid. Where do the numbers lead us? Is it just a business question?
Last month I described how we're working to build a next-generation news website management system, based on the Drupal platform. Much of that system has been built out and configured on a development server at work, but there's quite a bit of work remaining.
All this week I'm in daylong training sessions with 10 site developers from three Morris newspapers and Morris DigitalWorks. Many are new to Drupal, so we're covering basic site administration, configuration and operations. They're learning the power that comes with the Views, Nodequeue, Panels and Content Construction Kit modules. They're learning how the templating system gives them total control over presentational details.
When we're done, this will be an innovation platform, not just a content publishing and community platform. They'll be able to take an idea into production quickly.
For example, about a week ago a couple of us were talking about Twitter. The Florida Times-Union has a Jaxdotcom account on Twitter that's very active and rapidly gathering followers. Wouldn't it be great to include it right on the new website? We took that from an idea into a finished product in a little over an hour, using the FeedAPI RSS aggregator, a custom content type, an a custom output template for that type. To add some polish, we whipped up a custom output filter that links Twitter-style usernames like @jaxdotcom directly to their accounts.
Open tools and open platforms are great for developers, but what we really want to do is place this kind of power directly in the hands of content producers. They won't have to know a programming language, or how databases work, or even HTML to create special presentations based on database queries. Need a new XML feed? Point and click. When these folks get back to their respective newspapers, they'll become trainers and resources and spread the knowledge.
A friend of mine expressed great frustration at not being able to post a comment on my blog the other day. Because of blog spammers, I have grown progressively less comment-friendly, requiring CAPTCHA tests and moderating every post.
I just signed up for Mollom, a new Web service from Dries Buytaert, founder of the Drupal project. This lets me turn anonymous posting back on, and remove the mandatory CAPTCHA challenge. Mollum performs content analysis and, if it "thinks" a post might be spam, it intervenes with a CAPTCHA challenge. Mollom also tries to detect obscene and violent language, and over time it'll get smarter about that.
Like a lot of Web 2.0 services, Mollom "learns" from its users. If I mark an item as spam, that data gets passed back to the big Mollom brain to help everybody else. Mollom benefits from participation, and low-volume service (which is plenty adequate for personal blogs) is free.
Currently, Mollom claims to catch 99.69% of spam attempts, and it reports that 77% of all comment postings are spam.
The toughest challenge is a subtle one. A lot of spam today is human-written by people who have read something about SEO and go around posting plain-vanilla, meaningless comments like "good job" and "I want to know more about this" -- and then slipping in the URL of the site they're trying to pump in the Google pagerank. It will be interesting to see how Mollom handles this problem. I suspect that a couple will slip through, but one they're marked, those URLs will get the Mollom death penalty. I will enjoy that.
I got an email yesterday from a woman -- I think she's an East Coast real estate agent -- who's just furious at the Associated Press for daring to fact-check some speakers at the Republican convention in St. Paul. "It makes me so mad to see the media pick apart the candidates -- all for their own selfish purpose," she wrote. "I am an independent voter and have not yet decided who will win my vote, and articles like this infuriate me!"
I looked at the story she cited, and as far as I can tell the fact-checking is 100 percent on-target (although she clearly thinks otherwise). Among other things, she's convinced that Barack Obama didn't author any legislation. She says he "just worked with Republicans to have it done" and "Even an everyday citizen could have done that!"
I suppose that it's true an everyday citizen could do it, provided that the everyday citizen managed to get elected to the Senate and, once there, build the support necessary to get a bill through the swampland of committees and subcommittees.
And I don't want to get into a debate over whether a "sponsor" is an "author." Most legislation is drafted and edited by paid staff. Some seems to come straight from lobbyists. But the line Gov. Sarah Palin's speechwriters fed her -- "this is a man who has authored two memoirs but not a single major law or reform" -- was moose poop.
The AP story makes oblique reference to the Lugar-Obama Cooperative Proliferation Detection, Interdiction Assistance, and Conventional Threat Reduction Act of 2006, which is certainly a major piece of legislation, but my favorite is the Coburn-Obama Federal Funding Accountability and Transparency Act of 2006, which mandated the creation of USASpending.gov, an online database that tells you exactly where our money's been going.
Go there and try it out. Just for fun, take a peek at the federally funded spending trend for Alaska.
John McCain signed on as a cosponsor of that bill. As it gained momentum, a total of 43 signed on as cosponsors. One who did not was Alaskan Sen. Ted Stevens, who put a "secret block" on the bill in an attempt to kill it.
But I'm not trying to get into the politics of it. I'm personally more interested in what all this says about how and why people consume media.
Underlying this interaction is an unpleasant truth of human nature. We don't seek information and illumination as much as we seek validation.
Dissonant information -- anything that conflicts with what we think we know, and/or want to believe, is initially rejected. Information that reinforces our world view feels much better.
This phenomenon actually drives a lot of media consumption.
Here's an example: A suburban homeowner may read city crimes stories with special interest, even though they have no real bearing on the homeowner's life. But that homeowner made a decision to locate in the suburbs -- and perhaps endure a daily 50-minute commute. Stories about "inner city" horrors help validate that decision.
This explains why we watch Jon Stewart, cheer, and laugh. And why else would we read sports pages? We already know who won.
You may notice my use of the word "we." I mean that. Journalists are no less entangled with this desire for validation and reinforcement than everybody else.
As evidence, I point to today's Roy Greenslade blog at the Guardian, in which Greenslade is being taken to task by journalist-readers for being a "doom-monger" for daring to speak truth about the inevitable decline of ink-on-paper journalism.
On the Guardian site and at HoldTheFrontPage, print journalists are making it clear they don't like it one bit.
One admonishes Greenslade (who teaches at City University): "Is it not a bit like a First Wold War general to earn your living training young people and sending them out into a a career with an extremely uncertain future and little prospect of earning a decent living?" Another asks: "Why can't we have a cheerleader for newspapers? If we ever need one, it's now."
Rah.
All site content copyright ©2005 Metromemetics LLC unless otherwise noted.