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
{{ message }}
Repository navigation
RSS feeds with the atom:updated extension do not have correct dates #243
Through the grapevine (I do not know the reporter):
Hey, uh I have a bug report for fluentflame reader: Some feeds, such as https://volpeon.ink/notebook/feed.rss don't specify the post date via but instead with atom:updated, which causes the fluentflame to use the current time for the date and thus treats each post as new every time it syncs.
To Reproduce
See above.
Expected behaviour
Use the atom:updated when pubDate is not present.
I think, if we don't have a pubDate, we should probably assert it's the time in which it was fetched? <atom:updated> is not part of the standard, nor is it a common extension.
Nevermind, it is namespaced correctly. As per the namespace xmlns:atom="http://www.w3.org/2005/Atom", this is allowed. That being said, we could probably extend this to work with dc as well (seen here: https://www.dublincore.org/specifications/dublin-core/dcmi-terms/).
Activity
CrystalSplitter commentedon Oct 24, 2026
I think, if we don't have a pubDate, we should probably assert it's the time in which it was fetched?
<atom:updated>is not part of the standard, nor is it a common extension.CrystalSplitter commentedon Oct 24, 2026
Nevermind, it is namespaced correctly. As per the namespace
xmlns:atom="http://www.w3.org/2005/Atom", this is allowed. That being said, we could probably extend this to work withdcas well (seen here: https://www.dublincore.org/specifications/dublin-core/dcmi-terms/).CrystalSplitter commentedon Oct 24, 2026
Opened #245 to handle this.