Quote from: khal on May 28, 2012, 02:04:16 PM

If you want a feature to add existing email addresses and to ckeck if someone really owns it, you insert control and you want someone else to control a registered alias. This is not possible in namecoin because there is no central control (and it must be like that for security reasons !).

I see. No problem, it simply means that we have to make sure that we use the correct alias, just like we do with phone numbers and e-mail addresses.

Quote from: khal on May 28, 2012, 02:04:16 PM

What you can do is :
- adding alias with .bit domains, for example : khal@dot-bit.bit or khal@tor.bit
- adding alias with a namecoin mark : khal25@namecoin, manu44@namecoin, khal25@alia
- adding alias without domains : khal25, manu44

How about #Khal#, #Gavin.Andresen#, or #Bitinvestor# as pattern for the aliases? It would be easily recognized as a payment address and it can't be confused with an e-mail address.

Quote from: khal on May 28, 2012, 02:04:16 PM

Quote from: Bitinvestor on May 28, 2012, 11:39:26 AM

* Make it independent of any coin (except Namecoin, obviously). Leave it up to the user to decide which coins to use and provide a secure data structure that any coin (existing or yet to be invented) can query to associate an e-mail address with a wallet address. While this feature isn't implemented by other coins it should still be possible to query Namecoin manually to list all the addresses for gavin@acm.org so that the right one can be copied and pasted into the client.

This is the case.

Excellent! So what else do we need to make this work?