Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simplify Backup Page #751

Open
rolznz opened this issue Oct 23, 2024 · 2 comments
Open

Simplify Backup Page #751

rolznz opened this issue Oct 23, 2024 · 2 comments
Milestone

Comments

@rolznz
Copy link
Contributor

rolznz commented Oct 23, 2024

Currently the backup page is scary and complicated (requires saving multiple things - see #750).

We could split it into Alby Account vs no Alby Account components to reduce the conditionals.

No Alby Account could have a button to download SCBs (or somewhere else, e.g. on the node page which is shown whenever a new channel is opened and user does not have backups for that channel yet).

Alby Account version can be improved when we implement VSS and remote backup of NWC data.

@rolznz rolznz added this to the v1.13.0 milestone Oct 23, 2024
@jpl-btc
Copy link

jpl-btc commented Oct 23, 2024

Just an idea: For no-Alby Account Hubs, whenever a new channel is opened, include a prompt or a warning somewhere reminding the user to download the SCB (Static Channel Backup) file. It might be a little annoying for power users, but increases the user's security by pushing him/her to download the necessary backup files after each new channel, as it should be, and they may better understand the convenience of having an Account and a subscription.

@rolznz
Copy link
Contributor Author

rolznz commented Oct 31, 2024

This could also be good for Alby Account users who still want to save SCBs locally ("what happens if alby disappears" question).

@rolznz rolznz modified the milestones: v1.13.0, v1.12.0 Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants