jeez.. Are you serious? …. think that way: EVERYTHING can be crash and melted. But words CAN NOT.
If having the private key bothers you, simply do not save it in any unencrypted or encrypted copies.
Then you will be sure that no one will steal it from you.
2 Likes
It’s strange to see your statement. Who said phrases or private keys are just paper? When valuing assets, they are stored in multiple media and locations.Besides, those who are interested in logarithmic currencies, who wouldn’t value it: ‘Your private key, your assets’
1 Like
How is Passkey not your private key?
Man, don’t you understand that a device can break down? Next you’re going to tell me you can have four or five devices and they won’t all break down. Well, you never know what will happen or what situation you’ll find yourself in. If you don’t want to be protected by a private key (and you think it’s dangerous for you in any way -which is just ridiculous!), just don’t use it—but let others use it, okay?
I don’t see a passkey as a private key. Maybe it’s the same for you, but not for me. Getting rid of the seed phrase is PURE madness - and I’m surprised it even needs explaining to anyone.
Yes, this way of “organization” has certainly encouraged many new investors, and no one will leave, they will only be delighted that from now on they have to rely on a device, on which one stupid Windows update can blow everything up.
4 Likes
In fact, that the Kong exchange is FORCING all users logging in via ii , to migrate to 2.0 (it’s no longer possible to log in via 1.0) is a sign of irresponsibility and disregard for security standards. REGRETABLE. The longer 2.0 remains unsupported by seed, the more likely first users who have lost access to their Kong accounts will soon experience problems.
2 Likes
When i log into my migrated 2.0 it shows that i still have the seed phrase as a recovery method. But i suppose this will only recover my 1.0 key. But the way it says in the ui is may be misleading.
1 Like
So what does that mean ?!
cant login any more. my user is created via google… its not an upgraded one.. but doesn´t feel safe-
1 Like
but what are you trying to log in to?
Back to ii1.0😂…………….
Reaching out to you via DM to solve this issue.
id.ai for example.. guess that should work flawless =)
Just want to give a little feedback on II v.2:
User Customization: Let users be able to change the name that has been set in II v.2.
User Choice: Developers who are integrating II v.2 should not force users to adopt it. Instead, they should continue to give option to users either to use II v.1 or v.2
Product Maturity: Although II v.2 may be technically production ready, IMHO it’s not yet a fully polished or consumer-ready product. I feel it’s still “a work in progress” because of several issues, including a confusing user flow, a lack of detailed documentation or a user manual, and unclear consequences for certain actions.
4 Likes
Can the login page of IIv2 support a small button/link to forward the login request to IIv1 (login page)? I think that would also be convenient, since if an error occurs, users could use IIv1 as a fallback. Dapps also wouldn’t need to support both IIv1 and IIv2 login options.
1 Like
Thanks for the feedback.
We are working hard to improve 2.0, and the priority is to fix all issues that appear and to bring it to feature parity with 1.0.
We have the upgrade flow for existing users, and we’ll fix any issue that appears during that flow. Most of the issues we have seen so far were with passkeys confusion (we see similar confusions in 1.0) and not problems with the flow in itself.
If you encounter any problem, don’t hesitate to report it with screenshots and a way to replicate. We would very much appreciate it!
Thanks!
1 Like
My legacy that i upgraded from 1.0 i am able to login. Unfortunately the one i created for caffeine used google authentication which seems to not be working but it looks like you already submitted a proposal to fix that?
Yes, I hope it will be upgraded tomorrow.
However, there is a workaround. When logging in with Caffeine, go to the top right, your identity name, click there, then select “Use Another Identity” then “Continue with Google” and select the same account you used before. That should work and from then on you should not see the error.
1 Like
@imuntaner, I’m sure you keep hearing this top question, but could you tell us when caffeine will be available to the average user? (approximately)
Dom addressed some of these questions in one of the posts on X:
Should be fixed now: Fixed Internet Identity Issue With Google Sign In: Proposals 138263, 138262 and 138188
2 Likes
Simple type-O: “Are You And End User?” should be “Are You An End User?” thx