Dear maintainer. Since it seems that there is no way to create an account on the service used to sync, and I (presumably like many others) don't want to run my own nextcloud instance, would it be possible to sync using a webdav URL? Something like webdavs://username:password@host.name/path Then it's a matter of doing LOCK, PUT, UNLOCK, and just GET on the other side. I think a generic web server is easier and more common to host than nextcloud. Feel free to let me know if you think it's a good idea and want some patches. SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Sorry for not responding earlier. First of all: there are other free gpodder-based servers than the main official one, which seems to be broken for a very long time now. So maybe you could search around for one. Then, about the topic itself: I'm afraid that syncing is a little bit more complicated than just sending and retrieving files if more than one client is involved. You really need a server backend that deals with conflicts, timestamps and deduplication. By the way, Kasts is a founding member of the openpodcastapi.org project to define a new, open standard for podcast and episode syncing. The idea is that you would get a larger choice of clients and servers to choose from. That should include some really basic servers, or servers you can get a free account on (like funkwhale). Quite a few client and server projects are already involved. So, given the fact that I'm putting quite a lot of time into that more general project, I don't really have the time nor ambition to support yet another implementation. By the way, if you're interested in syncing only one client (i.e. basically doing backups), you can simply copy the database and the enclosures folder to and from a (webdav) server, which should be easy to script. This should also work across computers if you manually keep track of who did the last update. So, thinking about this last bit: maybe it would be useful to have "backup" and "restore" buttons in the settings that would allow to import/export the database from the Settings GUI? That might go some way towards your goal?
No. I already copy the sqlite db to sync, but I have to do it manually. But even then, doing it with the shell is easier than having to click a button. My thinking was that webdav is much easier to self host. Best