One of thing that I find annoying in various decentralized identities is that in 99.99% cases or more it is some awful unreadable meaningless opaque string (obviously either public key or its hash).
Humanity should create more meaningful (human-friendly) form of decentralized identies, that likely could be visualized as some "contact card", optionally with image, with name, and e. g. qr code or other representation of cryptographic material. ⬇️
Discussion
Loading...
Post
@koteisaev I did some thinking about this with MoodleNet based around an 'emoji identifier'.
Basically, a string of emojis that was unique to you. Benefit: like mobile phone numbers in the early days, could could sell the cool ones to the highest bidder.
@koteisaev I'd be something like 🤘 🏴☠️ ⚽ 🥃 🧀
@dajb Yes, this can be more readable, but still confusable, if long.
E, g if one contact ID is 🍎 🎈 🛏️ ⚽ 🍔 🐹 and another is 🍎 🎈 ⚽🛏️🍔 🐹
But if emoji library is big enough, such palette can be used as visualizable form of 4-word-address and these 4 emoji can be short enough to not get confused, at lest not _that_ often.
@koteisaev Yeah, always going to be a balance between usability and confusion.
There are ~3,953 emojis in the latest Unicode set, so even with a string of 3 emoji, that's actually ~61,773,466,377 unique combinations... 😅
@dajb Whoa I was not aware of that (how many emojis are out there). But still, even with that it is not so big in cryptography scale, it is like 2^36, while most common key lengths I seen for ECC these days represents space of 2^256. So if use that emoji palette it would require more emoji slots
Imagine if Alice and Bob decided to communicate via some software where there is some directory of people. Let it be chess club members or company employees.
Or it is social-media type of app with searching for people you contacted before and people discussing in a thread.
And imagine that there are two people with same name, e. g. Bob Atkinson. And one is the person Alice is looking for and other is other person, let it be Malory imposter or even simply unrelevant person with same name. ⬇️
And for Alice (ok, for me too!) these two Bobs, one with keys/ids like ABBB1324....1234 and ABBB1234....1234 will be the same.
Binding these key-based ids to some kind of username of username@example.org sorta solves problem but makes that identity dependent on existence of example.com thingy, so making it centralized one way or another.
What you can suggest as decentralized identity solution?
So far, nothing better than GnuNet approach of GNS with their zones and "pet names" I can imagine.
bonfire.cafe
A space for Bonfire maintainers and contributors to communicate
Automatic federation enabled