3 ms·

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 t

by tcd 7y ago

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.

deleted 7y ago
[deleted]
vageli 7y ago
> 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.
- sp332 7y ago
  Why would I want to send an incorrect user agent? There's no point having one if it's just going to lie anyway.
  - JohnFen 7y ago
    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.
    - sp332 7y ago
      https://news.ycombinator.com/item?id=22044057 https://news.ycombinator.com/item?id=22044057
londons_explore 7y ago
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.