https://bugs.kde.org/show_bug.cgi?id=454553
--- Comment #7 from JonOfUs <jonat...@flueren.eu> --- > I'm not sure but I think at a certain point in time Kasts did have such a > toggle. :) That was before it was able to sync with anything. > It might indeed be useful to reintroduce it. > > Anyway, if we're discussing the scope of syncing full sets of episode > "played" states across devices, then, in my opinion, it would be advisable > to extend the sync API to include such field explicitly. Maybe also add a > "queued" state or "queue position", although that might not be implemented > by all apps? 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. 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) -- You are receiving this mail because: You are watching all bug changes.
