Walletwasabi: Password control should displays asterisks instead of hieroglyphs

[kirillkovalenko]

General Description

Password control should displays asterisks instead of hieroglyphs. This is standard behavior on all major platforms.

Current behavior looks like a bug and is very confusing even for IT people let alone ordinary users, let alone Japanese / Chinese people who actually can read these symbols.

Relates to #439 and #1073.

Please revert this. It makes no sense.

How To Reproduce?

1. Go to 'Generate Wallet' or 'CoinJoin'
2. Type anything info password field
3. See hieroglyphs instead of asterisks

Screenshots

Operating System

Windows 10 1809 x64

[nopara73]

Sorry, but this is our most important feature.

[kirillkovalenko]

@nopara73 Care to elaborate or make first time users somehow be aware of this nice "most important feature"?

[nopara73]

If a programmer cannot have fun while programming, what's the point of programming in the first place?

[cbeams]

This feature creates a negative user experience at a critical moment where the user is still getting their first impression of Wasabi. In the process of scratching my head about what could be causing this behavior, I did consider that perhaps this was the team's way of having a little fun and doing something different with password masking, but dismissed it as something that one would never actually do if one's goal was to create clarity and confidence in an already complex and often confusing domain.

I'm all for the occasional easter egg or other benign ways to have fun, but in an application such as Wasabi, which one must place considerable trust in if one is to coinjoin any significant amount, I think it's well advised to keep fun features that might cause confusion and therefore degrade trust out of the critical path of wallet setup and other key use cases.

With that said, thanks for your work on the project, and I'm looking forward to further exploring it.

[nopara73]

In https://github.com/zkSNACKs/WalletWasabi/pull/1152 I refactored the password workflow, where I explain properly why we do this:

The new workflow will be:

1. Provide only one password at wallet generation.
2. After mnemonics, it'll redirect to Test Password tab, instead of Load Password tab. (Which is actually a Load Password tab, but with a password requirement and password tester menu.)

Rationale and discussion on lost passwords: https://github.com/zkSNACKs/Meta/issues/44

The thing is, I don't want to provide an explanation at wallet generation, because that calms the user down and stays reckless nevertheless.