Jeremy Zawodny wrote:
I'm not seeing that happen.Hmm. That's the feed I saw it with. We fetch hourly, and between the 2:45pm and 3:45pm fetch, the urls didn't change. They did change from our initial fetch at around 2:10pm (when the first user subscribed) and the normal 2:45pm fetch. Maybe it was a one-time thing. Here's a sample just for kicks:Can anyone else reproduce it? If so, what RSS URL? I'm testing with: http://rss.news.yahoo.com/rss/topstoriesand it seems okay.
What we got around 2:10pm or so: http://us.rd.yahoo.com/dailynews/rss/716/1b61ffe3d3e401f8a236c4e4727dcd70/*http://story.news.yahoo.com/news?tmpl =story2&u=/ap/20030826/ap_on_sc/shuttle_investigation What we got at 2:45pm: http://us.rd.yahoo.com/dailynews/rss/716/56c2218fb25259b13bf8066330154de1/*http://story.news.yahoo.com/news?t mpl=story2&u=/ap/20030826/ap_on_sc/shuttle_investigationAgain, we didn't see it between the last two fetches. Perhaps it was a fluke.
Use the guid as an index into the database for the item. But that doesn't tell you if the item's been edited. So you have new items, and updated items.I don't mind the tracking aspect, but because the link changes, Bloglines considers each item as being updated every time we fetch one of the feeds. We track which items each user has read, and when an item is updated, we treat it as an unread item. So users end up seeing items they've already read, over and over.Why not use the guid?
If it's really happening the way you say it is (I'm confirming that internally, but I seriously doubt it), then I'd argue that it's very wrong too.
Thanks, Mark -- Mark Fletcher Bloglines http://www.bloglines.com