For example: http://www.bloglines.com/public/techbuzz

If this is in the google reader, I’m missing it.

“Sorting by “date” is actually sorting by the date that Reader sees
items (we can’t really trust dates that are inside feeds since they
are very often incorrect). If a feed switched blogging systems or
otherwise appears new to Reader, then you’ll see it at the top.

However, this should be happening rarely. If you see it consistently
happen for specific feeds, then report it to us.

Mihai Parparita
Google Reader Engineer”

I’m afraid I must object to this philosophy in the strongest possible terms. The dates that are inside feeds are to be respected, by specification. If the dates listed inside a feed are incorrect, then that’s the feed producer’s problem to fix. If Google decides to second-guess the feed author and apply its own dates, there are unintended consequences, especially for brand new feeds. I just started publishing a feed, and Google decided to ignore my dates and apply its own. The problem is that there is no logic to the dates Google chose. They don’t sequence the same way as the dates inside the feed, nor do they sequence the same way as the appearance of entries in the feed. As a result, the entry listed as ‘most recent’ is over a year old, and the actual most recent entry appears near the bottom of the list.

What is even worse is that there is absolutely nothing that I can do to correct this situation, because the tools given me by the Atom specification to specify dates have been deactivated and ignored. Those historical entries that were added all at once will always be incorrectly sorted with entries appearing ‘more recent’ than other entries that were written more than a year later. This is the problem when aggregator developers ignore the specifications and try the ‘fix’ broken or inaccurate feeds by second-guessing the authors. You end up breaking the ability to specify anything accurately, rendering part of the feed specification irrelevant, and taking control out of the hands of the people who most properly and efficiently should have that control: those who are closest to the data.

Please respect the dates in feeds as laid out in the specification.

Bloglines used to force you to save the output (looked like a flat RSS feed) as an OPML which could easily be screwed up depending on the format you used to save it. This went much smoother. Really Simple

In Blogliness I cruise through a 100 feedback using the ‘j’ key to go through a feed and the ‘s’ key to go to the next feed.

In Reader I can space through a feed, but to go to the next one it’s SHIFT-n and then SHIFT-o. Not cool (or efficient).

Am I missing something?

I update my own feed daily, and all other readers display it with no difficulty.
But G Reader puts the publishing date two months in the past, so the new updates are pushed *completely off the page view*.

This has been the case since the beta launch, despite me selecting the ‘Neweset first’ option.