Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> |
|---|---|
| Newsgroups | comp.misc |
| Subject | Re: bad bot behavior |
| Date | 2025-03-23 14:30 +0000 |
| Organization | the-candyden-of-code |
| Message-ID | <slrnvu06ha.2o4dt.candycanearter07@candydeb.host.invalid> (permalink) |
| 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> <vret57$197b5$1@dont-email.me> |
Rich <rich@example.invalid> wrote at 16:59 this Wednesday (GMT):
> 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.
Good idea, but you should still put in some text to warn a real user
just in case.
--
user <candycane> is generated from /dev/urandom
Back to comp.misc | Previous | Next — Previous in thread | Next in thread | Find similar
bad bot behavior Ben Collver <bencollver@tilde.pink> - 2025-03-18 15:17 +0000
Re: bad bot behavior D Finnigan <dog_cow@macgui.com> - 2025-03-18 12:00 -0500
Re: bad bot behavior not@telling.you.invalid (Computer Nerd Kev) - 2025-03-19 08:19 +1000
Re: bad bot behavior Toaster <toaster@dne3.net> - 2025-03-18 18:20 -0400
Re: bad bot behavior Ian <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> - 2025-03-19 12:06 +0000
Re: bad bot behavior Rich <rich@example.invalid> - 2025-03-19 16:59 +0000
Re: bad bot behavior candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-03-23 14:30 +0000
Re: bad bot behavior Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-20 02:22 +0000
Re: bad bot behavior Ian <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> - 2025-03-20 08:33 +0000
Re: bad bot behavior Toaster <toaster@dne3.net> - 2025-03-20 19:01 -0400
Re: bad bot behavior Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-03-21 08:05 +0000
Re: bad bot behavior Ian <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> - 2025-03-21 08:42 +0000
Re: bad bot behavior candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-03-23 14:30 +0000
Re: bad bot behavior D Finnigan <dog_cow@macgui.com> - 2025-03-26 08:38 -0500
Re: bad bot behavior candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-03-26 17:00 +0000
Re: bad bot behavior not@telling.you.invalid (Computer Nerd Kev) - 2025-03-27 07:55 +1000
Re: bad bot behavior anthk <anthk@openbsd.home> - 2025-05-12 06:24 +0000
Re: bad bot behavior anthk <anthk@openbsd.home> - 2025-05-12 06:24 +0000
csiph-web