... | ... | @@ -10,7 +10,9 @@ The codebase consists of three separate repository which are dedicated to the th |
|
|
You also find the documentation in [this Read the Docs page](https://captcha-monitor.readthedocs.io).
|
|
|
|
|
|
## Dataset
|
|
|
The data collected so far can be found in [this dashboard](http://dashboard.captcha.wtf/). The data can be downloaded through the API.
|
|
|
The data collected so far can be found in this dashboard: [dashboard.captcha.wtf](https://dashboard.captcha.wtf) or [5yalu72ryu4xu457kmcze5kxb4on6xh2vkom35jnu4s3respg7hsguqd.onion](http://5yalu72ryu4xu457kmcze5kxb4on6xh2vkom35jnu4s3respg7hsguqd.onion)
|
|
|
|
|
|
The data can be downloaded through the API.
|
|
|
|
|
|
## Detailed description
|
|
|
By design, Cloudflare is developed to alter the traffic between the web servers and internet users. Cloudflare modifies the internet traffic to protect the Cloudflare fronted web servers from various attacks from users with malicious intentions. Even though this seems like a practice with good faith on the surface to protect servers, it harms millions of users more than doing good. Cloudflare makes decisions to block or not to block users based on multiple factors such as visitor's IP address, resources requested, request payload and frequency, and customer-defined firewall rules [Source](https://web.archive.org/web/20200328165212/https://support.cloudflare.com/hc/en-us/articles/205177068-How-does-Cloudflare-work). They don't share the specifics of their decision-making mechanism since it keeps changing over time, and it is not open-source. However, this doesn't stop us from experimenting with the algorithm and understanding how it decides to block/not block users.
|
... | ... | |