... | ... | @@ -12,7 +12,7 @@ The **CAPTCHA Monitoring** project aims to track how often CDN (for ex. Cloudfla |
|
|
### Background
|
|
|
I have been personally annoyed by receiving CAPTCHAs while using Tor, and going through the Tor Project's issue tickets showed that I wasn't alone in this, especially ticket [#33010](https://gitlab.torproject.org/tpo/metrics/ideas/-/issues/33010). After years of complaints from users and research papers published on the topic, it was clear that a public database & data collection tool was needed to back up the claims and let CDN companies take action. So, the CAPTCHA Monitor was born. Since this project didn't exist before, I designed the whole system from scratch and built it during GSoC. The designs of other similar tools, such as [OONI](https://ooni.org/), [Tor Metrics](https://metrics.torproject.org/), and [ExitMap](https://github.com/NullHypothesis/exitmap/), were influential in the decisions I made.
|
|
|
|
|
|
Next, I compiled a list of related tickets & comments from Tor Project's bug tracking system (see [metrics to track section](home#metrics-to-track)) to understand which metrics are valuable to collect and what the community wants to learn. These findings helped me to further tune my design.
|
|
|
Next, I compiled a list of related tickets & comments from Tor Project's bug tracking system (see [metrics to track section](home#metrics-to-track)) to understand which metrics are valuable to collect and what the community wants to learn. These findings helped me to further tune my design and build a [roadmap](home#roadmap).
|
|
|
|
|
|
Here is a high-level overview of the design I implemented:
|
|
|
```mermaid
|
... | ... | @@ -66,15 +66,11 @@ The other repository is [CAPTCHA Monitor Web repository](https://gitlab.torproje |
|
|
|
|
|
|
|
|
### CAPTCHA Monitor API
|
|
|
The API is responsible for serving the collected data
|
|
|
|
|
|
The code, issues, and documentation related to the CAPTCHA Monitor API can be found in [this repository](https://gitlab.torproject.org/woswos/CAPTCHA-Monitor-API).
|
|
|
The API is responsible for serving the collected data over a RESTful API. It both feeds the dashboard and provides open access to the collected data. The code, issues, and documentation related to the CAPTCHA Monitor API can be found in [this repository](https://gitlab.torproject.org/woswos/CAPTCHA-Monitor-API). A live instance of the API can be accessed at [api.captcha.wtf](https://api.captcha.wtf/) or [capi4ljiudrzsnnlcnjror4ziizzbxevyngy5sbtxaato6v6gv5ck3qd.onion](http://capi4ljiudrzsnnlcnjror4ziizzbxevyngy5sbtxaato6v6gv5ck3qd.onion/)
|
|
|
|
|
|
|
|
|
### CAPTCHA Monitor Dashboard
|
|
|
https://gitlab.torproject.org/woswos/CAPTCHA-Monitor-Dashboard
|
|
|
|
|
|
The code, issues, and documentation related to the CAPTCHA Monitor Dashboard can be found in [this repository](https://gitlab.torproject.org/woswos/CAPTCHA-Monitor-Dashboard).
|
|
|
The dashboard is used for visualizing the analyzed data and for detecting anomalies in the trends. The code, issues, and documentation related to the CAPTCHA Monitor Dashboard can be found in [this repository](https://gitlab.torproject.org/woswos/CAPTCHA-Monitor-Dashboard). A live instance of the dashboard can be accessed at [dashboard.captcha.wtf](https://dashboard.captcha.wtf) or [captchaufjq5m2i73up537pldaxnbp6rzcbdrzc7y5rlwtx3mwigznad.onion](http://captchaufjq5m2i73up537pldaxnbp6rzcbdrzc7y5rlwtx3mwigznad.onion/)
|
|
|
|
|
|
## Challenges
|
|
|
|
... | ... | |