Other uses for the hostname

[hackerfactor]

VIDA uses a hostname's TXT field in a DNS record for storing the public key. However, how else can the hostname be used?

For example:
The hostname could store a unique user identifier.

• vida.hackerfactor.com is for a site-specific public key.
• neal.vida.hackerfactor.com could store a unique public key for user "neal"
• 1111222233334444.5555666677778888.facebook.com could hold the anonymized account information for a particular user. (Facebook uses really long numbers for ids, and they like to include at least one long number as a random seed to deter brute-force iterations.)

The VIDA DNS entry only needs a TXT field, not a network address (A or AAAA). But what if they also had a network address? For example, what if it had a running web server?

• For a site-specific public key, it might return a web page about the service and where to get more information.
• For an account-specific public key, it might return information about the account! For example:
  • If the account is public, then "neal.vida.hackerfactor.com" might return information about the account: name, registration date, contact information, links to known social networks, etc.
  • If the account is private, then maybe it only returns information about the registration date. (Attorneys and law enforcement could be told where to send the subpoena or warrant if it's a legal issue.)
  • A private account that requires a login to access? (E.g., LinkedIn or Instagram) If you're not logged in, then you might see minimal information. If you're logged in as a known friend, then you might see more information.

Thoughts?