http://maverick.i2p/blog/mavewaf
Memory footprint in production: Component Memory Blog ~6.9 MB MaveWAF ~8.5 MB I2P ~18 MB Tor ~75 MB Total ~108.4 MB ntfy.sh-style webhooks for push notifications on defense mode, rate limit hits, and circuit kills. On Tor, most traffic is bots. MaveWAF forces connections to prove a human is there. If you can solve a noisy image without Selenium, you’re welcome. If you’re a script, get bent. Source on clearnet: https://git.mrmave.work/maverick/mavewaf On Tor:...