Three Scalability related links for today

Dare Obasanjo: Dark Launches, Gradual Ramps and Isolation: Testing the Scalability of New Features on your Web Site

“Esoteric Curio”, the blog of Theo Schlossnagle, author of “Scalable Internet Architectures”.

b-list: Media and performance: There’s simply no way around this.

“Global naming leads to global network effects.”

First, a reminder about what makes the Web, the Web….

W3C.org: Architecture of the World Wide Web, Volume One: 2. Identification:

In order to communicate internally, a community agrees (to a reasonable extent) on a set of terms and their meanings. One goal of the Web, since its inception, has been to build a global community in which any party can share information with any other party. To achieve this goal, the Web makes use of a single global identification system: the URI. URIs are a cornerstone of Web architecture, providing identification that is common across the Web. The global scope of URIs promotes large-scale “network effects”: the value of an identifier increases the more it is used consistently (for example, the more it is used in hypertext links (§4.4)).

Principle: Global Identifiers

Global naming leads to global network effects.

This principle dates back at least as far as Douglas Engelbart’s seminal work on open hypertext systems; see section Every Object Addressable in [Eng90].

What are the global – public – URI’s of Facebook? What are they in regards to any social network for that matter?

This is an important train of thought to consider when debating how Facebook and other social networks influence our relationship with Google, and the entire Web.

Facebook’s growth devalues Google’s utility – it devalues the public Web – at least how it is described in “Small Pieces Loosely Joined” and the Web’s own architecture document.

This is why Scoble can’t be more wrong when he says “Why Mahalo, TechMeme, and Facebook are going to kick Google’s butt in four years” because Facebook and other social networks are going to not only affect how we use Google – but will eliminate the utility of the Mahalo’s and TechMeme’s of the world – because they too rely on a robust and growing *public* URI ecosystem.

Dare: Why Google Should be Scared of Facebook:

What Jason and Jeff are inadvertantly pointing out is that once you join Facebook, you immediately start getting less value out of Google’s search engine. This is a problem that Google cannot let continue indefinitely if they plan to stay relevant as the Web’s #1 search engine.

What is also interesting is that thanks to efforts of Google employees like Mark Lucovsky, I can use Google search from within Facebook but without divine intervention I can’t get Facebook content from Google’s search engine. If I was an exec at Google, I’d worry a lot more about the growing trend of users creating Web content where it cannot be accessed by Google than all the “me too” efforts coming out of competitors like Microsoft and Yahoo!.

The way you get disrupted is by focusing on competitors who are just like you instead of actually watching the marketplace. I wonder how Google will react when they eventually realize how deep this problem runs?

None of this invalidates Scott Karp’s riff on Scoble’s main point – there is a growing role for “Trusted Human Editors In Filtering The Web”. Our friends, our families, our communities. Not just machines and algorithms.

My favorite and fellow bloggers, Slashdot, Salon, the home page of the NYTimes, Philly Future, Shelley Powers, Scott himself, my news reader subscriptions, are all trusted humans, or representations of trusted humans, filtering the Web for me.

There’s nothing new to that fact that people play a direct role in how we discover what may interest us on the Web. It goes back to Yahoo!’s earliest days. Back to links.net, back to the NCSA What’s New page. It goes to the heart of what blogging is all about.

People have been way too hung up on Digg’s voting algorithms and forget that what makes Digg, Digg is its community of participants.

People forget Slashdot outright. As they do Metafilter.

So it still comes down to trust – What organizations do we trust? What systems do we trust? What communities do we trust? What people do we trust?

And just how do we share that with each other?

Social Software Rule: “Personal Value Precedes Network Value”

Bokardo: The Del.icio.us Lesson:

The one major idea behind the Del.icio.us Lesson is that personal value precedes network value. What this means is that if we are to build networks of value, then each person on the network needs to find value for themselves before they can contribute value to the network. In the case of Del.icio.us, people find value saving their personal bookmarks first and foremost. All other usage is secondary.

As people use Del.icio.us more, and in order to gain more personal value, they use tags to be able to find their bookmarks later. Tagging isn’t even the primary function of Del.icio.us. Most of the tagging done on Del.icio.us is done secondarily, and for personal use.

The social value of tags on Del.icio.us is only a happy side-effect. Even though most of the ink spilled about Del.icio.us is about the social value, it’s really not the reason why people use it.

Similar to Google aggregating links that were originally created for taking readers from one document to another, Del.icio.us can aggregate tags in order to find out how people value content. If 1,000 people save and tag the same bookmark, for example, that’s a good sign that they find value in it. But to think that people tag so that this information can be aggregated is to give people a trait of altruism they just don’t possess.
Blinded by the Aggregation Light

Unfortunately, the ability to aggregate has blinded many software developers to think that tags are a cure-all to the success of their software.

An Ajax RSS Reader

William Lazar cooked up a sweet RSS reader you can read about on his blog using Google’s Ajax Feed API and MooTools.

Part of me wants to whip up a Popurls page using this, that stores what feeds you want to see in a cookie. Something like that could take only a few hours, with minimum feed tech knowledge.

What’s exciting about Google Gears

A lot of folks are going gaga over Google Gears and its capability to enable partially connected web applications (web applications that can run offline).

Here is a paraphrase from a comment I left at Burningbird (Shelley Powers’s blog is one of my favorite places to discuss web technology and how it relates to society, politics, and more):

What really interests me about Google Gears is the local web server.

It’s the Dave Winer Fractional Horsepower HTTP Server idea (from back in 1997), that’s finally come of age.

Just what is possible when each of us have our own web servers, running on our desktops?

Immediately you think p2p heaven. But the possibilities for building collaborative apps is just massive.

I know, I know, for anyone who knows Perl, Python or Java, it’s never been too much of a big deal to spin up your own webserver, but this looks like it makes it more than simple – it makes it practical.

If I’m reading it right, you’ll need some form of centralized web app to co-ordinate collaboration across machines, which is no big deal.

The web’s about being connected. And it’s the online possibilities that Google Gears opens up that are rather mind boggling.

Flex, Flash, and Comcast Interactive Media’s Fan 4.0 Alpha

The team I belong to at Comcast, Comcast Interactive Media, released an alpha version of our video player, The Fan, this week.

You can give it a try here. If I say so myself, it’s pretty sweet.

While more information is available on its official cimLabs page, including links to give feedback, I’d like to point you towards one of its developers, Arpit Mathur, and his blog entry about it.

This version of The Fan was built with Adobe’s Flex and Arpit has a lot to share about the project. Feel free to leave a comment and tell him what you think.

As Arpit mentions, we’re on the lookout for Flash developers. But there’s more to the CIM story than Flash. In fact, the development stack we use at CIM resembles what Bruce Eckel proposed in a piece called “Hybridizing Java” on Artima a while back. We are looking for experienced Web developers of all stripes to join us. Check out cimLife for more.

Update:

Arpit’s post about the new version of the Fan is earning some buzz.

RIApedia: Comcast Launches New Flex Based Video Site

Masable: The Fan – Comcast’s New Flex Video Site

Ryan Stewart: Comcast jumps into Flex 2 for media content

Shelley Powers: Cool Thingie

Update:

Aaron Held, my manager at CIM, checks in with more about Flash, Java, and The Fan.

————————

Follow the linkage on Techmeme.