You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure whether this is an intentional hack to circumvent the browser limitations around handling custom TLDs (if so, ingenious really!) but .bt is the ccTLD of Bhutan.
We can use .bittorrent as well, but it would require users to type the protocol http(s):// in address bar, as opposed to "native" handling of .bt. Perhaps this is not as big of an issue given that users are not likely to type our domains by hand.
Lastly, if you know someone in Bhutan, we might snatch "link.bt". :)
The text was updated successfully, but these errors were encountered:
I honestly thought that bt didn't exist. It's only been a working TLD because it's short, and I wanted to avoid btlink.io or anything like that. I will have to test if using something entirely made up still works with the browsers, working around certificate handling has been very interesting.
Any suggestions for alternatives? btlink.io does seem like the best option for now, unless I come up with a fancier name for this project.
I am not sure whether this is an intentional hack to circumvent the browser limitations around handling custom TLDs (if so, ingenious really!) but .bt is the ccTLD of Bhutan.
We can use
.bittorrent
as well, but it would require users to type the protocolhttp(s)://
in address bar, as opposed to "native" handling of .bt. Perhaps this is not as big of an issue given that users are not likely to type our domains by hand.Lastly, if you know someone in Bhutan, we might snatch "link.bt". :)
The text was updated successfully, but these errors were encountered: