Robert Scoble ruffled a few feathers today, when he issued his latest missive against TechMeme's direction, as he sees the blog headlines site moving away from its roots and more toward general news coverage, like Google News. Robert says the site should give higher credence to those sites which are generating discussion, arguing in summary that he with the most links wins. But with TechMeme's proprietary algorithm being somewhat of a mystery, it's interesting to consider what I would see as the ideal blog news aggregation site, and how it would change what TechMeme is today.

For the large part, TechMeme automatically senses what are the hot blog conversations of the day. The more noise, the higher on the page, with those blogs with the highest readership and external links receiving the "lead" and referring or related sites being shoehorned in their shadow. Today's biggest discussions? The continued coverage of Facebook, MySpace and LinkedIn, and the latest developments on Apple's iPhone. Today's news was that the devices have reached the mainland.

To be sure, both stories have tongues wagging. But Robert, looking inwardly, noted that one media site's coverage of Plaxo's new platform was rated more highly than his own dedicated coverage. Looking at referrals from Technorati, he can't figure why The Register would trump The Scobleizer. And he's got a point. If TechMeme's tracking discussions, The Register would be a related item, not the lead.

But I have other issues. It seems to me that if TechMeme wants to treat A-list bloggers equally with others generating news, then those who provide original coverage, or break the news, should be given higher credence. I can't tell you how many times I've gotten to a story before "the big guys" get it, only to be ignored. For example, last night, around 2, I posted that I thought Google Reader was down. A TechCrunch reporter, Duncan Riley, and I traded e-mail, we both visited and commented on a discussion board on the outage, and later, he wrote a story. That TechCrunch got the lead can make sense, as the site has tremendous credibility, and many external links, but not only was my note not the lead, but it didn't even get noted by TechMeme, who instead opted to carry follow-on notes from The Download Squad.

Total Technorati external links to The Download Squad? Eight. Total Technorati external links to my story? Eight. So all things being equal, I'd argue that the site which got the story first chronologically, with original reporting, should be given equal or greater value. But if, due to some mysterious rule, I'm being kicked to the curb for a lack of pre-existing popularity, that seems to conflict with what I would hope is the goal of TechMeme, to deliver the a real-time summary of what's happening now in the blogosphere, and to raise the profile of those bloggers who might not necessarily be household names. Otherwise, TechMeme isn't offering much real value.

Robert jokingly called himself an "arrogant bbbbaahhhhhsssssttttttaaaarrrrrdddddd" for calling for change, and wondering why his efforts didn't make it, and I might come off as a whiner as well, but with extra effort should come extra reward. Duncan Riley and I put in an equivalent amount of effort to find out the truth, analyze the situation and write it up. But as far as TechMeme is concerned, I'm a cipher. I can take the abuse, but I think the blogosphere as a whole would be better served to highlight original reporting from the corners of the Web that are driving value.

It turns out the Google Reader crew jumped into action after their alarm clocks went off this morning, restarting the service after six a.m. Pacific time, following what was an approximately eight-hour outage. There hasn't been any notice as to why the outage occured on the company's product blog, but Mihai Parparita, here and elsewhere, apologized for the outages, saying feeds should be refreshing again. And they are.

The outage came at a less-impactful time for those of us based on the West Coast of the United States, but for those in Europe, India and elsewhere, it couldn't have come at a worse time, staying down throughout the day. Google Reader's news group lit up with reports around the world of frustrated techies who couldn't get their feed fix.

It's clear the redundancy held so dear by Google's mainstream apps, like search, hasn't yet trickled down to the individual apps and lab projects. For those of us who have been early adopters and made these projects part of our daily routine, we can only hope that practice is resolved shortly. Until then, we'll keep backing up our feeds, and watch for future bumps.

One of the things I actually like about the Windows platform is the ability to type in a URL in the desktop environment rather than needing to open a Web browser. While that's a byproduct of their illegal bundling practices that aimed to kill Netscape, I occasionally would like to see similar functionality on my Mac OS X boxes.

So far, readers at The Apple Blog believe a move to integrate Safari with Finder, mimicking Microsoft's move, would be a daft one, arguing that malware and feature bloat are two things Microsoft does that Apple should not. But it's worth looking into in my opinion. I could view boomarks and search Google from the Finder, rather than jumping into Safari, and Apple has all the necessary tools.

That's the background behind my most recent contribution to The Apple Blog, titled Why Not Integrate Safari With Finder?. Per agreement with them, I will not be cross-posting the piece, but instead, have provided a link. Enjoy.

It's not often that I go more than two hours without any new RSS feeds, even if it is in the middle of the night on the weekend. But if I were to believe that Google Reader were fully functioning, then that's what the RSS feed reader would be telling me, as two hours into my Monday, I'm still at zero feeds, and I don't have any solid proof that anything has been delivered since 10 or so Sunday.


Something is wrong. And given that it's so late, and most are asleep, it's a very quiet outage right now. Truth is, if people are saying anything about it, it sure as heck isn't hitting my RSS feeds in Google Reader... for obvious reasons.


Over the last few hours, I know there have been updates, thanks to Technorati, and my own efforts. A story I posted to Athletics Nation around midnight hasn't crossed to Google Reader, nor have my two posts here, or Tony Chung's note on opening up a new GeekWhat forum. As Tony is one of my Technorati favorites, I knew he posted, but otherwise, we've got radio silence in the blogosphere, and as they say, it's quiet... too quiet.

If I lose RSS for any extended period, I just might resort to actually visiting individual sites. And we all know that would be a real tragedy.

Confirmed: Reader is down, apparently for everyone. Google's engineers all appear to be asleep. Additional coverage here and here and here. (TechCrunch is also on the case.)