Feature Request
A feature you'd like to see
Currently there is a choice of either Microsoft or Google and there is are reasons to not use either.
There is WebDav, but a backend for that is complicated and needs NextCloud or something similar.
How about a docker container that contains a simple server, that could run on something like a Raspberry Pi or TV app. Your DB needs to be more than one place, that's all.
That server simply take connections from Tusk
The server would do regular internal backups to a specified count.
Alternatives you've considered
There are none if you have a Google or Microsoft account or a NAS locally.
The file mechanism does not work as it copies the file into the browser.
Additional remarks
Maybe use web-sockets or MQTT? I am not a browser app developer so I don't know what the browser sandbox permits. Or rather than record base it could be file based using SCP.
Perhaps have it such the locked DB is stored in the browser and a sync app copies the changes to the remote side.
That way you have at least two copies of the DB without the need to actually ensure the single storage
location survives a disaster.
Feature Request
A feature you'd like to see
Currently there is a choice of either Microsoft or Google and there is are reasons to not use either.
There is WebDav, but a backend for that is complicated and needs NextCloud or something similar.
How about a docker container that contains a simple server, that could run on something like a Raspberry Pi or TV app. Your DB needs to be more than one place, that's all.
That server simply take connections from Tusk
The server would do regular internal backups to a specified count.
Alternatives you've considered
There are none if you have a Google or Microsoft account or a NAS locally.
The file mechanism does not work as it copies the file into the browser.
Additional remarks
Maybe use web-sockets or MQTT? I am not a browser app developer so I don't know what the browser sandbox permits. Or rather than record base it could be file based using SCP.
Perhaps have it such the locked DB is stored in the browser and a sync app copies the changes to the remote side.
That way you have at least two copies of the DB without the need to actually ensure the single storage
location survives a disaster.