It’s an interesting proposal. Right now, as
@Vitor Pamplona pointed out, the only universal identifiers are pubkeys and event ids. Which of course are not human readable.
So the question is: can we make a human readable name like Fabio that is also in some sense “universal”? Primal does this; you subscribe to their services and you can reserve your username. But of course that’s a centralized entity, so the question is whether you can do it in a manner that does not rely on a centralized entity.
Your method proposes a naming system that does not rely on any single entity. It might be too strong to say it’s “centralized” around the system itself, but we would have to ask whether the system itself would be universally adopted. In the real world, there will never be one and only one Fabio; it may be unique within some small domain, but not universally unique. That’s the price of making it human readable. Your system is first come first served; will people accept that as opposed to, say, a system that selects the “real” Fabio to be the one with the most proof of work? There could be more than one decentralized naming system. But with your system, I would have the comfort of knowing my name won’t be taken from me.
Perhaps a use case could be: suppose I want you to zap me some sats, I can’t remember my npub, I don’t want to use a centralized naming system like primal, so I tell you to zap “Fabio” using your system as the naming system.
When I put on my product hat it’s hard for me to see this gaining wide utility as is, but it is worthy of thought.
Thoughts?
@ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ
@Jay