But Leo wasn’t a villain. He was just bored.
That night, he decided to burn it all down. He wrote a kill-switch script designed to redirect all proxy traffic to a Rick Astley YouTube video. But just as he hit deploy, a private message appeared in his GitHub inbox:
On day three, Leo walked into Mr. Grimes’s office and slid a USB drive across the desk. “The source,” he said. “I built it. But here’s the thing—it’s not just kids watching dances. There’s a kid in rural Arkansas using this to livestream his robotics club because his school blocked YouTube. There’s a deaf student at Central using it to access sign-language tutorials.” tiktok unblocked github io
“Teach me how to fork that repo properly,” he said. “And next time? Open a pull request before you break my network.”
On day two, Mr. Grimes pulled Leo into the IT closet. “I ran a packet trace,” he said, squinting. “The proxy’s architecture is… elegant. Sloppy in places, but smart. You wouldn’t know anything about that, would you?” But Leo wasn’t a villain
Mr. Grimes deleted the logs. Then he wrote a new line of code into the school’s firewall—a hidden exception for educational content only. He closed the laptop and looked at Leo.
Worse, the comments section on the repo’s archived issues was filling up with usernames from other schools. “Can you add a dark mode?” “Does this bypass Cisco Umbrella?” “Hey, this is down in Houston—pls fix.” He wrote a kill-switch script designed to redirect
The next morning, Mr. Grimes stood at the front of the library, arms crossed. His bald head gleamed under the fluorescent lights like a warning beacon. “Someone,” he said, voice calm but sharp, “built a backdoor. The board is concerned about ‘bandwidth misuse.’ I have seventy-two hours to find the source.”