Hacker News Reader

Comment by lolinder | Hacker News Reader

That seems unlikely given that the vast majority of users have no clue what the underlying service provider is for the web services they're using, and those who do know are savvy enough to understand the difference between an AWS issue and a configuration issue.

View on HN

Imagine if Cloudflare went to IPV6 only. Yes, Cloudflare's customers should know what that means, but the end users that are using the service may not be and if the error in anyway says Cloudflare, then it gives Cloudflare a bad reputation.

While AWS is a bit (just a bit) more removed from the end user than Cloudflare, there is still the potential for it not being good PR.

Cloudflare couldn't dare of IPv6 only until a lot more of the internet supports IPv6. They could however offer a discount of some sort to customers that are IPv6 only. That includes proxy your IPv6 only site to IPv4 (actually they would probably not give a discount directly, but let you apply discounts you get from your ISP)

Cloudflare actually presents end users with an authentication page on a regular basis. AWS is strictly behind the scenes. The only time I've ever become aware that a site is using AWS is when reading their engineering blog or spelunking in the dev tools.

These infinite verification prompts are the reason I no longer consider Cloudflare as an option for business use and would not recommend it to anyone. I know that they are configurable by the admins but they give bad PR to Cloudflare. I am not sure what this company was thinking associating itself with such a terrible user experience.

Reply on news.ycombinator.com