OK, a couple problems with supporting Google Drive if GNOME loses their key:
- No clear way to include our own key. Putting the secret in our source code is rightfully disapproved of by Google. Not clear how GNOME is getting away with it without anyone abusing it.
- No suitable duplicity backend to use. 'gio' only supports GOA's keys. 'gdocs' is EOL and can't work. 'pydrive' is not packaged in Fedora or Ubuntu.
So... I dunno. Seems like the best option is to just prepare a dialog explaining why users can't access their Drive with deja-dup anymore. And what to do about it.
I guess the next default backend would be Nextcloud.
OK, a couple problems with supporting Google Drive if GNOME loses their key:
- No clear way to include our own key. Putting the secret in our source code is rightfully disapproved of by Google. Not clear how GNOME is getting away with it without anyone abusing it.
- No suitable duplicity backend to use. 'gio' only supports GOA's keys. 'gdocs' is EOL and can't work. 'pydrive' is not packaged in Fedora or Ubuntu.
So... I dunno. Seems like the best option is to just prepare a dialog explaining why users can't access their Drive with deja-dup anymore. And what to do about it.
I guess the next default backend would be Nextcloud.