⬆️ integrate with RCX / RoundSync / rClone (or any other cloud backup solution that's FOSS compatible)

[alexanderadam]

trafficstars

Since the README says that Google Drive integration is planned I thought that I might mention that RoundSync or RCX integration would be more helpful instead.

Just a few reasons:

1. You don't have to rely on proprietary libraries or services and therefore this wouldn't hinder F-Droid integration.

2. It also supports other providers out of the box (not just Google Drive)

3. The specific API integration lives in another project so you don't have to struggle with it in case there are any changes for Google Drive changes

4. RoundSync and RCX support SAF so it could work transparently out of the box — you probably only would have to document the integration within one_second_diary. RoundSync's maintainer is also very responsive and tech savvy in case SAF integration doesn't suite one_second_diary's needs.

5. RoundSync and RCX support the native encryption of RClone. So people can encrypt and sync the videos with their Desktop or server systems and yet keeping their private videos secure from spying eyes

[KyleKun]

Thanks for the suggestion, it looks like a great solution, I didn't know about it. If I understood it correctly, the only drawback would be basically forcing users to install RCX app if they want to make cloud backups, right? I have the impression that most OSD are not that tech savvy to do this setup (it's an extra friction, I would prefer to keep everything inside the app if possible), and also that this app seems to inactive for some time (plus, SAF looks to have some issues on Android 11 from what I was looking at the docs) so it concerns me a bit about how long it would still work.

I pretty much agree with all the benefits pointed out, and indeed thought on giving up Google API's integration idea because of F-Droid terms and the general app privacy principle. Do you think there's other way we can make it more easy to users while also not relying on non open source 3rd party solutions? Or maybe I got the wrong impression from RCX?

[alexanderadam]

Do you think there's other way we can make it more easy to users while also not relying on non open source 3rd party solutions? Or maybe I got the wrong impression from RCX?

I have no idea whether there's a possibility to create a nicer and easier way to integrate RCX to be honest but I just asked at the RCX repo and the extRact repo (discussion) whether they see something easier.

[newhinton]

It would probably best if you would implement exporting your data to a user specified folder via SAF. This way you have a generic way to access other storage systems, eg. Google Drive, Nextcloud, OneDrive or whatever other apps provide targets for SAF.

What issues exactly do you mean with android 11? Do you mean the requestLegacyExternalStorage-flag?

To get back to RCX, the workflow that i found working for apps that write their content to storage directly is to just let them do their job, and use RCX' Task to regularly sync them to a remote. It works rather well without having to actually integrate anything.

[alexanderadam]

By the way, I'm using RoundSync now. It has a nice sync feature, it is free and open source software, it works with every cloud and even supports encrypting the data before uploading.

Just in case somebody else is looking for something similar.