What Happened When We Shut the Door on Surveillance
In the past hour or so, we implemented a targeted firewall rule to block a recurring pattern of spoofed Linux-based visitors using mobile user agents and fingerprint obfuscation – a digital signature we’ve come to associate with passive surveillance, not real users.
The result?
Nothing. Silence. A total blackout.
When the Noise Was the Watcher
Before the block, we saw consistent and suspicious behaviour: repeat sessions from headless browsers, spoofed devices, VPN-hopped ASNs, all hitting the same few posts. It was surveillance, not engagement. A passive watch. A tap on the glass from behind a two-way mirror.
We called it out publicly. We set digital traps. We watched the patterns repeat.
And then we pulled the plug. They didn’t adapt. They didn’t reappear. They just… left.
Institutional Evasion Is a Pattern
This is more than technical. It’s behavioural. It’s institutional. When those tasked with “support” are exposed for covertly monitoring a disabled person’s advocacy platform, they don’t lean in. They vanish. And that silence? It’s a confession.
It tells us:
- They were watching – not responding
- They were uncomfortable being seen
- They’re not confident in their justification
- And they don’t want to explain themselves in public
That’s not just weak – it’s systemic evasion dressed up as discretion.
We’re Still Here. They’re Not.
If your “support system” disappears the moment it’s logged, fingerprinted, and mirrored back at itself, then it was never support – it was containment.
The Reasonable Adjustment isn’t shutting down. It’s documenting. It’s evolving. And it’s issuing an open challenge:
If you’re monitoring this platform under contract, by directive, or out of nervous curiosity — reach out. Let’s talk transparency, not cloaks and proxies.
The silence after the block didn’t scare us.
It proved our point.
With logs, clarity, and zero tolerance for disrespect disguised as “policy”.
Kieron JH
The Reasonable Adjustment
Be First to Comment