https://bugs.gpodder.org/show_bug.cgi?id=1708
Stefan Kögl <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |CONFIRMED Ever Confirmed|0 |1 --- Comment #1 from Stefan Kögl <[email protected]> 2012-11-07 15:21:24 GMT --- This is actually a design flaw of the internal data structures. Most objects such as episode actions, episodes, etc have some kind of creation timestamp: * episode actions have a timestamp when the action happened * episodes have a release timestamp These timestamps come from clients and podcast feeds respectively and are currently not validated. This means especially, that the timestamps can be larger than UTC now. API requests such as the Device Updates return * a current Unix timestamp * all objects (episode actions, episodes, etc) after the provided "since" value This includes objects from the future (eg episodes with release-timestamp from the future, datetime values with incorrect timezone information, etc). Currently those are returned again when the API is called again with a larger timestamp, as long as it is smaller than the object's "future" timestamp. Bug 1366 has already addresses the problem for episode actions. I'll make similar changes for other affected objects under this bug. -- Configure bugmail: https://bugs.gpodder.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes. _______________________________________________ gPodder-Bugs mailing list [email protected] https://lists.berlios.de/mailman/listinfo/gpodder-bugs
