Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Rich <rich@example.invalid>
Newsgroups: comp.misc
Subject: Re: bad bot behavior
Date: Wed, 19 Mar 2025 16:59:19 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 22
Message-ID: <vret57$197b5$1@dont-email.me>
References: <vrc2r4$2okrp$1@dont-email.me> <vrc8qm$2tkq5$1@dont-email.me> <20250318182006.00006ae3@dne3.net> <slrnvtlcpl.41d.${send-direct-email-to-news1021-at-jusme-dot-com-if@vm46.home.jusme.com>
Injection-Date: Wed, 19 Mar 2025 17:59:20 +0100 (CET)
Injection-Info: dont-email.me; posting-host="46d6655484631e2ac3d60d94ad3f8d5b";
	logging-data="1351013"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/IO1e3xoh9p+38ZTsqS59A"
User-Agent: tin/2.6.1-20211226 ("Convalmore") (Linux/5.15.139 (x86_64))
Cancel-Lock: sha1:NRizB5O93ELU11QO/XE2327J98g=

Ian <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> wrote:
> On 2025-03-18, Toaster <toaster@dne3.net> wrote:
>>
>> But what can be done to mitigate this issue? Crawlers and bots ruin the
>> internet.
> 
> #mode=evil
> 
> How about a script that spews out an endless stream of junk from
> /usr/share/dict/words, parked on a random URL that's listed in
> robots.txt as forbidden. Any bot choosing to chew on that gets what
> it deserves, though you might need to bandwidth limit it.

Another option could be to craft a "gzip bomb" (a carefully crafted 
zlib compressed file that is compressed to the maximum limits of the 
zlib/gzip algorithm) and return it with the http type of "gzip 
compressed".

Then you only have to output a few tens of megs, but if the AI 
decompresses the gzip bomb it has to consume multiple gigabytes of 
data.