“But aren’t those expensive or sketchy?” Leo asked.

He typed the history site’s URL. No grey wall. No proxy warning. Just the old, grainy photograph of the harbour master’s cottage, loading fast and clear. He could browse every forum post, every scanned diary entry. The firewall didn’t even know he’d left the room.

He hit Enter. The translated page loaded. It was clunky, and the images were a bit squashed, but there it was: the forum, readable, clickable, unblocked . The filter saw only Google’s domain, not the forbidden one.

Leo stared at the screen, the same grey brick wall staring back. “This site is blocked.” His school’s firewall had struck again. For weeks, he’d been trying to access the digital archives of the Old Harbour Historical Society —a quirky, image-heavy site he needed for his local history project. But the school’s filter saw the word “forum” in its URL and threw up a digital “keep out” sign.

He grinned. For ten minutes, he downloaded photos of 1920s dockworkers and scanned letters from the site. Then, just as he was saving a crucial map, the page flickered. The school’s IT had patched the Translate loophole last week. The content vanished, replaced by the grey brick wall again. Slam.

He didn’t give up. He recalled another loophole: Google Translate. Some older filters treat Google’s translation service as “always safe.” The trick: instead of visiting the blocked site directly, you ask Google Translate to translate it from any language to another.

Maya finally put her laptop aside. “You’re using public tricks. The school knows those. You need a private tunnel.” She opened a clean browser window. “Ever heard of a VPN ?”