Waddup Buzz?

Google seems to be working hard at Buzz. Increasingly it seems to group buzz updates together, like so:

On twitter we long had this problem with the same links and retweets showing up in our streams every so often. It would have been nice if those had automatically been grouped together like in the Buzz timeline, but they weren’t. Twitter fixed this problem by implementing native retweet functionality, which sort of solves the issue. So, the question is: why did Buzz group these particular updates together? To Let’s step into the algorithmic brain of the Google and try to figure this out. Let’s ungroup the updates:

Those with eye to detail will notice the number of updates here. How many were there when they were grouped? 1, 2, 3, 4, 5. Right? And when expanded? 1, 2, 3, 4… huh?

Anyway.

Let’s see if we can discover the reason behind the grouping. Is it content-based aggregation? Probably not, unless Google aggregates programming related content here, which I doubt. Did it summarize the four updates into one? Not at all, the javascript framework update has absolutely nothing to do with the other updates. So what is it then, that made Google feel the other updates were somehow less important than the Javascript one? And why would this be useful to me? The only answer I can come up with is that they were all posted by me around the same time. Except they’re really not posted all at 10:47am, they were posted in the course of about an hour, but Google only polls twitter every few hours or so (it seems). Is time-based aggregation really a useful thing, though?

Google, I think, or at least hope, you can do better than this.