Not commenting on this particular case, but I know in smaller dev shops that time spent working on one feature is directly taken away from time spent on other things, and so if the new feature isn't useful to you, it has also taken fixing and dev time away from ones that might be. I also suspect that many people have seen the trajectory where apps get more and more features and don't focus on their core competency.

Again, I don't believe this is the case here, but it might generally explain the phenomena/misplaced snark.

Sort of, at least in fashion. This store https://www.bottegaveneta.com/en-ca/large-pillow-pouch-dark-... caused a lot of mocking for their multi-thousand dollar normal looking shirts for example

Don’t think it’s deserved in Cloudflare’s case though here.

Because when they are personally detected due to a false positive it is a poor experience.

I see a lot of sites (including those behind Cloudflare) being blocked when using Cloudfare's Warp VPN. 403s, captchas, etc.

It would be nice if Cloudflare could put abuse control measures on the front-side, and stop the abuse before allowing it to exit their VPN. E.g., if Cloudflare detects abuse with their existing anti-DDoS, anti-scraping, etc. measures, and the client is on Warp, instead of creating a poor experience for every other Warp user sharing that exit IP, just block/aggressively throttle the bad actor's traffic at the VPN terminator.

They have struggled with credential stuffing, captchas were the only way to stop our login pages from being bombarded at one time. They are getting better with it though but I would rather not lose a tool of last resort.