Entries tagged “standards”

The Web in Danger

I love the Internet. I love lots of things that are on the Internet. I have less love for things that want to undermine the Internet.

Tim O'Reilly, The War for the Web:

If you've followed my thinking about Web 2.0 from the beginning, you know that I believe we are engaged in a long term project to build an internet operating system. In my talks over the years, I've argued that there are two models of operating system, which I have characterized as "One Ring to Rule Them All" and "Small Pieces Loosely Joined," with the latter represented by a routing map of the Internet.

The first is the winner-takes-all world that we saw with Microsoft Windows on the PC, a world that promises simplicity and ease of use, but ends up diminishing user and developer choice as the operating system provider.

The second is an operating system that works like the Internet itself, like the web, and like open source operating systems like Linux: a world that is admittedly less polished, less controlled, but one that is profoundly generative of new innovations because anyone can bring new ideas to the market without having to ask permission of anyone.

I've outlined a few of the ways that big players like Facebook, Apple, and News Corp are potentially breaking the "small pieces loosely joined" model of the Internet. But perhaps most threatening of all are the natural monopolies created by Web 2.0 network effects.

One of the points I've made repeatedly about Web 2.0 is that it is the design of systems that get better the more people use them, and that over time, such systems have a natural tendency towards monopoly.

And so we've grown used to a world with one dominant search engine, one dominant online encyclopedia, one dominant online retailer, one dominant auction site, one dominant online classified site, and we've been readying ourselves for one dominant social network.

Doc Searls, Beyond Social Media:

Missing in action is credit to what goes below private platforms like Twitter, MySpace and Facebook — namely the Net, the Web, and the growing portfolio of standards that comprise the deep infrastructure, the geology, that makes social media (and everything else they support) possible.

Look at four other social things you can do on the Net (along with the standards and protocols that support them): email (SMTP, POP3, IMAP, MIME); blogging (HTTP, XML, RSS, Atom); podcasting (RSS); and instant messaging (IRC, XMPP, SIP/SIMPLE). Unlike private social media platforms, these are NEA: Nobody owns them, Everybody can use them and Anybody can improve them. That’s what makes them infrastructural and generative. (Even in cases where protocols were owned, such as by Dave Winer with RSS, efforts were made to remove ownership as an issue.)

Tweeting today is in many ways like instant messaging was when the only way you could do it was with AOL, Microsoft, Yahoo, Apple and ICQ. All were silos, with little if any interoperabiity. Some still are.

Chris Messina, The Death of the URL:

The rise of the “app store mentality” is a direct attack on the web, and on the very nature of free discovery and choice built upon URL-based hyperlinks. By depriving us the ability to pick and choose which “stores” we shop from on these devices — we’re empowering a new breed of middle men and ceding to them monopoly control over our digital experience. The architecture of the web was intended to withstand such threats — but that all changes when the hardware makers get into the content business! Even though developers are beginning to see the dark side of this faustian bargain, the momentum is huge — and big business smells money.

By removing our ability to navigate, choose, and share freely — these app stores are exchanging our freedom for a promise that they’ll keep us safe, give us everything we need, and do all the choosing of what’s “good enough” for us — all starting at ninety-nine cents a hit.

We cannot say we were not warned. We will not be able to say "nobody saw this coming". It's clear that, even those who are privileged by access and wealth and the ability to amplify their own voices have anticipated that we'll all be disenfranchised by the private companies that own and control our networks of communication. And yet, most of our effort and ambition in the technology industry are not going towards building for the open web. Most communities that are disadvantaged are still trying to win on networks that they don't own and will never control. Most of us are still cheering when the most powerful voices in culture and society embrace closed networks, instead of properly criticizing them for doing so.

I am still optimistic; Apple's control over smartphone usage with the iPhone today is but a sliver compared to AOL's enormous control over Internet access a decade ago, and AOL still eventually crumbled in the face of open standards. But the web's victory over the proprietary networks that have been built on top of it is not inevitable — it's going to take lots of hard work. And right now, it's not just the attention that's disproportionately lavished on proprietary platforms that want to undermine the open web, it's the money too. We'll have to turn those strengths into weaknesses if we're going to undo the trend towards disempowerment and centralization that's going on right now.

This, for me, is a social issue, a cultural issue, and a political issue, not just a technological issue. Perhaps we need to speak of it that way more often, to make the stakes clear.

I've seen a number of people make reference to Facebook's application platform without knowing a lot of background about some historical examples that might be useful to learn from. So, since I remember a good bit of info about these things, I figured I'd share it for future reference.

In 1995, Microsoft believed that its proprietary development tool, codenamed "Blackbird" would be the dominant platform for creating rich online experiences. While it would eventually evolve into a tool that created reasonably standard HTML, Blackbird's ability to make attractive and pleasing aesthetic experiences for MSN was considered a no-brainer to replace regular HTML for anything that needed to seem polished. It wasn't an unreasonable assumption at a time when most browsers were showing ugly text on a plain grey background with almost no advanced layout or design.

In 1999, AOL believed that its proprietary development tool, called RAINMAN (Remote Automated INformation MANager) would be the dominant platform for creating rich online experiences. While it would eventually be replaced by tools that created reasonably standard HTML, Rainman's ability to make attractive and pleasing aesthetic experiences that integrated seamlessly into the AOL client was an effective replacement for HTML for tens of millions of users who wanted a polished and social first experience on the Net in the late 90s as they first got online. This wasn't an unreasonable constraint to impose on the experience at a time when having a rich interactive experience meant downloading complicated browser plugins for video, or configuring temperamental client software just to read email.

AOL was always secretive about Rainman, and remains so to this day, even though Rainman has been largely retired in favor of standard HTML, which has let AOL open up much of its proprietary content to the public web. But Microsoft really wanted to get the word out about Blackbird. There were even conferences for developers, to promote Blackbird for their applications. Ironically, MSN would reverse direction from Blackbird almost immediately after launch, eventually building much of its original content around a small vector plugin called FutureSplash. One big reason you have Flash in your browser right now is because MSN aggressively distributed millions of copies of the FutureSplash plugin with all of their client software, and eventually, with Windows itself. But that's a whole 'nother story.

Back in late 1995, the venerable Release 1.0 newsletter offered an analysis of Blackbird that's well worth reading in its entirety. Some highlights:

Microsoft's challenge is to make MSN flourish soon, so that it won't be eclipsed by more open systems, making Blackbird irrelevant, or at least obsolescent. ... The question at hand is whether Microsoft's networked-application architecture makes it beyond MSN's walls and becomes more commonly used. The innovations Netscape is introducing, described above, make this a difficult task. This is where the battle between proprietary operating systems and the Internet is being fought.

...

Microsoft wants Blackbird to be an inviting environment for third-party tools. The pace of technological change will help. Connectivity will change all standalone applications, making many obsolete. With Blackbird, Microsoft is attempting to offer traditional Windows applications a viable path to re-create and re-validate themselves in the networked world. ... Blackbird has its own representation format, the Blackbird Markup Language (BML), which is a variant of HTML enhanced to be OLE 2.0-aware.

In 2007, Facebook has released its proprietary development platform, codenamed F8. Blackbird was to provide better presentation, and Rainman promised better social abilities, than open standards of their time made possible. F8 promises a combination of both aesthetic and social capabilities, with the key feature of the platform (presented as an "innovation") being the social APIs for friends lists. F8's ability to create broadly-distributed social applications that integrate seamlessly into the Facebook environment offers an experience that, for now, exceeds what publicly-available social APIs can do. It's not an unreasonable behavior that people are building and using applications on the platform today.

  • Just like Blackbird, Facebook's APIs offer more features than the available open standards do today.
  • Just like Blackbird, Facebook's APIs have inspired conferences and development toolkits and a lot of reactive responses in the industry.
  • Just like Rainman, Facebook APIs offer native integration with social functions like buddy lists.
  • Just like Rainman, the user experience for integrating those applications is far easier than the equivalent behavior on the open web.
  • Just like Rainman, Facebook's APIs support applications that have millions of users, users that the conventional wisdom says could never be displaced.

It's not true to say that Facebook is the new AOL, and it's oversimplification to say that Facebook's API is the new Blackbird, or the new Rainman. But Facebook is part of the web. Think of the web, of the Internet itself, as water. Proprietary platforms based on the web are ice cubes. They can, for a time, suspend themselves above the web at large. But over time, they only ever melt into the water. And maybe they make it better when they do.

Some links:

  • We're opening up the Social Graph. Six Apart, where I work, is committed to helping create, promote, develop for, and popularize the open standards that will be needed for helping grow social platforms from Facebook or anyone else.
  • The O'Reilly Radar Research Report on Facebook's application platform. Interestingly, given the Release 1.0 report I quoted above, that publication has evolved into Release 2.0, which is now an O'Reilly publication.
  • Jason Kottke on "Facebook vs. AOL". He covers much of the fundamentals that I've discussed here, and helped inspire me to offer some more concrete examples of the history of these sorts of efforts.
  • Somehow I'd missed it at the time, but Scott Heiferman had drawn the analogy to Rainman first. I still feel people aren't very familiar with that point in web history.
  • Graphing Social Patterns, the conference on Facebook and its applications that Dave McClure is currently hosting.
  • The circle of web life, another similar historical lesson.
1

Explore This Site

About Dashes.com

I'm Anil Dash, and I've been blogging here since 1999, writing about how culture is made. You can contact me at anil@dashes.com or +1 646 541 5843.

1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009
  Jan Jan Jan Jan Jan Jan Jan Jan Jan Jan
  Feb Feb Feb Feb Feb Feb Feb Feb Feb Feb
  Mar Mar Mar Mar Mar Mar Mar Mar Mar Mar
  Apr Apr Apr Apr Apr Apr Apr Apr Apr Apr
  May May May May May May May May May May
  Jun Jun Jun Jun Jun Jun Jun Jun Jun Jun
Jul Jul Jul Jul Jul Jul Jul Jul Jul Jul Jul
Aug Aug Aug Aug Aug Aug Aug Aug Aug Aug Aug
Sep Sep Sep Sep Sep Sep Sep Sep Sep Sep Sep
Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct
Nov Nov Nov Nov Nov Nov Nov Nov Nov Nov Nov
Dec Dec Dec Dec Dec Dec Dec Dec Dec Dec  
Close