Sorry, but the title is click bait. Can people just write "Our IO domain Resolution Failed, A Lesson Learned"? In the "What Really Went Wrong" section, the aut

Sorry, but the title is click bait. Can people just write "Our IO domain Resolution Failed, A Lesson Learned"? In the "What Really Went Wrong" section, the author wrote: > it does not take a lot of research to find out that the .io TLD team made several mistakes and went on to cite two incidents, which are not exclusive to .IO domain. So let's not blame ".io domain team" and only happen to .IO domain, try to convince me (at least the way I read it based on the title) that using .io domain is a bad idea. I should stop using .com then. For me, I was looking for a "so we are going to switch away from .io domain in the next year or so" at the end of the post, because .io is not good according to the author. The plan instead is just add a backup domain, so it looks like the author is eating his/her own words, even though the critical stuff are going to run over .com. So let's just switch everything over, what's the big deal for your user-facing website not over .com? Do people really think a big deal now about .io vs .com when you have established a business? Anyway, I do appreciate when a postmortem is available because I can learn something new, but I do hope we write postmortem with an objective tone. So no, if there is a downvote button on HN for the submission, I would downvote.