Live data from Hacker News

Google Domains blocking all Gitbook URLS: post-mortem

blog.gitbook.com

91–100 of 189 posts

Re: Google Domains blocking all Gitbook URLS: post-mortem

#91
post #61
post #60

If you were hosting phishing sites then I'm glad they did this. You should have better controls.

According to the postmortem they had removed the site in question a week back. Google was acting on a week old data. Besides, any user-content serving platform will have to deal with malicious users. It is not a perfect process, especially against bot traffic. Shutting down the whole domain was very heavy handed.

I'll say it was. I can't believe they shut them down for content that had been removed over a week prior.

I realize some things take time, but the onus is on them to do a final verification before flipping the switch to shut down an entire business(!)

Google is "saving money" on support costs while simultaneously destroying their brand image (at least among the tech crowd). It will be near impossible for them to re-earn that goodwill. It's such ridiculously short sighted thinking.

I'm moving off of G-Suite this week. This is the final straw.

Re: Google Domains blocking all Gitbook URLS: post-mortem

#92
post #86

Earlier quoted context omitted.

ahh yes, the more ethical choice to move to well known hosters of DDoS protection for white supremacist sites and literal nazis. Why not move to a company that is just a domain registrar.

Why not stick to the topic at hand, rather than trying to hijack the discussion?

What makes you think that overall ethical behavior of a domain registrar is not relevant to the topic at hand?

Re: Google Domains blocking all Gitbook URLS: post-mortem

#93

Earlier quoted context omitted.

In the postmortem it states that they are moving to Cloudflare

ahh yes, the more ethical choice to move to well known hosters of DDoS protection for white supremacist sites and literal nazis. Why not move to a company that is just a domain registrar.

I'm pretty sure anyone cause cloudflare's DDoS protection. It's not limited to a particular political persuasion.

Re: Google Domains blocking all Gitbook URLS: post-mortem

#95

GitBook CTO here: Our production domains (gitbook.com and gitbook.io) have been blocked and locked by our registrar (Google Domains). None of our infrastructure is impacted, all user content and databases are safe; our domains simply blocked by a heavy handed policy. As mentioned on Twitter, we are all hands working with Google to fix this issues ASAP. We'll then share an in-depth post-mortem https://twitter.com/GitB…

As a former domain registrar, I would get the authcode, unlock the domains, and transfer them away as soon as possible. It's been a while since I read the RAA ( https://www.icann.org/resources/pages/approved-with-specs-20... ), but it's rather extraordinary to put a domain on clientHold, which is what I assume they did to you, outside of non-payment or some kind of legal dispute.

Google is the registry of some novelty TLDs as well, and you are pretty much bound to dance the way Google wants with those TLDs.

Re: Google Domains blocking all Gitbook URLS: post-mortem

#96

Just out of curiosity- when Google is infamous for hard-to-reach human support, what in the Internet would make anyone interested to register their domain with them? Do they provide some sort of security or insurance that I am unaware of? All the popular dedicated domain registrars I have used so far have excellent human support. Godaddy, namecheap, namesilo to name a few. I don't know if big companies or corporate u…

In terms of being able to open a ticket and get a response from a real human, for .ca domains the registrar canspace is quite responsive.

Re: Google Domains blocking all Gitbook URLS: post-mortem

#97
post #60

If you were hosting phishing sites then I'm glad they did this. You should have better controls.

There is spam on Facebook, there is spam on Reddit, there is spam on Twitter, there is spam on Hacker News. Proactive spam control is not a solved problem anywhere. Banning a website over it is absurd.

Nuking a domain with no warning for any reason is nuts. They started to shut it down before the email notification.

And any time support or PR is droning on about "muh policies" you know there are problems.

Re: Google Domains blocking all Gitbook URLS: post-mortem

#98
post #15

Earlier quoted context omitted.

Do you have examples?

Apart from the most obvious examples, I would also consider Cloudflare's new registry service. It's cheap, at-cost, and they support a lot of the new TLDs like .io which is also a lot cheaper.

What makes me uneasy about Cloudflare's registrar service is they force the use of Cloudflare's nameservers unless you have an "Enterprise" plan (paying a monthly fee for what amounts for some registry EPP calls?!) and given how they sell at cost I can't imagine the customer support in case of similar issues to this being good.

Re: Google Domains blocking all Gitbook URLS: post-mortem

#100
I don't think it should be registrar's duty to shut domains down.

Gitbook appears to use CloudFlare to host DNS, and likely to use their CDN/proxy, which makes them the actual "host" of the content. If there is any phishing, they should be the ones responsible.

The post says even their email was down. I'm deciding to not use Google Domains anymore.

Post reply on HN