ReadWriteWeb

Just ask the man who signs my paychecks... or at least, go back to October 2007 and ask Richard MacManus, the founder and EIC of this publication. He would tell you directly and succinctly that ReadWriteWeb is not a blog. That is, by the definition of that time, it's not a one-man show. "ReadWriteWeb has evolved," Richard wrote at the time, "into something different than a blog, which is traditionally thought of as the voice of a single person."

Over the years, the complaints I've received from readers (we all receive some) center around the notion of bias - a tendency to interpret a story with the appearance of a certain slant or, perhaps more accurately, from an angle somewhat askew from the angle most others use in their interpretations. If a blog were truly by and about one person, then the appearance of bias would be impossible to avoid. Typically with publications, it is plurality that enables the reader to see the complete picture of subject matter. Plurality, for any organization, requires organization. And at a time when the Web publishing industry's definition of what we do evolves faster than our ability to do it, organization has been difficult to achieve.

It was NCSA Mosaic that introduced the world to the Web. Since that time, the browser has become the principal software-based element in all the world's digital communications and transactions. It is the harbinger of a very powerful new class of dynamic language interpreters, making JavaScript the unlikely, though undisputed, vehicle for conveying interactive functionality. And for some manufacturers, it is the center of an apps ecosystem unto itself.

So the browser is in no danger of disappearing. But as the Web expands into a delivery mechanism for all forms of applications and services, is a stand-alone, exclusive window into the Web, complete with bookmarks and toolbars and add-ons, truly the most sensible usage model for a system that may yet embrace all of computing? This is a question Mozilla began asking last summer, and whose answer remains inconclusive.

Dave Winer, a man who was key to the creation and growth of blogging, RSS, podcasting, OPML and several more technical standards that helped social media become what it is today, announced this morning that he's working on a new technology, a simple blogging tool that keeps an archival copy of your content on your servers, but pushes it out onto whatever other publishing platform you choose, whether that be Tumblr, Twitter or "whatever new corporate blogging silo is popular next year or the year after."

"The important thing is that you and your ideas live outside the silo and are ported into it at your pleasure," Winer wrote in a blog post today. "You never have to worry about getting your stuff out of the silo because it never lived in there in the first place." This is very good news. It appears that the tool will live first at My.ReallySimple.org (password protected).

Dave Winer yesterday announced EC2 for Poets, a step-by-step guide to help you create a server on Amazon's EC2. His how-to is so easy to understand that we had our own server up and running within the hour. Sure, it may not seem like much that this fairly uninteresting page is sitting out there somewhere, but for this writer, it was an amazing coup.

"It's time to stop thinking about these servers as being things for geeks and start thinking about them as things for people with ideas," Winer said in a podcast roadmap he created for this work. The technology available today is enabling anyone with even the slightest technical bent to get out there and create amazing new things; often taking the technology in directions than the company which created it could have ever imagined.