You are viewing a single comment's thread.

view the rest of the comments →

SsupGuys ago

Saving meta from the article:

<meta property="article:published_time" content="2016-12-04T16:10:18-05:00" />

<meta property="article:modified_time" content="2016-12-04T21:08:26-05:00" />

<meta property="og:updated_time" content="2016-12-04T21:08:26-05:00" />

go1dfish ago

Publish date is likely set in the CMS to determine when the article is to be released.

May be when setting a date/current date that it sets the time to a specific time in the morning.

I think this is more likely than the more conspiratorial explanation.

SsupGuys ago

I'm not entirely sure if washingtonian is using wordpress, but every CMS including wordpress set the publsihed time when you START writing an article or SAVE it the first time. This has nothing to do with the time to actually publish an article, it would be also pretty odd to specify an article to the exact second it's supposed to be published.

Anyway, as written/edited, I think it's just a bug on the side of google since the time on article seems to be around an hour after the incident happened.

Malignment ago

Time discrepancy is on yahoo and i imagine other search engines too?

Malignment ago

I think they use Wordpress: https://washingtonian.com/robots.txt

SsupGuys ago

The server time might not be using Eastern Time...

Edit:

This is odd... when searching for the article on normal search, it still displays the article as 10 hours ago, when you search by news it now shows as 5 hours ago. Did They fix something there? https://sli.mg/a/uC2wUW

Edit2:

I was wrong... I'm sorry for confusing anybody but the time I fetched from the archived page was actually from the archived page itself (dating December 05). The lead was wrong so I'm actually more into thinking this is simply a timezone fuckup on googles side.

Freemasonsrus ago

Thank u! I asked about this up top and this helps explain a bit more.