Hi,

Sorry for the slow reply, I'm not subscribed to the debian-www mailing
list so only found out about this question today (also please keep me on
CC for replies).

> hi, i've been falsely flagged as an ai on ftp.uk.debian.org/debian
> i just have a question
> wtf does "Yourself to break. It was. Hands. For a. Had dreamed of did exist, 
> and never again could exist, any standard. The bathroom." even mean???????

As Ceppo says, it means nothing, and intentionally so.

What you are seeing is the output of iocaine:

  https://iocaine.madhouse-project.org/

Sadly, specifically for HTTP connections from web browsers, it's not
100% able to distinguish bots from humans, but it is very good on HTTPS
connections, and (as far as I know so far) it's also never identifies
requests from apt as bots, so serves it's main purpose without issues.

The reason I need to run something like iocaine is that the LLM bots
follow every link, which means that they grab copies of the whole
archive, including ancient .debs that are otherwise left alone for
months or years at a time. That constantly fills memory with rubbish,
flushing out the recently uploaded packages that everyone wants,
reducing the speed they can be served at from memory-speed to
disk-speed, and making the disks 100% busy, which is a pretty effective
DDoS. Without iocaine the server was regularly unusably slow, whereas
now it's back to its normal performance.

I think what I need to do, but have not yet worked out how to do, is
make it so that when it comes to the particular case of
ftp.uk.debian.org accessed via HTTP, instead of immediately serving up
nonsense, it should instead redirect to https://ftp.hands.com/$same_path
(or perhaps https://debian.hands.com/... which is the same thing).

That way it will then correctly identify the bots, without
inconveniencing humans, since that will be a HTTPS connection.

BTW I cannot redirect to https://ftp.uk.debian.org/ because this is not
a debian administered machine (it belongs to and is administered by me),
so there's no practical way of dealing with the certificates that would
be required, and if we created such certificates they would be largely
meaningless/misleading (especially when ftp.uk.debian.org gets pointed
to other servers when mine is down for maintenance).

Out of interest, why were you browsing the site?

Were you having a problem with apt that you wanted to diagnose?

Would your needs have been properly served by ending up at the same
place on https://ftp.hands.com/ instead?

Cheers, Phil.
-- 
Philip Hands -- https://hands.com/~phil

Attachment: signature.asc
Description: PGP signature

Reply via email to