Hacker News Reader

Because their regex is crap and if you have @twitterHandle or something with a legitimate "@" you just see the obfuscated version.

It's laughably adorable to think it's actually solving a problem or helping in any way, the 'bad actors' it's trying to prevent probably have a work around anyway.

View on HN

> It's laughably adorable to think it's actually solving a problem or helping in any way, the 'bad actors' it's trying to prevent probably have a work around anyway.

They do—changing your user agent is trivial.

Why would I want to send an incorrect user agent? There's no point having one if it's just going to lie anyway.

I agree. I wish browsers would just stop sending a user agent string entirely. I don't think that I've sent an honest one in over a decade.

https://news.ycombinator.com/item?id=22044057

Most of these protections are easy to work around, and people do just that, but that isn't the product cloudflare is selling.

To the target market, who have a spam issue, cloudflares protection sounds great, and by the time they've set it up, they won't switch CDN's just because it isn't effective enough.

Reply on news.ycombinator.com