-
Website
http://www.scripting.com/ -
Original page
http://www.scripting.com/stories/2009/05/28/googlesKillerApp.html -
Subscribe
All Comments -
Community
-
Top Commenters
-
eas
55 comments · 4 points
-
AndrewBurton
134 comments · 10 points
-
Michael Markman (Mickeleh)
154 comments · 16 points
-
Rex Hammock
52 comments · 9 points
-
malatmals
81 comments · 3 points
-
-
Popular Threads
-
How I develop formats and protocols. (Scripting News)
1 day ago · 11 comments
-
Open is in the eye of the beholder. (Scripting News)
3 days ago · 13 comments
-
Store Twitter URLs in earth's oceans? (Scripting News)
5 days ago · 16 comments
-
Why today's Twitter is like Napster in Y2K. (Scripting News)
5 days ago · 15 comments
-
If you wrote the words you own the copyright. (Scripting News)
5 days ago · 7 comments
-
How I develop formats and protocols. (Scripting News)
1) Wouldn't using the weblogs.com interface limit the use of it too much? A change in an open data set could be just as interesting.
2) Does weblogs' protocol facilitate subscribing (or following)? If not, i would opt for a different protocol.
what #1 did.
2. No but that's what the OPML is for. Again if they want to provide a web
service that allows you to tweak OPML that they're hosting for users, fine
-- no problem. But I want to be able to provide any interface on any other
server anywhere on the Internet without having to flow subscriptions through
any single company's server.
The whole point of this architecture is to make any element of it subject to
competition and thereby give users choice oever every aspect of it.
relying on a single central server. We have Feedburner to thank for that. At
least its problems haven't taken the whole community with it. We must never
rely on a single vendor like that again.
Small Pieces Loosely Joined.
Any component can be replaced.
Choice everywhere.
Laramie. :-)
want. I need these core features, and I don't need updates any more
frequently than once a minute.
http://www.google.com/search?q="search+engine"