- cross-posted to:
- devops
- cross-posted to:
- devops
Also, interesting comment I found on HackerNews (HN):
This post was definitely demoted by HN. It stayed in the first position for less than 5 minutes and, as it quickly gathered upvotes, it jumped straight into 24th and quickly fell off the first page as it got 200 or so more points in less than an hour.
I’m 80% confident HN tried to hide this link. It’s the fastest downhill I’ve noticed on here, and I’ve been lurking and commenting for longer than 10 years.
The irony here is that the article author confirms that they break TOS of CF and he still has a Pikachu face. Reddit discussion is pretty positive that CF is right in their decision and that new provider will shut them down at some time as well.
even if they were breaking tos (and i don’t think it sounds quite so cut and dry), shouldn’t the response be to notify them and allow them to fix it, or just terminate the account? demanding a ton of money to make the problem seems a skeevy way of handling it on cloudflare’s part.
They had two weeks to fix, instead they stood their ground and argued.
They very well knew that they were costing a lot more than the $250 they were paying and couldn’t get a deal anywhere else