KoalaSat
Relays list needs of local backup/restore method
Recently I added some relays to Nostros. I assume that I will lose them if I haven't a backup of them.
Rewriting them from skratch is too much tedious.
So why do not create a local backup/restore method in order to charge it when one buy a new phone?
I think this is in sync with this issue, yo can just export everything https://github.com/KoalaSat/nostros/issues/78
Good idea, but with modular backup like this one. It has taken as reference design from Libretube app.
@serrq Please could you test this prototype and tell me if this fit to your needs? The task is export your backup and then import it.
https://www.figma.com/proto/ZY2QeasyxpDbqzLyHj8zpu/NostrOS?page-id=20%3A59080&node-id=1205%3A91242&viewport=-6203%2C-10606%2C0.42&scaling=scale-down&starting-point-node-id=1205%3A91242&show-proto-sidebar=1
P.D: I missed the modular export screenshot I could add it to the flow but I need to know exactly what you can export or desired options @KoalaSat .
It looks amazing. Might I choose the exact saved location when I perform a backup?
Optional: final draft will have a format like yyyy-mm-dd_nostros.something? It would be useful?
Keep in mind that the backup format you are building will need to be cross-platform. That is that if in two years we will have Nostros for Mac or Nostros for Linux the backup will must run on all Nostros clients.
I was thinking about the default backup file name and I realized that it would be better to write it like this (to understand what your backup is when you move it to a shared computer (typically family) or if you have more than one account to identify it at first glance.)
yyyy-mm-dd_last8keysofyourpubkey.zip
Great suggestion thanks, the only change I would do is the extension, I think .json is the standard and right choice, will help other tools and clients to understand what's the format
Great suggestion thanks, the only change I would do is the extension, I think .json is the standard and right choice, will help other tools and clients to understand what's the format
You are the Messi of the development. 🙏
Great suggestion thanks, the only change I would do is the extension, I think .json is the standard and right choice, will help other tools and clients to understand what's the format
What happen if I make more than one backup in the same day? To the file name I mean... your algorithm will add (1), (2), (3)... etc ???
that's trivial we can add a way machines have to identify every second since 1970, it's called unixtime, that should fix the porblem
that's trivial we can add a way machines have to identify every second since 1970, it's called unixtime, that should fix the porblem
👍