Google Reader "AUTO" sort – good but missing something…

Google’s newsreader continues to be my favourite way to consume the stupid amount of feeds that I continue to find myself subscribing for. I try to purge from time to time but inevitably I end up finding something new to read. My general rule of thumb now is if I can’t remember anything I’ve read on a given blog in the past week or two I generally remove it – but this post isn’t about that…

Between the week of intermittent access in Berlin and then the Canada Day long weekend I’ve had a few occasions recently where my blog reading has gotten backlogged by a fair margin. Not a huge deal though as Google Reader comes with this handy dandy sort feature called “AUTO” – this sort feature floats the less frequently updated blogs to the top and the noisier blogs to the bottom.

This is generally good but there’s one annoying thing I find the reader doing – because of the sort order it tends to mean that each blog tends to end up with it’s own posts clumped together as you work your way through the unread list. I didn’t realize until recently (when I’ve done a few marathon reading sessions to catch up) how much I actually like the randomness of reading posts from all kinds of people rather than one person’s posts all in a string.

Attaching lead balloons to noisier blogs is a great idea but it’d be nice if they found a way to also randomize it up a bit even if it’s as simple as coding it so no two posts from the same author appear one after another (unless it’s completely unavoidable).

Just my 2 cents…

RSS – Airing your Dirty Laundry for all to see?

As a follow on to “Beware the All Seeing RSS Feed” I was amused to read about yet another “Found in the Feeds” post today on Tom Raftery’s blog. It seems that there was a parting of ways today in the TechCrunch community today after a disagreement between Mike Arrington & Sam Sethi over comments made about the “Le Web 3” show in Paris this past week (another odd story unto itself that’s been filtering out over the past few days).

Tom wrote:

Sam put up a post on TechCrunch UK saying he and Mike had parted ways but that post has been deleted also. I found it in my RSS reader and it said:

I wonder, is this something we’re going to see pop up more and more frequently as RSS spreads (further) beyond the blogging community and how long is it until something important accidentally sneaks out in the world? How do you fix it?

You can get to Tom’s full post here – might be worth a read as the ‘sphere could be buzzing about the “dismissal” for a few days…

Beware the all-seeing RSS Feed…

While I love RSS feeds and they’ve fundamentally changed how I consume information there’s one issue I run into all the time which is not being able to go back and fix a mistake etc. I often find that I publish a post and then notice a formatting issue or a typo I and go back and fix it but I can’t update the post that goes out in the RSS feed.

But along the way I’ve never seen anything quite like the item I came across in my feedreader this evening from the WebWorkerDaily.com blog:


The image is kind of small so for those who can’t read it, it says:

DUDE WE ALREADY DID THIS. MAYBE YOU SHOULD CHECK OUT THE ARCHIVES TO NOT BE REPETITIVE.

Yikes.

Someone clearly deleted the blog entry as the link takes you to this message:

But at the end of the day it’s still out there, and probably many of their loyal readers will see it as I’m going to guess the vast majority of us get their feed rather than visit the site.

So, I guess lesson to everyone: Beware the all-seeing RSS feed.