https://bugs.kde.org/show_bug.cgi?id=454553
--- Comment #8 from [email protected] --- (In reply to JonOfUs from comment #7) > These features in the api sound useful, especially syncing the queue would > be great. But I am not sure whether the Nextcloud-Gpodder api should alter > even more from the original gpodder.net. We already allow syncing by GUID, > which is not specified by gpodder.net. Altering even more could make it more > difficult to allow synchronizing with gpodder.net and Nextcloud-Gpodder in > the same app. > I might discuss this with the repository owner of the api, it would > definitely be a useful feature. Indeed, keeping compatibility with gpodder.net is also important. I'm also not looking forward to maintaining two implementations. :) Just saying that that would be the proper way to deal with it. ;) > I just tested it and it seems like AntennaPod synchronizes the state PLAYED > by POSITION being equal to TOTAL (or probably even by being close to TOTAL, > I think it even has an option for such a deadzone in seconds): > https://bugs.kde.org/attachment.cgi?id=149329 (screenshot of AntennaPod app > next to gpoddersync table in phpmyadmin) Indeed, that's also what my investigation of the source code and output of AntennaPod showed at the time. That's why the implementation in Kasts does the same thing (also with dead zone at the end) to ensure maximum compatibility with AntennaPod. So from a practical point of view, it's not that bad, but it still feels like abusing the API. :) -- You are receiving this mail because: You are watching all bug changes.
