You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firstly, I'd like to take a moment to express my gratitude for your work on Osmosfeed. The project is incredibly helpful and well-structured. It's truly been a pleasure to use it.
I'm writing to bring to your attention an issue I've come across while using the Osmosfeed with certain RSS feeds. Specifically, I've noticed that some feeds return a fallback timestamp, "1970-01-01T00:00:00.000Z", when the publication date isn't available. This is happening, for example, with some articles from Google Alert feeds.
While this isn't strictly a problem with Osmosfeed, it would be extremely useful to have a built-in fallback mechanism that could handle these cases. For instance, if the returned timestamp is the Unix Epoch (1970-01-01T00:00:00.000Z), new Date(null), the current date and time could be used instead.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
Firstly, I'd like to take a moment to express my gratitude for your work on Osmosfeed. The project is incredibly helpful and well-structured. It's truly been a pleasure to use it.
I'm writing to bring to your attention an issue I've come across while using the Osmosfeed with certain RSS feeds. Specifically, I've noticed that some feeds return a fallback timestamp, "1970-01-01T00:00:00.000Z", when the publication date isn't available. This is happening, for example, with some articles from Google Alert feeds.
While this isn't strictly a problem with Osmosfeed, it would be extremely useful to have a built-in fallback mechanism that could handle these cases. For instance, if the returned timestamp is the Unix Epoch (1970-01-01T00:00:00.000Z),
new Date(null)
, the current date and time could be used instead.I've attempted to create such a function:
However, I thought it would be better if such a mechanism was integrated into the project, given that other users might encounter the same issue.
Thank you once again for your wonderful work on this project. Your effort is truly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions