Is it possible to use S3 storage to synchronize data between different devices?

[zhouzongyan]

Is your feature request related to a problem ? Please describe.
Is it possible to use S3 storage to synchronize data between different devices?

Describe the solution you'd like
Synchronize data between different devices

Describe alternatives you've considered
Because Firebase is not very stable in some regions, a self-hosted storage synchronization solution is needed.
Additional context
None

[Skyost]

a self-hosted storage synchronization solution is needed.

This is planned, I'm currently working on it, but it's not that simple. I need to figure out what's the best approach to achieve that.

[zhouzongyan]

a self-hosted storage synchronization solution is needed.

This is planned, I'm currently working on it, but it's not that simple. I need to figure out what's the best approach to achieve that.

I think we can define an interface, and then implement it based on different storage methods. Later, if someone wants to add a cloud storage synchronization solution, they can simply add a new implementation without modifying any other code.

[Skyost]

@zhouzongyan I’m currently writing the backend using Nitro. One of its advantages is that it’s fully adaptable, both in terms of TOTP storage (it uses unstorage under the hood) and database support for things like user data (via db0). As a result, it will be compatible with a wide range of cloud providers as well as VPS environments.

[zhouzongyan]

@Skyost Okay, I'm looking forward to the feature release. Could you please let me know approximately when it will be completed? I can assist with development and provide testing capabilities. Thank you very much.

[Skyost]

@zhouzongyan Well, I already have an early but working implementation of the backend with authentication + contributor plan + TOTPs storage.

But this implies an almost full rewrite of how the app stores its data. I would also like to replace Material by ForUI in order to have a constistent look on all devices. That will also require a lot of work (& additional tasks like new screenshots, new docs look, etc.).

I also need to find the best strategy to migrate current users data. Of course, all ideas and PRs are welcome 🙂

To summarize : it's going to be a big release and it's not ready yet (and neither will be in january in my opinion).

[Skyost]

I've not opened a PR yet, but made some public progress : https://github.com/Skyost/OpenAuthenticator/tree/custom-backend. The backend repo will also be public, but I still need to make it look more presentable (eg. there's currently no README).

[Skyost]

I've open-sourced the backend code : https://github.com/openauthenticator-app/backend. Feel free to submit any potential issue and/or concern.