╔══════════════════════════════════════════════════════╗
║ ║
║ PLEASE HELP. THE OLD-SCHOOL UNCLES ARE ║
║ EVERYWHERE. ║
║ ║
╚══════════════════════════════════════════════════════╝
Hello everyone,
I have remained silent about this for a long time, but the evidence has become impossible to ignore.
For years, I believed wargames were simply websites where people solved challenges, submitted flags, collected points, and occasionally complained about broken PHP.
I was wrong.
┌──────────────────────────────────┐
│ There is a much larger network │
│ behind all of this. │
└──────────────────────────────────┘
The old-school uncles are everywhere.
At first, I thought it was a coincidence. I would open a challenge from 2007 and find an uncle in the comments. I would search for a hint and discover a forum post by someone whose registration date belonged in a museum. I would follow a broken link through three archives and somehow end up on another uncle’s website.
Different countries.
Different communities.
The same recurring signs:
Old PHP.
Strange Perl.
Forgotten forums.
Quiet IRC channels.
And uncles.
I began investigating.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
01 / THE FIRST SIGNS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Modern platforms usually tell you what you are looking at. There are categories, tags, difficulty ratings, and sometimes even hints.
An old-school uncle gives you a page with one input box.
Above it, a message:
good luck
You spend six hours reading the source and another six examining HTTP headers. Nothing makes sense.
Eventually, you discover that the intended solution involves a browser bug from 2004, mentioned exactly once on a German mailing list.
You ask the author whether this was intentional.
yes
The answer explains the challenge.
The smiley face raises further questions.
╭────────────────────────────────────────────────────╮
│ 02 / THEY CONTROL THE MEANING OF "EASY" │
╰────────────────────────────────────────────────────╯
Old-school uncles appear to use a difficulty scale that is incompatible with the one used by the rest of humanity.
When a normal person says “easy,” they mean:
You should be able to solve this
without too much trouble.
When an uncle says “easy,” they mean:
I solved this in 2009 after three days,
so you should be able to solve it
in twenty minutes.
The three days are no longer part of the calculation. Neither are the two years of background knowledge, the custom tool they wrote, or the conversation they had with the author on IRC.
Only the twenty minutes remain.
This pattern appears across Germany, the Netherlands, Vietnam, France, and probably everywhere else.
I suspect there is an international standard for uncle difficulty ratings.
Unfortunately,
[ the documentation is a dead link. ]
───[ 03 / THEIR RELATIONSHIP WITH TIME IS SUSPICIOUS ]───────
Normal people disconnect.
Old-school uncles do not.
You enter an IRC channel.
Nobody speaks.
Ten minutes pass, then an hour.
Just as you are about to leave, someone writes:
hi
You reply immediately.
Nine hours later, they answer as though the conversation had never paused.
There is no apology for the delay, because apparently there has been no delay. You are simply participating in a conversation whose timescale you do not yet understand.
Some of these people seem to have been idling in the same channel since before Discord existed. They may have changed computers, jobs, or countries during that time.
Their nickname has not moved.
Whatever timezone they live in, my operating system does not support it.
╔══════════════════════════════════════════════════════╗
║ 04 / THE NETWORK HAS NO HEADQUARTERS ║
╚══════════════════════════════════════════════════════╝
I do not believe the uncles are organized in any conventional sense.
There is no central server, no headquarters, and probably no shared calendar.
That would be too normal.
Instead, the network seems to operate through forum signatures, shoutboxes, PHP comments, forgotten Git repositories, and links labeled “friends” on websites nobody has redesigned in eighteen years.
broken link
↓
archive
↓
nickname
↓
repository
↓
unknown wargame
↓
registration page
The registration page still works.
Somewhere, an uncle notices you
in the access logs.
People often assume these corners of the internet are empty because they are quiet. Sometimes they are. But sometimes a challenge is still running, someone is still paying the hosting bill, and its author is still around.
You just have to ask your question and allow approximately one IRC conversation for a response.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
05 / I MAY HAVE MISUNDERSTOOD
THE PROGRESSION SYSTEM
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
This is where the investigation became personal.
I have spent years wandering through different wargames. I thought I was collecting points.
But gradually, something changed.
At first, I only cared about solving challenges. Then I started recognizing the people who wrote them. I became curious about the history of the platforms. I began talking to operators and spending more time in communities.
Eventually, I started thinking about building something myself.
I now suspect the real progression system is:
Player
↓
Contributor
↓
Builder
↓
Operator
↓
UNCLE
Nobody explains this when you register.
There is no warning when you create your account. No confirmation dialog appears the first time you think,
“It would be a shame if this disappeared.”
One day, you are learning SQL injection. The next, you are explaining a challenge that vanished twelve years ago to someone who has never heard of the platform.
Then you catch yourself saying:
back in my day...
I thought WeChall was tracking my scores.
It may actually have been documenting my transformation.
╭────────────────────────────────────────────────────╮
│ 06 / A FIELD GUIDE FOR NEW ENCOUNTERS │
╰────────────────────────────────────────────────────╯
If you encounter an old-school uncle, remain calm.
[!] Do not ask their exact age.
[!] Do not immediately question
the website’s design.
[!] Above all, do not open the conversation
by suggesting that the entire platform
should be rewritten in a framework
released last Tuesday.
Listen first.
They may give you the clue you needed, the history you did not know you were missing, or a completely unrelated story about a server that caught fire.
It is impossible to know in advance.
This is part of the experience.
When an uncle says a challenge is “easy,”
clear your evening.
When they say “just think,”
leave tomorrow flexible.
If they send you a smiley face, do not panic.
It may be encouragement.
It may also be the entire hint.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
07 / WHY WE SHOULD CHERISH THEM
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Behind all these jokes is something I genuinely appreciate.
These people built much of the maze
we still explore.
They wrote challenges for no money.
They answered questions from strangers.
They fixed things that almost nobody noticed were broken.
They kept communities alive long after the initial excitement had passed.
A ranking can tell you who solved a challenge.
It rarely tells you who spent a weekend repairing the server so that anyone could solve it at all.
Not every platform survived.
Domains expired.
Forums disappeared.
Source code was lost.
But the people often remained, carrying the things that were never properly documented:
why a challenge was written,
where an idea came from,
who helped build a platform,
and what it felt like to be there.
Then they passed some of that knowledge to new players.
Those players built new things.
That is why I am writing this—not to expose some secret uncle conspiracy, but to appreciate the people behind it.
┌────────────────────────────────────────────────────┐
│ Preserving that history does not require every │
│ old server to run forever. │
│ │
│ Sometimes it means saving the source, writing │
│ down a story, crediting an author, or thanking │
│ someone while they are still around to hear it. │
└────────────────────────────────────────────────────┘
We should not wait for a farewell announcement to say that a place mattered.
╔══════════════════════════════════════════════════════╗
║ 08 / ONE DAY, IT WILL BE US ║
╚══════════════════════════════════════════════════════╝
Today’s player
↓
tomorrow’s uncle.
The people we now think of as old-school were once newcomers too.
They got stuck.
They asked for hints.
They stayed awake far too late trying to understand something that would look obvious the next morning.
They probably broke a few things along the way.
And then, somehow,
twenty years passed.
One day, younger players will discover our old posts.
They will laugh at our tools and wonder why we used such primitive AI models.
The infrastructure we currently consider modern will look ancient.
We will try to explain that things were different then.
They will politely pretend to listen.
And when they get stuck on one of our challenges, we will find ourselves typing:
this challenge is easy
The cycle will be complete.
──────── KEEP THE MAZE ALIVE ────────
So explore the forgotten wargames.
Read the old forum threads.
Remember the people who built the places where you learned.
And when your turn comes, leave something behind:
a challenge,
a write-up,
some source code,
or a patient answer
to someone who is stuck.
The servers may disappear.
The rankings may change.
The technologies certainly will.
But something of those old mazes survives whenever a former player builds a new one—and leaves the door open for the next curious stranger.
╔══════════════════════════════════════════════════════╗
║ ║
║ CHERISH OUR OLD-SCHOOL UNCLES. ║
║ ║
║ AND WHEN YOUR TURN COMES, BE A GOOD ONE. ║
║ ║
╚══════════════════════════════════════════════════════╝
— rayaseiren
Current status:
slowly becoming an uncle
