Live data from Hacker News

Show HN: Use any text as a domain name

github.com

21–30 of 147 posts

Re: Show HN: Use any text as a domain name

#21
One downside of this is that you're using a secure one-way hashing function. This means that if for some reason you have the hashed url you can't get the clean one back.

You could use something something like base64 instead.. might work better but it would remove the ability to use files as domain names.

Re: Show HN: Use any text as a domain name

#22
post #3

this is a bad idea that will never work /s

Why do you think that? Please elaborate! HackerNews isn't supposed to be about trolling. Personally, I like the idea and i'm going to use it. However, it relies on people downloading the extension. If there are enough people using it (which is definitely possible) then it would be successful.

/s indicates sarcasm

Re: Show HN: Use any text as a domain name

#23
post #5

Reminds me of "RealNames". Dot-com era company. $130 million in funding. http://en.wikipedia.org/wiki/RealNames RealNames was a company founded in 1997 by Keith Teare. Its goal was to create a multilingual keyword-based naming system for the Internet that would translate keywords typed into the address bar of Microsoft's Internet Explorer web browser to Uniform Resource Identifiers, based on the existing Domain Name…

Also, AOL Keywords.

Re: Show HN: Use any text as a domain name

#26
post #23
post #5

Reminds me of "RealNames". Dot-com era company. $130 million in funding. http://en.wikipedia.org/wiki/RealNames RealNames was a company founded in 1997 by Keith Teare. Its goal was to create a multilingual keyword-based naming system for the Internet that would translate keywords typed into the address bar of Microsoft's Internet Explorer web browser to Uniform Resource Identifiers, based on the existing Domain Name…

Also, AOL Keywords.

And new.net, though I think that was basically malware. There were a lot of "DNS Alternatives" in the early 2000s.

Re: Show HN: Use any text as a domain name

#27
Neat idea! One quibble: since the essence is specifying a domain-name in a new way, it'd be good if the 'escaping' convention didnt' clobber/assume a single protocol/scheme. As it stands, it's not clear how this would be used for other schemes, even 'https'.

Perhaps allow 'scheme#' (where naked '#' implies 'http#'), or move the convention entirely to the domain-name area rather than scheme area. ('#food in chicago' -> 'http://#food in chicago' -> 'http://f02970848a63988965aa40cd368ffcf9046209ca.com')

Post reply on HN