Add ability to save coin IDs and amounts across devices

[tagawa]

Original suggestion by @Daven- :

_I was thinking of adding a username to the site (no password) to save coin amounts. So you could "login" with the username on different devices and it would save/update the coin amounts locally from the db amounts. I check the site on my phone and desktop and its kind of annoying updating amounts two times.

Curious to hear your thoughts on this. I'm not seeing any immediate security or privacy concerns unless the user writes their name and address as the username or something lol_

[tagawa]

I like the idea of saving the coins and amounts. Would be particularly useful for smart TVs where inputting text and numbers is usually so awkward.

The company I work for, DuckDuckGo, has a similar arrangement for saving settings in the cloud without saving personal data. See the Cloud Save box in the settings page here: https://duckduckgo.com/settings

In this case, a password is used but no username, and it's encrypted in the browser using jsSHA. In other words, only the encrypted password and the settings data are stored in the remote database.

Although a username for Crypto likely wouldn't contain any personal info, I think it's a good idea to encrypt it anyway, for a couple of reasons:

• A username could be linked to other online accounts. The case could arise where a user's coins grow to millions of dollars in value and they then decide they don't want that username publicly connected with the coin data.
• The encryption, if using an in-browser one-way function like jsSHA, is easy and very low overhead.

The disadvantage is that there's no way to discover or restore a user's lost data, but that a) reduces support effort, and b) is not the end of world. They presumably have wallets or accounts if they need to check their coin amounts again.

Either way, yes, sounds like a good idea to me, if you don't mind setting up a database or some server-side string storage.

[Daven-]

Encrypting the username is a good call! I'll look into jsSHA. Losing the users information wouldn't be a huge issue since the amounts would be saved locally as well and like you said they should presumably have that info somewhere else.

Cool I think I'll go for it when I have free time, maybe use firebase or some other light weight key value service. Thanks for your input!

[tagawa]

Sounds good. Actually, I've used Fieldbook for personal projects as they have a free tier. It's basically an online spreadsheet with an API for reading/writing data. There are similar alternatives as well but I can't remember their names.

[codingo]

Any progress on this one?

[Daven-]

Sadly no. It hasn't been a pain point for me since I don't buy or sell often. So basically I haven't been annoyed into implementing this feature. I'm not sure I ever will tbh.