Universal Acceptance Issues with .TUBE, ASCII and IDN Domains
circleid.com
circleid.com
People make typo's often and software can't always be sure if it should linkify something _just_ because it contains a dot. The definite way to be sure is people add the scheme `https://` or linkify the text using an app-specific way. Outside of that, every app has to make its own usability decision and some apps will correctly decide to ignore some unpopular TLDs for the sake of reducing annoyance.
Prepending https:// has issues. One, it's a matter of telling the general public what to do. You might as well blow against the wind. Two, this applies to IDNs, which are generally used by people with different keyboard layouts. If you have a 'ت' key on your keyboard, you'll have to switch keyboard layouts twice in order to input 'h'. Telling people to do that really is blowing against the wind.
> We are researching whether Microsoft has similar issues, but all of these efforts are draining our corporate executive time and resources, to do a job that should have been done by ICANN years ago
Are we supposed to care about these poor executives, working hard to write angry emails to various private organizations trying to get their FOTM TLDs added to some regex? I'd tell them to go pound sand!