Skip to content

Commit

Permalink
Add blog post about .org
Browse files Browse the repository at this point in the history
  • Loading branch information
iHiD committed Aug 29, 2021
1 parent 2d7294b commit ea5b739
Show file tree
Hide file tree
Showing 2 changed files with 34 additions and 0 deletions.
9 changes: 9 additions & 0 deletions config.json
Expand Up @@ -209,6 +209,15 @@
"author_handle": "iHiD",
"marketing_copy": "Our community is hard at work building Exercism v3, which means mentoring is quite a bit slower than normal. Read to learn more",
"youtube_id": "XiV_vYn1Ea8"
},
{
"uuid": "3aa1037d-ea5f-4346-9a07-fee4c09b6397",
"slug": "exercism-io-is-now-exercism-org",
"category": "updates",
"published_at": "2021-08-29 01:00",
"title": "Exercism has moved to exercism.org",
"author_handle": "iHiD",
"marketing_copy": "Exercism has a new home! With the launch of v3 we've moved from exercism.io to exercism.lol. Read on to learn more!"
}
]
}
25 changes: 25 additions & 0 deletions posts/exercism-io-is-now-exercism-org.md
@@ -0,0 +1,25 @@
# Exercism has moved to exercism.org

Exercism has a new home at exercism.org!

For the last 8 years Exercism has lived at exercism.io and we decided it was time for a change!

If you're interested, here are a few of the reasons we made the decision.

Primarily, we feel that the `.org` domain better represents what Exercism is.
Most startups begin with finding whatever domain is available, and `.io` was a nice fit as it's often associated with I/O, but as we've grown and evolved, and become a larger platform, we've felt for a while that it was time to change to a more "official" seeming domain.
We own `exercism.com`, `exercism.net`, and a few others, but we feel that `exercism.org` best represents our not-for-profit mission and gives the best first impression.
As we also look to raise donations from both our community and from organisations, we felt that the more professional `.org` also offers more trust, especially as our name can sometimes give a slightly jarring first impression…

Secondly, being on an `io` domain gives a little less safety than using one of the original TLDs.
Back in 2017 the [io authoritative nameservers were compromised](https://thehackerblog.com/the-io-error-taking-control-of-all-io-domains-with-a-targeted-registration/) using a pretty trivial method, and while mistakes happen and things were quickly rectified, this isn't the sort of thing that's going to happen to `.org` domains.
We've also had sporadic issues with DNS resolving, which people being unable to access the site.
We've never been able to track this exactly down, but our best understanding is that something occasionally goes wrong at the `.io` level, rather than the AWS level.

There's also some questions about the ongoing ownership of the `io` TLD, and the potential consequences of that, which derive from the origins of the `.io` TLD and who benefits from it.
If you're interested in reading more on that [this article](https://gigaom.com/2014/06/30/the-dark-side-of-io-how-the-u-k-is-making-web-domain-profits-from-a-shady-cold-war-land-deal/) outlines some of the information.

All pieced together, and moving to `.org` feels like the right step for us.
It's something we've been planning for a couple of years now, and felt that with the upheaval of launching v3, the time was right to do it.
If you hate all of these reasons, feel that we've betrayed our roots, have no principles, and have sold out, sorry for spoiling your day.
To everyone else, I hope you enjoy our new home!

0 comments on commit ea5b739

Please sign in to comment.