News for hackers. Stuff that matters.
Re:The Trouble with CloudFlare by unexistance on Friday April 01, 2016 @12:19PM (#11405978)
The somewhat-faster way to reduce this annoyance (I've been hit by this) is to 'block'/captcha the offending IPs for a time (depends on whatever metrics CloudFlare think is best) then unblock it.

At least this will reduce legitimate user's annoyance, instead of being blocked indefinitely

My own experience: Tried accessing wikialpha from work LAN, 'blocked' by endless captcha (for a few months already) and opening the said wiki from home network, all is perfectly fine...

well at least now I know why, still does NOT makes it OK from end-users perpective

Re:The Trouble with CloudFlare by Kalium on Friday April 01, 2016 @04:13PM (#11408178)
Given how much of TOR traffic is malicious (94%), what you propose would get all TOR traffic always considered malicious.
Re:The Trouble with CloudFlare by _Codemonkeyism on Monday April 04, 2016 @03:54AM (#11420117)
Care to share a source for "TOR traffic is malicious (94%)"?

What does malicious percentage of traffic in this case mean? Malicious sessions? IPs used? Packets? Users?

Re:The Trouble with CloudFlare by Kalium on Monday April 04, 2016 @02:11PM (#11423990)
The number is in the CloudFlare blog post that started this.

> Based on data across the CloudFlare network, 94% of requests that we see across the Tor network are per se malicious. That doesn’t mean they are visiting controversial content, but instead that they are automated requests designed to harm our customers.