Hey Thomas, I've actually been working on device sync for gPodder, but I'm a only a Python novice so it's been more of a learning project for me. I actually started by copying the sync.py code from 2.20 into the 3.01 codebase, and figuring out how to get it working, which involved adding back in various settings, some object model tweaks, and making a couple of changes to the SQLlite db. I didn't want to commit to adding in device sync since I had no idea how long it might take me, which is why I didn't say anything before. However even if a lot of it needs to be thrown out it was still worth my time :) I've only been working on filesystem-based syncing, under GTK though, but from what I can tell, my changes wouldn't break other UIs, these other interfaces just wouldn't show any of the sync menus / commands in the interface. Anyway, I've got it 95% working at present. My last issue is trying to get the episode published date to show up correctly in the custom sync rename. But, I still have a number of questions The first of course is even whether the approach to syncing used for 2.20 is even something you wanted to carry over into 3.x. Additionally, would it be ok for me to add in filesytem-based syncing into GTK only, since that's the platform I'm using? It seems that the core sync functionality is platform independent, but I wouldn't be able to make or test the sync components of the UI for other platforms. How do you handle changes to the SQLlite db structure (additional columns to the tables)? Is that even something you'd want to do? Also, I could conceivably add in ipod support since I had an old iPod shuffle floating around somewhere, but I don't know about MTP. Let me know your thoughts. I'm happy to rework the sync using JSON if that's your preferred approach - I imagine a lot of the settings & UI updates that I've made will be unaffected anyway. Hoping to get device sync back in gPodder soon (and then enhance it!) Joseph