-
Notifications
You must be signed in to change notification settings - Fork 79
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
fix(@profile): copy chat key rather than transformed key #5787
Conversation
Jenkins Builds
|
@anastasiyaig isn't weird from the UI side to have one string displayed and clicking on the "copy" button get something else stored in clipboard? :) |
The UI displayed is "short version of the chat key" but the copy button needs to be the real chat key However I agree this may confuse the user, UI could be different, we should I think have a way to expand to the real chat key The most confusing in the display is not the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The UI displayed is "short version of the chat key" but the copy button needs to be the real chat key
e.g if you want to send your chat key to a friend!
It's the opposite of: #5361
However I agree this may confuse the user, UI could be different, we should I think have a way to expand to the real chat key
IMO we should still copy the compressed key. Backward compatibility is an issue indeed, maybe when clicking on copy button the context menu should appear:
[-- copy compressed key --]
[-- copy raw key --]
The most confusing in the display is not the ... in the middle but the fact that we remove the prefix 0x04
The prefix 0x04 is "removed" because key is compressed and encoded, see: status-im/status-go#1937 (comment)
This is something I would like to have, at least more intuitive. |
@osmaczko Out of curiosity why would you copy the compressed key? When I tried to add a contact I needed the raw key, has this changed too? (edit: I use 0.3 so backward compatibility is not working) Does a user know that they are using compressed key vs chat key? |
fixes #5775 the copy needs to be on the real chat key, not the transformed one used for UI
Because the user should only know about compressed key representation. It's the user interface, joining links and qr codes should be adapted to that. In other words, raw keys should be only used internally.
Answer above.
raw key (only because of backward compatibility) or compressed key -> new app (should work) |
fixes #5775
the copy needs to be on the real chat key, not the transformed one used
for UI