3 ms·
I can say from experience that moving content to a different domain without breaking things for users can be atrociously difficult. So if you make a mistake in
by thayne 6y ago
I can say from experience that moving content to a different domain without breaking things for users can be atrociously difficult. So if you make a mistake in how you split domains in the beginning, it can be very expensive to rectify later. Can you imagine going to all your customers and saying "you know all those links you have to example.com? You're going to have to change all of them to point to example.org now."
They _should_ split their domains, and given this recent issue, it would make sense for them to prioritize that. But, well, easier said than done.
- mbreese 6y agoI imagine it will be painful to split their domains. But, I was surprised to see that wasn't mentioned in their post-mortem. Even if they didn't plan on doing it, I think that it would have made sense to mention. I imagine their main paying customers would start demanding this change though. They are probably using a custom domain, so whatever domain GitBook chooses to use should be irrelevant for them (in theory, but in practice, who knows...).