PC Forum

I’m at PC Forum this week. Monday saw the pitches of 9 startups (including edgeio)

Here is the movie of their 2 minute infommercials.

Microformats at Mashup Camp

I’m at Mashup Camp. Tantek is moderating a session on microformats.

I just made an hcard. Here is is 🙂

photo
Keith Teare

edgeio
44 James Avenue

Atherton,
CA
94027

+1-650-331-1998

edgeio

I have been gratified to see all the coverage about edgeio since I demo’d it last week at SDForum’s Search SIG, and Rob Hof’s first post. Everybody seems to like the concept. You can track the discussion here and here.

Mike posted on Techcrunch and on the edgeio blog.

For those who like to know the background, just a few pointers.

Philosophically: tagging – it seemed to me – was the thing that could enable RSS to be leveraged as an application layer enabler. Basically, the idea of RSS carrying a payload for an application. Using the “listing” tag to enable a decentralized listings marketplace was and is, in my view, only a start. It can enable users to use their blog for listings. In future I would expect many more applications to be built using various tags as their starting point (podcast and videocast and photocast seem obvious ones). Indeed if you combine the “listing” tag with the “services” tag and one of those today you would be creating a subset on edgeio focussed on podcasts, videocasts and photocasts.

The exciting thing for me is the idea that edge content and applications can enable each other. But additionally that the applications can be a vehicle for the distribution of that content. edgeio – the name – is the word edge with an I and an O. The I stands for “In” and the O for “Out”. We will have API’s for all edgeio content and allow both individuals and other applications to re-publish our data in new and unpredicatable ways. Want listings on your gadget blog, just call our API (we will have a widget for this) and you can have gadget specific listings on your gadget blog. And so on..

How it started: I first came up with the edgeio idea in late 2004, whilst working with the Real Time Web team at VeriSign, as an external consultant. Mike and I began working on it almost immediately and then added Vidar Hokstad (back end engineer) and Matt Kaufman (product manager) to the team in early 2005. Fred Olivera has done front end work since last October. His role is more or less complete now (great job on the design by the way).

I’m looking forward to seeing how all this plays out. Thanks for the – so far – gracious and positive reception.

Update:

Good discussion on Pete Cashmore’s Mashable post.

Phil Sim disagrees with Pete. Has some critical points.

Note:

At some point soon we will try and aggregate the critical remarks on the edgeio blog. We’re pretty heads down on getting edgeio launched so this may take a couple of weeks but rest assured we are reading all remarks and will both be thinking about them and learning from them.

Teare’s theorem: The first law of RSS (updated)

Umair has a post about why the “Rise of the Edge“? is something highly disruptive to orthodox Internet companies. In “Umair Rocks”? Fred Wilson says he wants to understand better what Umair means here, and plans to spend the time doing so.

For me the key is to comprehend that “the edge”? is a concept that only makes sense in a networked world. In a network “the edge”? is “the people”?. And “the edge”? plays the role of both subject (consumers) and object (creators).Blogs are a great example of the edge. Multi-player gaming is another example. Of course the edge is not yet highly diversified. But with the emergence of AJAX and Tagging the diversity of edge content is set to explode. Inputs from the edge to the center and Outputs from the center to the edge (old fashioned IO where the center plays the role of a hub, not a destination) become more important than web 1.0 aggregators that primarily serve as silos of content.

The growing role of the edge – as the originating point of content and the end point of its consumption – forces the redefinition of the the role and meaning of the center of the network. Content hosting is now a peripheral function (at best a means of having an index). Content discovery and distribution takes over as the primary role of the center.

Googlebase isn’t yet getting this (it is so far based on too centralized a publishing model). Craigslist, with it’s centralized publishing model, and evidenced by its recent outlawing of Oodle from taking it’s content, also isn’t getting it.

Yahoo – which has made some smart acquisitions – also begins to look out of date in this world. It seems to have no concept of enabling the edge; it is a network center seeing the edge as merely a source of user generated (read cheap) content and of potential subscribers to it’s centralized system. Opeining it’s API’s is a move in the right direction, but then the limits need to be removed. Even Flickr is centralized from a publishing point of view, albeit with good feed api’s for that centralized content. How much better would it be if you could publish photos and albums to your own blog and have Flickr acquire them, organize them and distribute them.

In a few weeks Mike and I will launch edgeio (note: for geeks it’s meaning is clear – edge content consumed (The I) and then re-disributed (the O). For my mom it’s just a cool word, spoken with an Italian accent, edge^ee oh). edgeio may well help clarify the possibilities of the new edge based network we all now use and inhabit. At least that is one of its goals.
edgeio-base :-)

edgeio is founded on a law we believe in. This is the first articulation of the law and we may be able to improve on it. But for now (until Dave; Mike; Scoble; Jeremy or others gives feedback :-) )

…the first law of RSS is:

“The value of edge published data (say a post) is directly proportional to the velocity of it’s consumption and re-production, that is, the number of input and output operations it goes through each day”?

RSS has enabled data to be freed from the confines of it’s initial point of publishing and to re-appear, through an RSS or ATOM feed at another point in the network. This takes place in a p2p (I read your feed) and an edge to center (I republish your post) and then a center to edge (others read my version of your post and so discover you) manner. As a post is consumed and republished, it, and the links to the original that are generated, create growing awareness, attention and probably traffic value which may or may not have a $ value.

edgeio has been built as an enabler of a more diverisified edge, with a role as a hub in accelerating the velocity of data as it travels around the network. We can’t wait to show it. We are now on the final UI usability tests for a beta. Shouldn’t be too long.

Links

Bubblegeneration Strategy Lab
Umair Rocks
Techcrunch
edgeio

Beattie on RealNames

Russell Beattie ay Yahoo has a lengthy post about RealNames. It’s a generous and thoughtful piece. Thanks for the link Russell.

There are a couple of things worth knowing.

Firstly RealNames didn’t really crash in the bubble. At least not directly. We were profitable and growing fast (about 120% a quarter back in Q1 2002.

Secondly, we had an awesome business model. Resellers all over the world were selling Keywords. Most uptake was in China, Korea and Japan where we were the only way to make local languages useable as navigational addresses. We had pretty strict controls on ownership but we were able to segment nations into seperate namespaces. Today we would do local keywords too.

Thirdly, we were doing 1 billion resolutions a quarter in Q1 2002. That was page views that MSN lost to us because we were able to provide direct navigation to a web page from a keyword. Microsoft decided to close us down in order to regain those page views. Search this blog for the story.

There is a patent. You (Yahoo) own it through your acquisition of 3721.

I still own all of the code and the domain name. 🙂

Google launched Dbase, circa 1985, but with less functionality.

Google launched GoogleBase last night. What a disappointment. Whilst Google Reader clearly points to somebody at Google “getting” the importance of edge published content and real-time indexing, GoogleBase is a throw back. Basically a dumb flat-file database system for the world to throw content into. It’s actually embarrasing for the whole of Silicon Valley. I know insiders who desperately do not want their name associated with it. Can’t say I blame them.

Not to be abusive but why would millions of people who run web sites, and databases, and blogs, suddenly feed stuff into GoogleBase (an act of duplicating their already web based data into another database run by Google)? Maybe to get better search results. But this is an act of pure laziness from Google. The same results could be achieved in a manner far more consistent with the distributed data model that the world is currently flocking to. Google, just define a few extensions to RSS, make it easy to publish a feed with those extensions, and suck in the feeds. It works!

Oh well. Back to work 🙂

Update: well I guess the primary reason this is disappointing is that we expect Google to innovate. This just isn’t innovative. See Mike Arrington’s assessment on TechCrunch

An Awesome web 2.0 post

Fred Wilson has an awesome post covering what is novel and new about web 2.0. Posting, subscribing and tagging are all discussed. Fred’s views mirror entirely what Mike and myself are discussing at Archimedes Ventures, and a little in public at TechCrunch. We have also experimented a little at EarningsCast. Try a search for the tag “earningscast” at Technorati – here . We have a major project close to beta that embeds this philosophy deep within it’s genes. Fred, we love ya man!

Apple and Intel

The news is of course everywhere. But what does it all mean. Here are some random thoughts:

1. Steve Jobs is a great decision maker. Despite the obvious risks and short term concerns (stock price, consumer confusion and so on) he had made a call to shift Apple up a gear by embracing a chip roadmap that can serve for a decade or more. Two years from now the stock holders will be cheering. Five years from now he will be lionised as a saviour.
2. Apple had no choice. IBM just isn’t able to deliver.
3. CPU flavor is increasingly unimportant. The fact that an OS can run on top of many different architectures (look at Linux) is now normal. An OS vendor is not locked in to any particular CPU vendor.
4. Even OS’s are fairly unimportant. Most of the software we all use runs on top of any CPU and any OS.
5. The future is about content and the ability of a company to serve its customers. These make hardware and even OS’s a commodity. Want margins, get into the software as service business real fast (like iTunes for example). These may also drive hardware sales. Without them there will be no sales.

Open Win API Emails

Many emails, some of which make the same point – that OpenWin API would just be another JAVA (See emails below).

 

To be clear – I am not proposing an interpreted code environment with its own language. I am proposing a series of API’s that are bundled together and can be assumed to be on many Windows machines. These API’s – like Microsoft’s own .NET Framework – would allow developers to build code on top of them. The difference would be that these API’s would sit between applications – such as IE – and the OS.

 

Microsoft’s ability to hard code its applications to the OS, and to its own web services, like MSN Search, would be heavily constrained if not made impossible.

 

The API’s would include open and standards based code for key services like web navigation, dns resolution, search, white and yellow page directory services, authentication, messaging, alerts, p2p file sharing and so on.

 

By organizing the collective distribution power of all those with an interest in an open OS and web services infrastructure, Microsoft’s OS domination could be made irrelevant – without having to distribute a competing OS.

 

I’ll follow up with more on this – maybe some diagrams – during the next few days.

 

 

Open Win API?

OK so here’s an idea.

I got to thinking about Microsoft’s Win32 API’s. They are its crown jewels. So far, RealNames had focused on DNS as the problem. Its limits were experienced around the world as intense irritations. Especially in Japan, China, Taiwan, Korea, India, Russia, Israel, Greece, Turkey, Thailand and the Arab world.

Microsoft has essentially frozen innovation in the naming area. By favoring its search engine over true innovation it has held back progress as surely as the Church did during the dark ages.

So … how about we build a layer on top of Windows. An OpenWin API so to speak. This API would sit on top of the Win32 API, and whatever succeeds it. It would stand between applications and the Windows OS. It would be open and free. Developers would be encouraged to write to it instead of to Win32’s.

In my opinion this would be a great way to push Microsoft’s OS down – to the level of a service. The “real” API would be the OpenWinAPI.

Think about it. No longer any need for Linux or a whole new OS. We could use the boring parts of Windows and its widespread distribution as a platform on which to build a truly OpenWin API. All Windows Apps would work on top of the OpenWin API. In the era of desktop applications talking to web services this is possibly the only way to insert control in between Microsoft and the Internet.

The calls the browser makes to the wininet.dll could be intercepted and new innovative features could be available to it through this OpenWin API. Innovation would again be in the hands of the users and the development community.

I really like this idea.

In fact, I could even be persuaded to invest time and money into it.

How many people would download it? How many of the Dell’s Compaq’s and Gateway’s would pre-install it? My guess is all of them.

We would effectively be implementing the separation of Microsoft’s OS from its applications, by inserting open middleware between them. That would also cut off Microsoft’s ability – through the OS and its applications, to monopolize access to web services. I have registered open-passport.com. Truly open and federated authentication should be the first app in the OpenWin API application suite. Single sign-on through a trusted third party should be the goal.

Of course Keyword navigation could live on too. We could support third party search [Google comes to mind, and Overture] as the default.

Email me with ideas, suggestions and comments.

9:31:00 PM