Bug 460727 - Sync between apps
Summary: Sync between apps
Status: RESOLVED NOT A BUG
Alias: None
Product: kasts
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: bart
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-19 19:26 UTC by Roman Šmakal
Modified: 2023-01-17 13:14 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Šmakal 2022-10-19 19:26:33 UTC
It would be great to sync subscriptions, queue and play positions between devices. Maybe using KDEconnect could be a way?
Comment 1 bart 2022-10-19 19:48:25 UTC
Kasts already supports syncing of subscriptions and episode play positions through the gpodder API.
You can create an account on gpodder.net (or alternative servers) or install the nextcloud-gpodder app if you have a nextcloud installation.
This will even allow you to sync with other clients (such as AntennaPod) as well.

Would this suit your use case?
Comment 2 Roman Šmakal 2022-10-20 04:05:25 UTC
It seems it would, but it does not sync anything for me (may be issue only on my side, had no time to find out). I'd still preffer offline variant with kdeconnect though anyway.

But i guess GPodder API makes my FR invalid, so feel free to close it :)
Comment 3 bart 2022-10-20 08:47:25 UTC
(In reply to Roman Šmakal from comment #2)
> It seems it would, but it does not sync anything for me (may be issue only
> on my side, had no time to find out). 

That's probably because of the confusing nature of the gpodder.net protocol.  It will only sync changes that happen after the first login.  So that means that only subscriptions that were added after the first login will sync and the same holds for episode states.  If you login with a first device on a new account and then afterwards log in with a second device, then indeed nothing will happen.

For that reason I've implemented the two advanced option buttons in the synchronization settings.  On the first login, you could use the "push all local episode states to server" button.  In principle, that would trigger a complete sync on a second device if that's added after that "force push".  If it doesn't, then you can try the "Fetch all episode states from server" button on the second device.

> I'd still preffer offline variant with kdeconnect though anyway.

I understand, but it's going to be very low priority.  Kasts already handles two "standardized" syncing mechanisms.  Syncing is quite complicated due to the fact that you have to design a flow that will handle sync conflicts gracefully etc.

If you want local sync without a server, you can always use any sync/backup tool to sync the local Kasts database and enclosure folders across devices, though.
Comment 4 Roman Šmakal 2022-10-20 20:21:46 UTC
Thanks for tips, managed to make online sync to work somehow (relogin on both devices fixed it). Thanks.

If you are not interested in implementing the kdeconnect way, then i guess bug report can be closed
Comment 5 bart 2023-01-17 13:14:45 UTC
Closing now, since I don't see anyone implementing this anything time soon given the existing syncing features.