mirror of
https://github.com/LBRYFoundation/lbry.com.git
synced 2025-09-01 17:55:10 +00:00
Update 206-feb-19-update.md
This commit is contained in:
parent
e2d31461ea
commit
13363c916e
1 changed files with 1 additions and 1 deletions
|
@ -89,7 +89,7 @@ We are currently in the process of a large metadata upgrade to both claims and c
|
|||
|
||||

|
||||
|
||||
### Cross Device Sync Coming Soon {#sync)}
|
||||
### Cross Device Sync Coming Soon {#sync}
|
||||
Cross device syncing, especially related to wallets, has been a hot topic around LBRY for the past few months. It’s definitely a much needed feature to enable users easy access on multiple devices, and also one that must be carefully designed, especially when it comes to security and privacy. In order to sync wallets, we need to be able to store wallet data for users in an encrypted fashion. Even so, it’s still a fairly large risk to store multiple wallets in a single place without the right security measures and design in place. After collaboration on requirements and implementation details between our engineers, we feel we’ve come up with an approach that’s both secure and will offer a great experience to our users. The LBRY SDK will be responsible for providing new API calls that will allow getting and setting of synced data to include wallets and channels (will require user a user password and enable hashing of all data), which will then be security transmitted to our API server, and tied to the user’s email/account (and once again encrypted/salted locally). Initially we will not be allowing password recovery options (i.e. through a 3rd party / 2FA Key), but our design will allow for it in the future. We’ve completed the initial legwork on both the SDK and API side. Our goal is to first roll this out on Mobile (since backup procedures are not user friendly), then expand to the Desktop app and later on to LBRY Web.
|
||||
|
||||

|
||||
|
|
Loading…
Add table
Reference in a new issue