3 ms·
So instead, he makes it google's problem. This is an even more unreasonable and irresponsible decision. If he doesn't feel his project has the manpower to handl
by Sanddancer 11y ago
So instead, he makes it google's problem. This is an even more unreasonable and irresponsible decision. If he doesn't feel his project has the manpower to handle support requests for default servers, then he shouldn't list any default servers.
- Merovius 11y agoLennart has stated very clearly, that if someone where to propose some other publicly available server, that he would be happy to put that down instead. Also note, that the reporter didn't write "don't use this, we can't handle the load", but "don't use this, weird stuff will happen to your server". But yes, I agree, Googles NTP servers should be removed as a default. But a vendor pool also isn't a solution apparently. Luckily, there are people actively working on a PR to simply have no default. So everyone should just calm down and give the issue a while to resolve itself, instead of venting here on HN.
- wang_li 11y agoThe reporting wrote, in his first paragraph: >Google doesn't provide timeX.google.com as a public service. That's the end of the conversation. How Google handles rare time events, whether it's reliable or scalable are all irrelevant.