This page contains outdated docs and as discussed will be deleted...
This page is created to give people the in-depth idea as to why some of the steps are taken into consideration and how things got updated and looks in the recent version of the Project.
## Updates (05/30/2021):
I've updated the high level flowchart shown below and it can be found in the [Updated Logic Section](https://gitlab.torproject.org/woswos/CAPTCHA-Monitor/-/wikis/GSoC-2021#updated-logic)
##### HIGH LEVEL FLOW-CHART: (**Now Obsolete**) #####
I have already mentioned in the [Roadmaps](https://gitlab.torproject.org/woswos/CAPTCHA-Monitor/-/wikis/GSoC-2021/#nearby-goals-and-roadmap) the steps for `Consensus Lite` so would talk more about the approach I took to reach it.
When The `DOM Analysis` of Tor and Non-Tor fails, I'll proceed with the `VPN/Proxy` method for the particular `Continen`t or if `Location`, available to get a similar result of what a general DOM for a region should be like. Of-course, since we are taking the idea of consensus, we'll try mapping it to all `VPNs/Proxies` of that particular region to get an idea.
Cases mentioned below might still arise:
+ What would happen if we have just one `VPN/Proxy server` available for that location and it matches with Tor DOM and both returns `partial errors` as already our status check would filter the status blocks? Though there might not be many possibilities but still for the worst-case I think it should be helpful to think of an approach.
One possible solution to curtail above is to check the score of the `VPN server` we are testing: https://antcpt.com/score_detector/ and give weight-age accordingly.
