# Feeds with misinterpreted dates

**URL:** <https://discourse.netnewswire.com/t/feeds-with-misinterpreted-dates/381>\
**Category:** App\
**Tags:** bugs\
**Created:** [September 12, 2026, 11:42pm UTC](https://discourse.netnewswire.com/t/feeds-with-misinterpreted-dates/381 "2026-09-12T23:42:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ADobkin](https://discourse.netnewswire.com/letter_avatar_proxy/v4/letter/a/3bc359/32.png) [@ADobkin](https://discourse.netnewswire.com/u/ADobkin)\
**Post date:** [September 12, 2026, 11:42pm UTC](https://discourse.netnewswire.com/t/feeds-with-misinterpreted-dates/381/1 "2026-09-12T23:42:23Z")

</div>

I’m not sure if this is a feed parser bug or if the publishing sites are not following the standard properly. However, I have several feeds where the dates are being misinterpreted, for example:

[CrowdStrike Blog](https://www.crowdstrike.com/en-us/blog/feed/)

[NBC New York](https://www.nbcnewyork.com/?rss=y)

[NBC Miami](https://www.nbcmiami.com/?rss=y)

I assume these last two have the same exact issue since they appear to be using the same publisher and URL parameter format. However, the first one is a completely different source.

These appear to be active feeds with valid pubDate tags, but NetNewsWire interprets their dates as epoch (12/31/1969 or 1/1/970). Some of the updated posts in these feeds appear with slighly later dates such as January 1-11, 1970 and April 1-11, 1970. It is possible I added them 11-12 days ago, and they have just been counting up since then.

Any ideas or suggestions on how to fix this?

---

<div class="post-metadata">

**Author:** ![brent](https://discourse.netnewswire.com/user_avatar/discourse.netnewswire.com/brent/32/7_2.png) [@brent](https://discourse.netnewswire.com/u/brent)\
**Post date:** [September 14, 2026, 4:28pm UTC](https://discourse.netnewswire.com/t/feeds-with-misinterpreted-dates/381/2 "2026-09-14T16:28:03Z")

</div>

These feeds are all using invalid dates. Here are feed validator results:

[https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fwww.crowdstrike.com%2Fen-us%2Fblog%2Ffeed%2F](https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fwww.crowdstrike.com%2Fen-us%2Fblog%2Ffeed%2F)

[https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fwww.nbcnewyork.com%2F%3Frss%3Dy](https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fwww.nbcnewyork.com%2F%3Frss%3Dy)

---

<div class="post-metadata">

**Author:** ![ADobkin](https://discourse.netnewswire.com/letter_avatar_proxy/v4/letter/a/3bc359/32.png) [@ADobkin](https://discourse.netnewswire.com/u/ADobkin)\
**Post date:** [September 14, 2026, 6:57pm UTC](https://discourse.netnewswire.com/t/feeds-with-misinterpreted-dates/381/3 "2026-09-14T18:57:09Z")

</div>

Thank you for checking. I was not aware of the validator site. I’ll try to report the issue to these publishers, although I’m not sure if they will be willing to fix it.

---

<div class="post-metadata">

**Author:** ![RogParish](https://discourse.netnewswire.com/user_avatar/discourse.netnewswire.com/rogparish/32/167_2.png) [@RogParish](https://discourse.netnewswire.com/u/RogParish)\
**Post date:** [October 9, 2026, 1:30am UTC](https://discourse.netnewswire.com/t/feeds-with-misinterpreted-dates/381/4 "2026-10-09T01:30:14Z")

</div>

I have a similar problem with [Aero-News Network](https://www.aero-news.net/news/rssfeed.xml)

When I tried to validate their feed, the validator got 403-forbidden!

---

<div class="post-metadata">

**Author:** ![brent](https://discourse.netnewswire.com/user_avatar/discourse.netnewswire.com/brent/32/7_2.png) [@brent](https://discourse.netnewswire.com/u/brent)\
**Post date:** [October 9, 2026, 1:41am UTC](https://discourse.netnewswire.com/t/feeds-with-misinterpreted-dates/381/5 "2026-10-09T01:41:15Z")

</div>

> [@RogParish](#):
>
> [Aero-News Network](https://www.aero-news.net/news/rssfeed.xml)

They’re using `Wed, Oct 07,2026 08:06:32PM` which is not a valid date format.

It should be `Wed, 07 Oct 2026 20:06:32 GMT` instead. (Doesn’t have to be GMT, but it should be a 24-hour time and a time zone instead of just `08:06:32PM`.)

Also: they’re using a `pubDate` element for the date inside an RSS 1.0 feed. But `pubDate` is not part of RSS 1.0. Should be a Dublin Core date instead.

(NetNewsWire would pick it up anyway, but other RSS readers might not.)
