Fix Time for some Feeds

[TheOneImprove]

Steps to Reproduce

1.Fetch the feed entries.

What is currently happening: all or some of them fetch as delivered at the current time and date.

Example Feeds:
Have I been Pwned: https://feeds.feedburner.com/HaveIBeenPwnedLatestBreaches

Almodon (Arabic): https://www.almodon.com/rss

To do

• https://eurasianet.org/rss matches Sep 23, 2024
• https://www.crisisgroup.org/rss
• https://knowablemagazine.org/rss

[jocmp]

hey @TheOneImprove - thanks for the links. both of these sites are using non-standard timestamp formats. in those cases the app falls back to the "arrived at" time for each article. I'll add some code to handle these cases.

[jocmp]

@TheOneImprove - I have a fix up for the first feed that I'll include in the next version. Here's a demo of what that looks like:

I'm not sure I have a good fix for the other feed. That one posts published dates with future timestamps like this article: https://www.almodon.com/politics/2024/9/14/إسرائيل-تجمع-الميدانين-اللبناني-والسوري-إنزالات-الكومندوس-البداية. So the issue for that feed is not a parsing bug.

[TheOneImprove]

In my humble opinion, I think that it might be better to support future timestamps instead of leaving it at the current state.

Just wanted to say that you are really one of the best developers I interacted with.

Thank you for creating this amazing RSS reader.

[jocmp]

That sounds good to me. I'll add handling for future timestamps with #361. Thanks for the kind words!

[TheOneImprove]

@TheOneImprove - I have a fix up for the first feed that I'll include in the next version.

I deleted capy reader and reinstalled the new version from F-Droid, upon importing my subscriptions, I noticed some of my subscriptions come as now.

Here is examples:

• Have I been pwned is still being fetched as now.
• https://eurasianet.org/rss
• https://www.crisisgroup.org/rss
• https://knowablemagazine.org/rss
• https://mises.org/rss.xml

Notice: I just noticed that you released 2024.09.1049 , I will check it out on F-Droid and report back here.

Thank you for your work.

[TheOneImprove]

The bug still exists at the latest f-droid version.

[jocmp]

@TheOneImprove which version number are you seeing on F-Droid? F-Droid's builds usually have a lag up to a week and the fix is available in 2024.09.1049 which I created yesterday.

The IzzyOnDroid version is usually available more quickly if you want to add an F-Droid repo. I would expect that to update to 2024.09.1049 in a day or two.

[TheOneImprove]

I meant the izzyondroid version, I did not know that you release also on the main F-Droid repo.

The version is 2024.09.1049.

[jocmp]

I'm not seeing the issue anymore on 2024.09.1049. Let me know how it compares to what you're seeing. Here's what I have.

Times are correct for https://feeds.feedburner.com/HaveIBeenPwnedLatestBreaches

For https://www.almodon.com/rss future times are saved as the "arrived at" time. This is how Feedbin handles future times and it ensures that there's a specific point-in-time to avoid showing "Just now" or a future date. The problem with future dates is that they may never arrive depending on what the server sends back.

Note how the published date is 5:04PM while the current time is 5:06PM. This is different to how it was previously where the published date was always kept in the future.

[TheOneImprove]

I rechecked on the latest version, the have I been pwned rss has been fixed, the following is still fetched as the current time and then cached(The time is the first time it get fetched:

• https://eurasianet.org/rss
• https://www.crisisgroup.org/rss
• https://knowablemagazine.org/rss

Thank you for your valuable work.

[jocmp]

A small update

• eurasianet.org/rss is fixed with Handle date-only strings #407. I'll include that in the next release
• https://knowablemagazine.org/rss formats correctly in browsers but has inconsistent behavior that I'm not able to fix
• I'm planning on adding support for https://www.crisisgroup.org/rss still. They change the formatting based on the article language so I need to find the correct formatting rules.

Thanks for your patience!

[narinishi]

Hi, Capy Reader is showing all posts from the following feed as being on the current date https://www.the-digital-picture.com/News-RSS.aspx
They are specified as such <pubDate>Sun, 22 Dec 2024 00:00:00 EDT</pubDate>, which is following standards as far as I'm aware.

[jocmp]

@narinishi yep! that's a standard format. i'm not seeing a problem with that feed in my testing.

[narinishi]

@narinishi yep! that's a standard format. i'm not seeing a problem with that feed in my testing.

The specific URL I'm using is actually https://www.the-digital-picture.com/News-RSS.aspx?Cat=Camera-Gear-Review-News
The article which appears first for me is Just Posted: Sony FE 16-25mm F2.8 G Lens Review, which has <pubDate>Wed, 12 Jun 2024 09:00:00 EDT</pubDate>
and First Looks at Sony FE 28-70mm F2 GM Lens Image Quality is right at the end, despite it being the most recent article

All of the posts from The Digital Picture show as being 1 day ago in Capy Reader, which is when I added the feed.

[jocmp]

I'm still not able to replicate this with that category feed. Here's what I was able to see below - the "Just Posted..." is at the bottom of the feed. The "First Looks at..." article appears at the top.

Can you try unsubscribing and re-adding the feed? That would at least confirm whether this was a one-time bug or something persistent.

[narinishi]

Still encountering the issue after re-adding.

[jocmp]

@narinishi thanks for the screenshot. I noticed the time says 06:44. I should have asked sooner - can you confirm what language/timezone you're using? I think this might be a parser issue that assumes en-US.

I was able to replicate your issue by changing my locale to en-AU. If that's the root cause I have a fix that I'll push for the next release.

[narinishi]

@narinishi thanks for the screenshot. I noticed the time says 06:44. I should have asked sooner - can you confirm what language/timezone you're using? I think this might be a parser issue that assumes en-US.

I was able to replicate your issue by changing my locale to en-AU. If that's the root cause I have a fix that I'll push for the next release.

Ah yep, I do have it set to Australia. 24-hour time isn't the default though, I manually set that.