I do like the delineation between official Github content and user-content, but there definitely other ways to go about the problem without buying into the latest TLD fad.
I do like the delineation between official Github content and user-content, but there definitely other ways to go about the problem without buying into the latest TLD fad.
Now, there is an issue with the Chagossians being forcibly removed from the islands, but should they ever resettle and gain sovereignty, it seems unlikely they'll continue to call themselves the British Indian Ocean Territory, necessitating a TLD change anyway (a la .su, .tp, and .an).
We also considered http://github.me and a few others, but thought this one worked well and was short without sounding like we were trying to make a mid-90's Personal Home Page Product™.
Now if we could only get Google to see .io as a "generic" TLD: https://iwantmyname.com/blog/2012/08/dear-google-please-add-...
> without sounding like we were trying to make a mid-90's Personal Home Page Product™
That's not a dig on PHP is it? :)
It's also easier to find a relatively short/applicable tld.
1. http://domaintyper.com/top-websites/most-popular-websites-wi...
2. https://news.ycombinator.com/item?id=4920233
3. http://answers.onstartups.com/questions/18209/whats-with-sta...
The trend will eventually be that, except for established historical domains (.co.uk, and a few dozen more), most TLDs won't signinfy anything. That's already happened with .ly, and is happening now with .io and .co.