Scripting News - Latest Comments in Google's killer app (Scripting News)

Re: Google's killer app (Scripting News)

mackieb — Tue, 09 Jun 2009 05:18:20 -0000

Ah yeah, quite! Low profile boys, those search engines, always forgetting about them :) btw nice to see good ol' AltaVista holding on to the top spot there for 'search engine' - so technically I guess that makes them the nr 1 search engine on the web...

Re: Google's killer app (Scripting News)

dave — Fri, 05 Jun 2009 11:59:22 -0000

#1 is straight from weblogs.com but #2 is what Google does. A little thing called a search engine. :-)

http://www.google.com/searc..."search+engine"

Re: Google's killer app (Scripting News)

mackieb — Fri, 05 Jun 2009 04:48:17 -0000

Dave, #1 and #2, isn't that basically weblogs.com ? Or are you saying go straight to the source where people get the content from (i.e. google et al) and cut out the middle ping server man? Which sounds like you think has an issue as a single central vendor/server (or maybe I'm reading that wrong)

Re: Google's killer app (Scripting News)

Nerdisterrogator — Wed, 03 Jun 2009 20:12:00 -0000

Thanks me for sharing your blog.

Re: Google's killer app (Scripting News)

Nerdisterrogator — Wed, 03 Jun 2009 20:10:59 -0000

Best of luck for the Internet!

Re: Google's killer app (Scripting News)

dave — Sat, 30 May 2009 17:06:12 -0000

Great. I was talking about "at a minimum" features. Add all the extras you
want. I need these core features, and I don't need updates any more
frequently than once a minute.

Re: Google's killer app (Scripting News)

Brett Slatkin — Sat, 30 May 2009 17:03:28 -0000

Hey Dave, this still suffers from the problem with polling, right? But the low-latency goals here are similar to PubSubHubbub (http://code.google.com/p/pu... and SUP. However, SUP still uses polling. Why do sites have to poll each other? Why can't we push content to subscribers (and their aggregators) and eliminate the minute delay? I want posts to RSS feeds to propagate in less than 500ms.

Re: Google's killer app (Scripting News)

m0nty — Fri, 29 May 2009 03:11:10 -0000

Seems like an issue that deserves more than 140 characters, mate. ;)

Re: Google's killer app (Scripting News)

dave — Fri, 29 May 2009 02:43:05 -0000

http://twitter.com/davewine...

Re: Google's killer app (Scripting News)

m0nty — Fri, 29 May 2009 02:36:34 -0000

Ah, righto then. I look forward to your review of Wave in a separate post.

Re: Google's killer app (Scripting News)

dave — Fri, 29 May 2009 02:27:07 -0000

not at all

Re: Google's killer app (Scripting News)

m0nty — Fri, 29 May 2009 02:07:25 -0000

How does Google Wave fit in with this wishlist?

Re: Google's killer app (Scripting News)

aswath — Fri, 29 May 2009 01:29:41 -0000

pubsubhubbub? (http://code.google.com/p/pu...

Re: Google's killer app (Scripting News)

gbattle — Thu, 28 May 2009 21:28:40 -0000

The point is that each search engine uses it's own "magic" as the organizing overlay (they could even be combined). Given that time, in this real-time universe, now becomes a driver affecting the factors for each search engine overlay (decay, aggregation, etc.), the complexity of this delivery would require something beyond real simple syndication. Again, I'll defer to you in this arena.

Re: Google's killer app (Scripting News)

gbattle — Thu, 28 May 2009 21:21:23 -0000

Correct me if I'm wrong, but I believe that your #1 and #2 are being done within Google News already. Granted, Google News is a much more limited universe, but it appears to work exactly as you've detailed. On these two points, it seems as if all you are suggesting is low latency aggregated RSS. Where I disagree is with your #3, especially when using Google. Aggregating blogs that have been indexed offers a much bigger opportunity than low latency delivery. The point should be to offer users what Google News or TechMeme does; empower them with an aggregated RSS stream where the order isn't via a simple time series, but via some indexing algorithm. By adding reputation, diversity, popularity, references as an overlay and breaking away from freshness alone as the organizer of RSS or even Twitter is probably the most value that a search engine can provide. Again, just my $.02.

Re: Google's killer app (Scripting News)

dave — Thu, 28 May 2009 17:53:24 -0000

Thanks Brett. Your words of encouragement mean a lot! Hope all is well in
Laramie. :-)

Re: Google's killer app (Scripting News)

dave — Thu, 28 May 2009 17:52:23 -0000

Perhaps I misunderstood. If so, my apologies.

Re: Google's killer app (Scripting News)

eelcoh — Thu, 28 May 2009 17:30:01 -0000

I'm not sure what that single server has got to do with by comments. Limiting pub/sub to a single server would be a bad idea indeed.

Re: Google's killer app (Scripting News)

Brett Glass — Thu, 28 May 2009 17:21:53 -0000

Dave, I'm glad to see that you've published those ideas, lest Google try to claim and patent them. (Despite its motto, GoogleClick has become at least as evil as any other large corporation and might well do such a thing.) Perhaps those ideas could become part of an effort to compete with Google, which now has more than 75% market share in search advertising -- a monopoly.

Re: Google's killer app (Scripting News)

F. Andy Seidl — Thu, 28 May 2009 17:09:03 -0000

Thanks; that makes perfect sense. I guess I was thrown off track by the singular "killer app" ;-)

Re: Google's killer app (Scripting News)

dave — Thu, 28 May 2009 16:52:42 -0000

It's independent.

Small Pieces Loosely Joined.

Any component can be replaced.

Choice everywhere.

Re: Google's killer app (Scripting News)

F. Andy Seidl — Thu, 28 May 2009 16:48:01 -0000

Dave, are #1 & #2 independent of #3? Is #3 really just a masher of a collection of feeds into a single feed? Or is #3 somehow dependent on #1 and/or #2?

Re: Google's killer app (Scripting News)

dave — Thu, 28 May 2009 16:44:37 -0000

Hopefully by now everyone, including Google, understands the problems with
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.

Re: Google's killer app (Scripting News)

dave — Thu, 28 May 2009 16:42:29 -0000

1. No because I said they could do more than #1, I just wanted at a minimum
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.

Re: Google's killer app (Scripting News)

eelcoh — Thu, 28 May 2009 16:33:02 -0000

My 2 cents:
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.