I would really like you to clarify your intentions on serving non-HTML content.
I say this slightly nervously as a Cloudflare customer who serves some amount of binary data. One message is "it's ok if you're on a paid plan". Another is "it's not ok at any time". My suspicion is that "it's ok unless we notice you".
If you could come up with consistent understandable messaging that would help a lot. I don't mind paying (stay competitive against AWS and Hetzner and that's all I need) but the uncertainty is not good.
I really curious about how this unfolds, I was planning to migrate from `AWS Lambda` to `Cloudflare Workers` as a paying customer. I'm basicaly an API with lots of JSON.
Why Cloudflare cancel paying Workers customers? Makes no sense to me.
> No more egress charges. You shouldn’t have to pay to access your data. Pay no egress charges for data accessed from R2. Our affordable and consistent pricing means no more surprise bills.
Whereas I think the non-HTML traffic terms still apply to R2. Or do they?
The supplemental terms about the developer platform apply to R2 (https://www.cloudflare.com/supplemental-terms/#cloudflare-de...). Same goes for Workers itself (the Cache api within Workers is also covered under these vs the non-HTML content restriction applies to the normal CDN path).
Posts like this make me so angry. Its unacceptable that _paying customers_ need to rely on the lottery of going viral of HN/Twitter to shame companies into providing legitimate customer support!
A moment of silence for the 100s of people who've made posts similar to this but not made it to the front page, and thus had their grievances ignored...
Friendly advice, stop digging and step away from this thread/talk to your PR team. You're not helping yourself or Cloudflare by responding in this way.
It's pretty amazing to me that even after seeing a response from a real human being, people continue to dog pile.
To those continuing to foam at the mouth: what would be the ideal outcome? Cloudflare closing up shop entirely after this? The whole "this shouldn't have happened in the first place" mentality is completely unproductive.
>To those continuing to foam at the mouth: what would be the ideal outcome?
Cloudflare changing their TOS from
>Cloudflare may, with or without notice to you and without liability of any kind, temporarily limit your storage and/or the number of requests you can make or receive using the Developer Platform for any reason (in its sole reasonable discretion), including without limitation
to something that does not allow them to do so on a whim, or with requiring upfront notice.
Wow this is the worst take about customer service I have ever seen by a company. You cause huge issues for business with the touch of a button, and when they require help and don’t think the cause was acceptable behavior, they’re whining? Just wow.
I've removed the word "whining" but to be clear I was not talking about the person who posted on HN that they had a problem. I immediately jumped on their problem when I saw it and I've ended up spending almost all morning on it. I took the long threads personally and should not have done.
10% globally and 30% of US traffic. Probably. Google has more aggregate users and traffic, and they're also world renowned for not having any customer service short of "blowing up on twitter" or getting lucky here on HN.
jgrahamc responded directly to the point. Replying before it made the front page means this post didn't need to go viral or win the front page lottery in order to get support, making it a counterexample to the GP.
I'm always unsure how to read this.
One one hand it is nice that there is someone in the company willing to do work which is in the interest of the customer (of sorts).
But on the other hand it shows the company is willing to let quality, support, customer care, service and everything else decline but when it comes to public image is prepared to do everything within their power, even (yuck) their job in order for damage control.
Now that I'm writing this I know exactly how to read comments like "now that it's in the public eye, we'll do something - maybe".
People like jgrahamc are the people who care and are embarrassed their company provides such unreliable service. I just wish the people in charge of these companies felt the same responsibility and embarrassment.
I did not know that. That certainly changes things.
I don't know how many people work at Cloudflare, but I'd imagine it's more efficient to have a working customer support system than to have the CTO personally handle every problem.
I agree about the efficiency and wouldn't expect anyone to know that on a thread, off of a handle alone. However, I see it in a more positive light- based on John's other comments in the thread, he's made the time to stay active in communities like this one even as the CTO and followed up with folks internally to understand how an oversight like this could've happened.
I think people see a lot of posts like "I tried to get help with my problem but received no response" and don't think about the selection bias involved. (Of course, if someone gets helped by customer service with no issues, that doesn't tend to come to Hacker News' attention.)
But from their perspective it does feel like these sorts of posts are the only way to get attention on a problem.
