71–80 of 329 posts
Earlier quoted context omitted.
[deleted]
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.
Earlier quoted context omitted.
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.
[deleted]
(People don't think about incentives either.)
Earlier quoted context omitted.
Not a big surprise given they think HN threads are an acceptable form of customer support for paying customers.
[deleted]
Maybe they booted you because your business model is to use Cloudflare to repeatedly and aggressively scrape data from cryptocurrency exchanges and then resell it for hundreds of dollars a month. Sounds like an abuse of their terms of service to me.
Literally just sent an email to my devops guys to move off cloudflare asap. This cavalier lack of respect is a diservice and insult to all the people who rely on my product for their livelihood.
At this point @jgrahamc has the worst of it - people show up here time after time hoping they can make enough of a stink to get him involved.
Earlier quoted context omitted.
Actually, my mistake... it was almost 3 weeks ago. https://news.ycombinator.com/item?id=34383720 https://web.archive.org/web/20230114202232/https://news.ycom...
Ah damn, all it says is "I was advised to remove this post" and what was there before is not in archive.is
How are you using the workers? Is the JSON cached? Where do you get the JSON?
I'm using Workers as basically API gateway/smart load balancer to backend services that handle actual load (resource intensive data filtering). Most of the responses are not cached on Cloudflare level. Thing is that I was using Workers for about 4 years already with not issue at at all, I'm aware that I use lots of requests and bandwidth but I just wish I was contacted about mandatory upgrade before effectively turni…
I’m using cloudflare pages with workers doing the same as you on a much smaller scale. The workers reverse proxy a rest api under the same host so I don’t need to worry about CORS, take the country HTTP header provided by Cloudflare then route the request to backend servers in the nearest AWS region and also cache any responses with cache control headers utilising Cloudflare’s Edge caching. It works great and gives a fast user experience regardless of where you are in the world.
I was going to implement rate limiting backed by durable objects to protect my backends.
It seems exactly the usecase and ideal usage of workers! Now seeing this, it has me rethinking using/investing in cloudflare if they can decide if they like how you use workers or not and kick you off. It shouldn’t matter what output the worker generates as long as it conforms to https://developers.cloudflare.com/workers/platform/limits/