3 ms·

So, Canon realizes that half of the programs in the world (if not more) that autodetect urls aren't going to detect http://canon http://canon or anemailusername

So, Canon realizes that half of the programs in the world (if not more) that autodetect urls aren't going to detect http://canon http://canon or anemailusername@cannon as urls/emails, right?That limits what they can really do with this. I guess they could have other stuff redirect to http://canon http://canon, and urls for "subdomains", which are now normal domains, become nice and might catch some more url detectors. http://slr.canon http://slr.canon and the like. It's still a major problem.

jerf 17y ago
Of course, they own canon.com, and http://canon http://canon will generally redirect there. Then they set up their own nameserver to simply do things like redirect blah.blah.canon.com to blah.blah.canon. Then you find yourself asking what the point of all this is again because DNS is already hierarchical and once you own canon.com you already own an effectively-infinite series of subdomains, so Canon is spending $185,000 + ongoing maintenance so they can trim ".com" off and incur first-mover expenses as they encounter those problems you mention and that seems hardly worth it. But hey, who am I to argue?