C--NO--->D{check whether <br> tor returns 4xx or 5xx <br>error codes}--YES----->F(Tor Block Error)
C--NO--->D{check whether <br> tor returns 4xx or 5xx <br>error codes}--YES----->F(Tor Block Error)
E4--No---->E[/Additional Tests <br> DOM checks/]
E4--No---->E[/Additional Tests <br> DOM checks/]
E-->E1[DOM Checks <br> Percentage of differnce in DOM nodes]
E-->E1[DOM Checks <br> Percentage of differnce in DOM nodes]
E-.->E2[Consensus Module (Lite)]
E-.->E2[Consensus Module Lite]
E------>E3[Captcha Check] %% This will use the fact of the request path containing captcha in the url itself
E------>E3[Captcha Check] %% This will use the fact of the request path containing captcha in the url itself
E4{If the <br> Redirected website <br>returns error}--yes------->F
E4{If the <br> Redirected website <br>returns error}--yes------->F
E1-->G{if <br> score >0}
E1-->G{if <br> score >0}
...
@@ -135,6 +136,7 @@ style NT stroke-width:3px,fill:#FFFF00
...
@@ -135,6 +136,7 @@ style NT stroke-width:3px,fill:#FFFF00
```
```
+ Use of dashed lines and boxes show the things that haven't been implemented as of now.
+ Use of dashed lines and boxes show the things that haven't been implemented as of now.
+ As of now K has been set to 150 (Experimental Analysis)
+ As of now K has been set to 150 (Experimental Analysis)
+ The Captcha Checking Module has been proposed recently, which enables the use of "captcha" in the requests path from the responses we get while we load a website.
+ The Captcha Checking Module has been proposed recently, which enables the use of "captcha" in the requests path from the responses we get while we load a website.
...
@@ -143,8 +145,9 @@ style NT stroke-width:3px,fill:#FFFF00
...
@@ -143,8 +145,9 @@ style NT stroke-width:3px,fill:#FFFF00
For more details one you could look into the [Experimental code](https://raw.githubusercontent.com/Hackhard/Fetcher/main/status%20code/test_run4/tr.py) and it's [output](https://raw.githubusercontent.com/Hackhard/Fetcher/main/status%20code/test_run4/tr_bash_output) to gain an even more insight.
For more details one you could look into the [Experimental code](https://raw.githubusercontent.com/Hackhard/Fetcher/main/status%20code/test_run4/tr.py) and it's [output](https://raw.githubusercontent.com/Hackhard/Fetcher/main/status%20code/test_run4/tr_bash_output) to gain an even more insight.
This is the tabular form of the logic for the current version of `Consensus Module` that I would follow, that would be called lite because it's using proxies + non-tor Dom values to check with the tor values, providing a better statistical result when the tor isn't blocked fully (status code error) and also will be using `proxies` rather than `Vpn`, as they are easier to integrate and a simple Google search can give us a list of many proxies according to different regions which are updated too.
This is the tabular form of the logic for the current version of `Consensus Module` that I would follow, that would be called lite because it's using proxies + non-tor Dom values to check with the tor values, providing a better statistical result when the tor isn't blocked fully (status code error) and also will be using `proxies` rather than `Vpn`, as they are easier to integrate and a simple Google search can give us a list of many proxies according to different regions which are updated too.