-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gpodder.net stabilization: archive inactive users #830
Comments
Personally, I'm happy with using gpodder.net as a sync between devices. Thanks for your hard work in keeping this project going. |
The account purge is a necessary step to make gpodder sync work. It can very well be a sync service from now on, but it's vital to keep the exploration services (directory) up |
My main use of gpodder is being able to sync podcast subscriptions and listened episodes on AntennaPod app. This is the only solution if a person wants an open-source podcast app while being able to sync. Regarding the purging or inactive users, I totally agree, it is a must. |
The main draw to gppoder for me was being able to sync listen state between my phone and anywhere else. Even with syncing currently struggling, I'm quite happy to wait for the archival process to see if it allows me to sync everything more easily than adding everything manually each time, because that's the biggest pain point that I haven't been able to easily solve elsewhere. |
We will most likely archive inactive user accounts end of March - begining of April 2025.
See https://gpodder.net for the announcement.
This issue is to track this process and to gather input from the community about it. It will be open for the month of February.
For comments on the archival process (what should be archived, etc.), please go to #829.
If you have thoughts on gpodder.net features that could be removed, please let us know here.
I have a bias towards progress/download sync between a user's devices vs gpodder.net as a podcast directory.
What do you think?
The text was updated successfully, but these errors were encountered: