If people can understand username/password they can understand public/private keys. It’s high time we stop with this learned disability nonsense.
Discussion
Right! No more excuses.
You are right, but still it will take time.
And the platform/service which handles that best, will get the masses.
I mean there are lot of people using passwords like “12345” and what else.
They know how to use it but many don’t care much about passwords. As they know there is a way to reset it when they forgot it.
With #Bitcoin private keys it’s different. There is no recovery process if you lose it, and what you lose hurts a lot if you have stacked a lot of Sats.
It’s different and that needs to be learned. And that will take a lot of time for most people in this generation. Even if it is actually quite easy for us Bitcoiners.
Just my 2 Sats.
✌️
We don’t need to develop for these people, this change could be cultural, through all walkthroughs learnings etc. damus does a good job here
If you speak from the perspective of a Bitcoin Core Developer, then I totally agree with you.
As Bitcoin is designed that it doesn’t need you, but you will need Bitcoin at some time.
And it should not be developed to meet the needs of stupid, lazy and what not people.
But services, apps etc, which are building on Bitcoin will need to design their services for the people, as they want to reach as many as possible.
I mean Damus does a good job. But Damus is building on the NOSTR protocol. What they are doing is to design it in a way that even non techies can use the Nostr protocol.
Big social media platforms like Facebook, Twitter, Instagram or TikTok already spent a lot of money for research. Researching UI and UX to get and hold more users.
I could imagine that different Nostr clients could adopt these. One will adopt TikTok, another one will feel like Twitter etc.
But I hope I did understand you correctly and we are not talking about different topics 😅
All you need to do is put a password on their private key to use it. Most private keys I use have a password required to use.
Let them sign in with their password, and keep the private key unlocked for their whole session.
The only difference is that they get the extra protection from pub key cryptography in a way there minds can comprehend.
Passwords are then client specific, they would need to understand and store their keys if they want to use the same “account” on some other client. The ROI of passwords on top of a client isn’t there IMO. Signers do have a place though, something akin to a nip-07 or hardware wallets. But they require the knowledge of how pubkeys/private keys work as well.