From 111f7606e6b31c199762e16288534ddb5ea4c354 Mon Sep 17 00:00:00 2001 From: Frans Veldman Date: Fri, 12 Jun 2026 12:12:25 +0000 Subject: [PATCH] Fixed picture display --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index ed0629d..682db57 100644 --- a/README.md +++ b/README.md @@ -8,8 +8,6 @@ My SearxNG instance on [searx.thefloatinglab.world](https://searx.thefloatinglab Despite the deployment of botlists, limiters, and manually blocking the most obvious bots, it still remained an endless battle. Most of the time my instance was useless. So either I had to give up on this project, or find a way to block the bots and let the genuine users through. A captcha system might not be popular, but on the other hand, a useless site is well, pretty useless. By combining the captcha system with a cookie, only once in 90 days the user has to solve the captcha. A small price to pay for access to a wonderfull instance! -![picture](https://git.thefloatinglab.world/TheFloatingLab/SearxNG-Captcha/raw/branch/main/captcha.jpeg?raw=1) - # Features - No modification of the SearxNG code is necessary, the captcha system runs entirely within Nginx. - The captcha, once solved, stays valid for 90 days. @@ -21,6 +19,8 @@ By combining the captcha system with a cookie, only once in 90 days the user has - Everything is script based, no compilation is necessary. - In an emergency, all existing cookies can be invalidated at once. +![picture](https://git.thefloatinglab.world/TheFloatingLab/SearxNG-Captcha/raw/branch/main/captcha.jpg?raw=1) + # Installation This guide is not a complete walk through. I show you my code and how I have done it. Some tweaking might be necessary, and the locations of files on your system might be different than on mine. I have not made an attempt to add subdirectories to this git, so you have to download the files and place them manually in the correct locations.