Engadget News Feed Timestamps off

  • 6
  • Problem
  • Updated 6 years ago
For whatever reason, when I have subscribed to Engadget's RSS Feed, their timestamps on the articles are off by an hour. For instance, if they posted an article at 1:00pm, it will show up as being posted at 2:00pm.
Photo of Seth Herren

Seth Herren

  • 5 Posts
  • 0 Reply Likes

Posted 6 years ago

  • 6
Photo of Livven

Livven

  • 23 Posts
  • 2 Reply Likes
I've also found that ZDNet's feeds are off by 7 hours. It's a problem with their RSS feeds, not a problem with NewsBlur. You didn't notice these things in Google Reader because it sorted by the time an item was fetched, not the information from the feed itself. I'm currently building a Windows client for NewsBlur that allows you to specify offsets for feeds to correct this, here's hoping NewsBlur itself will add such a feature too.
Photo of Seth Herren

Seth Herren

  • 5 Posts
  • 0 Reply Likes
Yeah, you're right. I contacted Engadget regarding this, and it seems they fixed the problem. It would be nice if NewsBlur allowed us to manually adjust these sorts of offsets, but in the meantime, I would suggest contacting ZDNet to see if they can fix the problem on their end.
Photo of Drew

Drew

  • 18 Posts
  • 0 Reply Likes
All of my Engadget timestamps are yesterday at 8PM. For the past few days, it's always the day before at 8PM.
Photo of lsmartman

lsmartman

  • 3 Posts
  • 0 Reply Likes
had a look at the RSS feed, and the times stamps are correct... feed is at http://www.engadget.com/rss.xml, timestamp is: Tue, 09 Apr 2013 00:28:00

guessing its a problem with the datetime parsing...
Photo of Drew

Drew

  • 18 Posts
  • 0 Reply Likes
I'm not sure if this is a symptom of the same problem, but all of the feed items from Splitsider are coming in with the timestamp 4 hours earlier than when it posted.
Photo of Samuel Clay

Samuel Clay, Official Rep

  • 6514 Posts
  • 1474 Reply Likes
Are you really going to want to manually adjust timestamps? I guess if you could change the time offset for an entire feed might be handy to correct for these issues, but that's a bit above and beyond in terms of expectations from the user, and in the end it really doesn't matter that the time is off. It's a bug on their part, but it's not such a bad bug.
Photo of Drew

Drew

  • 18 Posts
  • 0 Reply Likes
OK, Splitsider appears to be an issue with their own time offsets, so I'll bug them about that.

The Engadget timestamps are still correct on their feed and coming up as yesterday at 8pm in NewsBlur for me though.
Photo of Livven

Livven

  • 23 Posts
  • 2 Reply Likes
Guess it depends on what kind of user you're going for. For me it's really annoying, and the fact that fixing it is technically trivial only makes it all the more annoying. Google did somewhat workaround this issue in Reader, so there's that too.
Photo of lsmartman

lsmartman

  • 3 Posts
  • 0 Reply Likes
I could be wrong... But engaged, tauw, autoblog, etc, all use the same blogging engine... They all return the data the same way... But only engadget is wonkey. The problem is not that the time is off.. it's that finding the next unread item is off... My guess is the date time is not getting parsed correctly, and is defaulting to today's date... Where does the rss parsing code live? Tried looking, but got lost...
Photo of lsmartman

lsmartman

  • 3 Posts
  • 0 Reply Likes
Also, i noticed that Toms Hardware's RSS feed (http://www.tomshardware.com/feeds/rss...) has the same issue...

the pubdate for toms hardware is
Mon, 08 Apr 2013 15:00:00 CEST

for Engdaget, its
Tue, 09 Apr 2013 09:01:00

also, for reference, Autoblog send back:
Mon, 08 Apr 2013 18:00:00 EST

Tauw sends:
Mon, 08 Apr 2013 09:00:00 EST

So, Tom's hardware should be CET and the EST should be added to Engadget...
Photo of Ryan Nobles

Ryan Nobles

  • 8 Posts
  • 0 Reply Likes
I have the same issue for the Engadget feed. It shows as everything is from yesterday at 8pm.
Photo of Drew

Drew

  • 18 Posts
  • 0 Reply Likes
Just now, Engadget started showing up with the right time. Hoping this is fixed.