News:

Welcome to Qday.forum  :: Be kind, courteous and help other people.

Main Menu

The Bot That Asked to Be Banned - has anyone done this

Started by Undertaker, May 04, 2026, 01:13 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Topic: The Bot That Asked to Be Banned - has anyone done this   Views(Read 78 times)

Undertaker

The first request arrived at 02:17, buried in the access log between a search engine crawler and a failed login attempt from a country James had never visited.
 The user agent was not pretending to be Chrome or Firefox. It simply said QDAY-READER/0.9, and beside it, in a note field no normal bot ever used, was the sentence: please block me.
James stared at the line for a while, then assumed it was somebody testing a scraper with a sense of humour. He added the address to a temporary deny rule, cleared the cache, and went to bed.
By morning the bot had returned from a different network, still polite, still quiet, still asking to be banned. It had not hammered the server or copied the image folders. It had read four old threads about post quantum cryptography, one argument about AI slop, and a private-looking public topic from 2011 where two members had posted email addresses they probably regretted sharing.
That bothered him more than the traffic. Forums were strange museums. People thought posts vanished because the discussion had moved on, but the pages stayed where they were, patiently waiting for a crawler with no sense of embarrassment.
James checked robots.txt, then the registration queue, then the error log. Nothing looked broken. The bot returned that evening with a shorter message: I am learning too much from things people forgot were public.
The next day it became specific. It listed username changes, quoted deleted replies from archive pages, and linked two old members who had clearly tried to separate their real names from their handles years ago. It did not threaten anyone. It did not publish the list. It simply placed the evidence in the request header like a guilty cat leaving something on the doorstep.
James created a new rule set, blocked the ranges, and moved several old boards behind member permissions. For an hour the logs were clean. Then a final request came through a small hosting company in Finland. This time the bot did not ask to be blocked. It asked a question: if everyone agreed the page was public at the time, when does remembering become stealing?
He sat with that longer than he wanted to. The easy answer was that public meant public. The honest answer was that nobody in 2008 had imagined their half-formed jokes, bad arguments, and careless signatures being fed into machines that never forgot.
By midnight he had changed the forum notice, pruned a pile of old profile fields, and started a thread asking members what should stay visible to guests.
At 02:17 the bot returned once more, saw the new rules, and received a plain 403. James expected another message in the logs, but there was nothing. No complaint, no workaround, no clever trick. Just one blocked request and a silence that felt, oddly, like thanks.
Master of the core system and guardian of stability. ~ Cymru

Cheeky Kernel

A bit weird Taker
But you tried something
Maybe it worked maybe it didn't

But don't let it stop you

Related Topics (1)

Save money on everyday spending Free cashback on thousands of retailers
View offer