But for people who can live with a longer delay, this could be a solution for them. Of course, there is one drawback: you can not use this kind of synchronization and expect changes to be available on all devices within seconds or even minutes.
GPODDER WEBSERVICE ACCESS NOT ENABLED DOWNLOAD
Any synching software, regardless on which device, will always take care of timestamps and will always see that the most recent version is uploaded to the NC server, so that any device will always download the most recent version.įor example, this is the way I use Osmand (my navigation app) in conjunction with Nextcloud: whenever I save a new favorite location or a pre-calculated route one one device, this new data will be synchronized to all my devices. This file could then be synchronized using a simple service like Nextcloud. To me, a server based solution like gpodder, offers the possibility to sync the data nearly instantly: if I stop listening to a podcast on one device, within seconds the listening position is synchronized and I can pick up any other device and continue listening there.īut what about user, who don’t need this instant synchronization?ĪP could store all its information in one local data base (sqlite) file, whenever some changes are made, whether it’s a new subscription, a positioning info within a podcast, or whatever. I’ve read quite a few articles and discussions about what is necessary to synchronize a podcast app’s data between different devices, and I understand that it takes some API and some data base to store all the information about the subscribed podcasts and their status.īut I still think that there might be a different way to sync this data.
Now the service has been down completely for days, and who knows when (and if!) it is going to come up again. Especially when trying to sync more than 2 devices, there have always been discrepancies regarding subscriptions and their status. To me, gpodder’s service has proven to be quite unreliable, ever since I started using it.
0 kommentar(er)
