27 Jan 2026 17:14:43 Olafur Jens Sigurdsson <[email protected]>:
> On Tue, Jan 27, 2026 at 09:21:59AM +0100, Tom Szilagyi wrote:
>> On Sat, Jan 24, 2026 at 12:09:06PM +0000, requiem. wrote:
>>> This has come up on the list earlier and sadly no changes were made. The
>>> anti-scraping is too aggressive and there is no reason it HAS TO redirect
>>> to theannoyingsite. It does not annoy bots, only humans who accidentally
>>> get caught by it. I get "trolling botz lol" and fully agree with the need
>>> for self-defense but this is trolling the wrong targets.
>>>
>>> I would also like to ask once again in line with Strahinja's message to
>>> change the redirect to something else.
>>
>> Sorry if this has been suggested before (but I found no trace).
>>
>> I run an extremely obscure and insignificant personal gitweb instance
>> behind my residental connection. The LLM bots came for it regardless
>> and I tried out several different approaches (IP-based blocks among
>> other things) to regulate them. What proved the most effective was
>> implementing the simple trick described in this article:
>>
>> https://her.esy.fun/posts/0031-how-i-protect-my-forgejo-instance-from-ai-web-crawlers/index.html
>>
>> Basically, JS + cookie gate.
>
> And this breaks the web for those of us that like to use non javascript
> browsers like Dillo, w3m and the like.
>
> But that is the way it is I guess, time to move forward into the mud pit :-)
>
> Oli
Having continued access to cvsweb from the terminal via w3m etc would ve really
useful for those "i am stuck in the terminal because something broke"
scenarios. Would rather not habr a js challenge.
