This is not one of those switching posts. This is just to show you how broken some implementations are:
Switching might happen eventually, they might also surprise me with a nice implementation of Atom 1.0 that actually follows the rules.
Yeah I switched to Rojo which is -- I guess -- just broken in different ways. Ah well. Someone has yet to impress me with a web-based feed reader.
Hey Anne, why don't you (or your company) build the best web based feed reader? It'd be extremely interesting to see what kind of product would rise out of a group of techie bloggers working making a web based feed reader.
I've contacted Bloglines twice now regarding their problems with Atom 1.0. Hopefully this time something will actually happen - it can't take that long to get rid of the truncation of whitespace near the tags...
The day that they manage to parse Atom 1.0 correctly is the day I scrap all RDF/RSS and go all out Atom.
Just out of interest, Google Reader seems to completely strip the
object element out of this post of yours. It's not only Bloglines that suck it seems, although Google Reader does seem to be a bit more solid than Bloglines in general (haven't done any testing yet though).
I never actually read the news in bloglines. I open them in new tabs. Two reasons:
Norm Walsh reported this issue quite a long time ago. And even then it wasn’t at all new. I’m rather disappointed that such a dumb bug has been around for the better part of a year with no fix in sight.
Just a FYI:
object element does render in Safari 1.3.1,
but does so in a compressed manner, forcing one to utilize the
contextual menu to "Open Image in..." to view the graphic at its
actual/full dimensions. Quite irritating.
I got sick of waiting for Bloglines to fix this and wrote a Greasemonkey script to workaround the problem in the meantime.