Times they are not a'changing

Summary:Rojo to fix bugFrom Rojo's Chris Alden on the Rojo blog:Steve speculated that perhaps the "Times doesnt want server-based aggregators such as Bloglines and Rojo to consistently allow permalink access beyond seven days." Fortunately we don't see any evidence of that and in fact believe NYT has done a great job in making their content available via RSS, particularly by including a specific "partner" parameter on the URL for RSS aggregators (client and server alike).

Rojo to fix bug

From Rojo's Chris Alden
on the Rojo blog:

Steve speculated that perhaps the "Times doesnt want server-based aggregators such as Bloglines and Rojo to consistently allow permalink access beyond seven days." Fortunately we don't see any evidence of that and in fact believe NYT has done a great job in making their content available via RSS, particularly by including a specific "partner" parameter on the URL for RSS aggregators (client and server alike).

And more details from Rojo's Kevin Burton here.

Glad to hear Chris is reassured. But I'd feel even better if someone from the Times would explain how (or why) something changed within the past few days after not showing up for such a long time (June in Bloglines' case). Even though I am a regular subscriber to the print edition of the Times, I still check the archives online going back a week or two to catch up as the paper pile grows out of control. The way we discovered this bug was by comparing the feed urls to my NetNewsWire archive, which has saved Times archives since Brent Simmons added a persistent store in a private beta late last year.


More:

From Bloglines' Mark Fletcher
:

The NYTimes problem was a bug on our end. What to un-escape and what not to un-escape is tricky business with all the RSS formats, and we screwed up. Interestingly, this bug has been on the site since June 1, but this is the first we heard of it. A fix has been checked in and we're in the process of testing it now. If all goes well, it should be pushed to the
live site tomorrow evening.

Thanks for bringing this to my attention.

I've alerted Rojo's Chris Alden to the issue, and should hear from him shortly. Assuming the Bloglines fix works, I can then return to wondering what has changed on the Times site, whether inadvertent or a harbinger of things to come.

This just in: Mark Fletcher and I are on the trail of the behavior, having duplicated the issue on his machine. More soon.

Third verse, same as the first. Now the archive wall has moved a day forward to Sunday. Still no response from anyone at the Times. Or Mark Fletcher. Or any of the 1600+ co-subscribers or any of the Rojo beta-testers who might have the same behavior. Since I still have no external confirmation of the problem, I'll continue to shout into the wind but leave it as an exercise to the reader what the impact of this could be, not just on the Times in terms of loss of authority in the blogosphere, but on the hundreds of other media companies grappling with the disruptive effects of RSS and attention.


And thanks to Geek News Central for pointing.


Now back to our movie, already in progress: Podcasting in America, starring Jon E. Appleseed.


Topics: Browser

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Related Stories

The best of ZDNet, delivered

You have been successfully signed up. To sign up for more newsletters or to manage your account, visit the Newsletter Subscription Center.
Subscription failed.