Optional feature proposal: make EndGame transparent by default, enable queue + captcha under specific conditions. : EndGame | Torhoo darknet markets

Correct me if I'm wrong:

- EndGame 2 tools in 1, it is infinitely more than a captcha. The captcha and queue are only the visible part (from the user's point of view).

- You can use EndGame without load balancing, have only one front-end, and give the front-end URL directly to users.

- The queue and captcha are only useful in case of request spam (DoS attempt) to distribute the load on the fronts without it reaching the backend.

- The captcha does not make it impossible to use a bot if a cookie has been previously generated by hand.

- The absence of a captcha (and a queue) does not prevent a cookie from being blacklisted.

- Some sites are frequently (or constantly) DDoS, others are occasionally (or never).

For those other sites that don't have a DDOS problem, why not offer an option (which can be activated during setup via the config file, or any other way) to disable the queue and captcha and leave EVERYTHING else: rate limiter (per cookie and circuit), Fail2ban, Rkhunter, Chkrootkit and NAXSI.

There could be 3 modes configurable during setup:
- EndGame Full: Queue, Captcha + everything else (default)
- EndGame Adaptive: Queue and Captcha with automatic on/off under conditions (CPU load/requests spamming) + everything else
- EndGame Minimal: Queue and Captcha disabled (manual activation possible) + everything else.