July 10, 2006 at 11:00PM Bloglines’ atom support is broken again
It was good while it lasted, I guess.
I can’t figure out why they reverted to the old code. There was no announcement on the site concerning the regression. So much for thinking they’d actually got a clue again.
So here’s the blogline freedbacking: If you’re going to do something like this, warn your users beforehand. And if it’s an accident, fess up and fix it.
Update: In case anybody was wondering, the regression in question concerned Bloglines’ handling of links in Atom feed entries. Predictably, it was Sam Ruby’s feed that bit me first. Just before midnight (UTC) on the 10th, Ryan Phillips (I assume this one) stating “There was a bug in the atom parser the last few days that I fixed today.” I probably ought to have posted up that the error’d been resolved a little earlier. Sorry about that, Ben.
1 On July 12, 2006 at 3:50, Ben Lowery wrote:
Hi there,
Thanks for reporting your findings. We havn’t reverted to our old parser for atom, so I’m very curious what are you seeing that makes you suspect that we have?
Thanks. Feel free to contact me at the email address supplied.
--ben