Bitmessage addresses are difficult, or impossible to remember. This note proposes an address lookup system, based on the DNS infrastructure.
An Bitmessage address could be defined like this:
bm://example.com
Then in the Zonefile for example.com you would have:
example.com. IN TXT "v=bm-{addressProtocolVersionNumber} BM-{bitmessageAddress}"
If the user wants to send a message to example.com the client would do a DNS lookup
exmaple.com, recieve the TXT record and look for the v=bm in the start of the string,
knowing that a Bitmessage address will follow.
I love the spirit of this: giving a human-friendly name to a human-unfriendly address. But this just isn't secure. A site like Firstbits could at least use SSL and the x.509 system which is better than nothing. In this case, the address you would give someone would be something like bm://friendlyaddress.com/xqus
Then you would have to trust friendlyaddress.com to tell the truth, and also all of the x.509 root authorities to not get hacked or be malicious. So do we rely on trust or be completely insecure? We've just arrived back at Zooko's triangle.