It’s just data

Forward Motion!

The Bloglines Team: As we continue to develop new features, small and large, we also make necessary improvements to existing systems. Expanding our support for the Atom 1.0 syndication standard is the latest of these. You may notice duplicate posts coming from atom feeds as we make the switch from the old to the new atom parser. But have no fear, these duplicates will fade away and soon be a distant memory.

Attention weblog shoppers: It is now safe to talk about markup in weblogs!  I can now say things like <xmp> and &#xe9; without Bloglines getting confused.  Hooray!

This is important to me as quite a few of my readers see my posts through the filter that is Bloglines.  Thanks!

Based on a quick sampling, it appears that relative URI references are also handled correctly.  Kudos!

Now the true test of a product isn’t how perfect it is — after all, nothing ever quite meets that standard — but how responsive the team is to bug reports and feature requests.  Given that there is a brand spanking new Atom parser in Bloglines, hopefully the knowledge of how it is constructed is still fresh, and the following requests should be easy:

While there may be bugs in other corner cases, these are the ones that I see as most likely to affect readers of my weblog.

Thank you for the upgrade, and thanks in advance for your consideration of these requests.


Hurray! Clicking through did not nuke all my other unread items!

Posted by Darryl at

Looking at Planet Intertwingly, it appear that atom:titles that appear inside of atom:source elements are being interpreted as the title of the atom:entry.  Furthermore, relative URI references inside of Atom content are not consistently resolved correctly.

It does seem likely that fixing one or both of these will create a new wave of duplicates to appear.

Posted by Sam Ruby at

+1

And an extra +1 for support of atom:updated.

Posted by Jason Clark at

Sam Ruby: Forward Motion!

by znarf [link]...

Excerpt from Public marks at

Bloglines Updates Atom Support

Bloglines speaks!: As we continue to develop new features, small and large, we also make necessary improvements to existing systems. Expanding our support for the Atom 1.0 syndication standard is the latest of these. You may notice duplicate posts coming...... [more]

Trackback from Alpha-Geek.com

at

Bloglines Does Atom 1.0

Sam reports that Bloglines has announced they’re now parsing Atom 1.0 feeds. The first thing I’ve done as a result was to unsubscribe from Tim Bray’s RSS feed (which Bloglines forced me to) and subscribe to his Atom feed. Looking...... [more]

Trackback from cygweb

at

Some of my comments are missing text.  It seems that Bloglines no longer handles content that is of type text

Posted by Sam Ruby at

Bloglines and Atom 1.0

Sam Ruby: “Thank you for the upgrade” Indeed. This is progress....

Excerpt from snellspace.com at

your atom feed doesn’t seem to be playing nice with my.yahoo.com’s rss support, empty hrefs for your article links. anyway, sorry if this is offtopic.

Posted by grumpY! at

your atom feed doesn’t seem to be playing nice with my.yahoo.com’s rss support, empty hrefs for your article links.

Perhaps they have the same bug that Bloglines used to have, i.e., not realizing that the rel attribute has a default (frankly, I don’t know how the spec could have been written much clearer).  Merely by reporting it here (the first bullet), and Bloglines was fixed in under 24 hours.  Now that is responsive!

Posted by Sam Ruby at

Too bad they aren’t responsive to actual user feedback (aka not on a public blog). About 20% of my feeds have not updated at all on Bloglines since they made that post. Including feeds with high subs like the CNET News.com feed or Dilbert comic. You’d think they would want to get something like this fixed ASAP but apparently not.

Posted by Ron at

Bloglines finally do something about their crappy Atom support.

Seeing as they refuse to give proper permalinks on their newslog, I’ve no intention of linking to them, but I’ll happily link to Sam Ruby’s post on it. Kids, throw down your RSS shackles and embrace Atom!...

Excerpt from Talideon.com Linklog at

Perhaps they have the same bug that Bloglines used to have

FWIW, LiveJournal’s syndicated account feed parser has the same bug.

(frankly, I don’t know how the spec could have been written much clearer)

Maybe it should have said “If you write an Atom 1.0 parser by search-and-replace-updating an Atom 0.3 parser you will have bugs!

Posted by Aristotle Pagaltzis at

Perhaps they have the same bug that Bloglines used to have

FWIW, LiveJournal’s syndicated account feed parser has the same bug.

Along the same lines, <comments> with the type attribute left off has always been broken in the Sage extension on Firefox.  I fixed my own copy and submitted a patch, but unfortunately it appears getting the coveted “Most Innovative Upgraded Extension award” in the Extend Firefox contest did nothing to get its maintainers progressing on future versions.

Posted by KevinH at

but unfortunately it appears getting the coveted “Most Innovative Upgraded Extension award” in the Extend Firefox contest did nothing to get its maintainers progressing on future versions.

Milk has snorted out my nose.

Posted by Mark at

Woo-hoo, it’s about time! Now I can desegregate Intertwingly back into my tech folder.

Btw, have you noticed their drag and drop interface for managing subscriptions and folders? It’s nice, and makes me wonder whether that had taken priority over Atom parser improvements.

Posted by Justin Watt at

Sam, this is unrelated, but I’m reminded to mention it every time I post a comment here (apologies if it has already been addressed). How come you forward people to the homepage of your blog after they submit a comment? Redirecting them to the post they just left a comment on is the excepted behavior across most blogging platforms.

Posted by Justin Watt at

Atom 1.0 and Blogger

Bloglines now has Atom 1.0 support, and though there are some problems there still, it’s time for a new target. I’m sure it’s clear from all my posts that I’m a big proponent of Atom 1.0. However, I probably appeared to be a bit of a hypocrite,...

Excerpt from Stephen's Statements at

Redirecting them to the post they just left a comment on is the excepted behavior across most blogging platforms.

My thinking is that once you post a comment, you are done with this entry for a moment.

Posted by Sam Ruby at

Sam, I think you have a bug in your commenting system: a*b

Posted by Sjoerd Visscher at

Ah, nice! Only the preview is broken. I had inserted a &#1; character.

Posted by Sjoerd Visscher at

the preview is broken

Fixed... and improved.  Now instead of replacing illegal XML characters with an asterisk, I replace them with a numeric character reference.

example: a&#1;b

Posted by Sam Ruby at

| My thinking is that once you post a comment, you are done with this entry for a moment.

Speaking for myself, when I’ve commented somewhere I like to see whether my comment actually made it through. Invariably I’ll open up that entry again to double check. I’d say that at least half of the blogs where I’ve commented recently, my posts haven’t survived, so there is some justification for my concern. Not that I’ve had that kind of problem here, but I still like the reassurance of seeing my comment up on the page before I move on to something else.

Posted by James Holderness at

It looks like Bloglines has lost the entry authors.

Posted by Ken MacLeod at

Paul Querna: Posting about Work

From Alpha-Geek.com: I was even able to find a blog of one of their workers – Paul’s Journal – though he doesn’t seem to talk about his $job too much. It is hard to post about $job, because very little of Bloglines backend architecture is considered...

Excerpt from Planet Apache at

Links for 2006-06-21 [del.icio.us]

Sam Ruby: Forward Motion! Post App A SLASHPD PRODUCTION (/pd): Bloglines - CNN Supports OPML Hans on Experience: Welk protocol kan ik het beste gebruiken voor RSS? interesting survey of his readers...

Excerpt from The RSS Blog at

Nice that they escaped the ampersand in “Duplicates; Real & Imagined” even though they didn’t escape the one in “Blog & Feed Search on tap at Bloglines!” - I’d guess I’ll get to read the post about feed claiming in six months or so, once the latter title falls off the bottom of the feed.

Meantime I’m looking at the “preview page” for the feed in Firefox 2/3, which takes what the parser gave it up until it hit a fatal error, and just displays that much without comment, and wondering what the truly right thing to do is: it’s not an accurate preview of what you’ll get from the draconian Live Bookmarks, but then if you’ve told Firefox you want to subscribe with something slack and forgiving it’s not accurate either.

Posted by Phil Ringnalda at

Atom 1.0 and Blogger

Bloglines now has Atom 1.0 support, and though there are some problems there still, it’s time for a new target. I’m sure it’s clear from all my posts that I’m a big proponent of Atom 1.0. However, I probably appeared to be a bit of a hypocrite,...

Excerpt from Stephen's Statements at

Add your comment