Watching the Watchers

Public life has always been curated—by flags, by anthems, by who gets a microphone. What’s different now is the plumbing: tiny cameras, fingerprinted TLS stacks, and automated gatekeepers that decide who walks, scrolls, or even exists in a dataset. These are mundane seams of civic power, but they stitch together very consequential outcomes.

You’ll see this logic in three apparently unrelated places gathered here: a hacker’s how-to on blocking bots, a minimalist CCTV project on GitHub, and the glossy machinery of big‑stadium sports and celebrity transfers. Put them together and you get a recipe for modern control: instruments that are cheap enough for communities to wield and precise enough for states to weaponize.

If you live in Minnesota—or any state where enforcement agencies and civic institutions rub shoulders—you should care. The questions are simple and uncomfortable: who gets to surveil, who gets protected from surveillance, and who profits from building the bridges between them?

If you think bots are a niche sysadmin headache, read the rough guide titled “How To Block Some Of The Bots” and then imagine replacing “bot” with “migrant,” “protester,” or “journalist.” The piece walks through nine pragmatic techniques—HTTP/2 enforcement, IP blackhole routing, TLS fingerprinting, Brotli precompression, and more—each measured against collateral damage and operational risk. It’s blunt, usable, and intentionally unsuited to revenue-generating environments: not because it’s illegal, but because it is blunt-force civic surgery. See the original notes at Hacker News.

Two points matter for civil‑liberties watchers. First, the toolkit is dual‑use. The same set of filters that keeps scrapers out of a hobby blog can be adapted by municipal or federal actors to throttle access to news sites, legal aid portals, or community organizing pages—especially when those pages are thinly staffed and low on legal cover. Second, the methods prize observable signals—IP ranges, headers, TLS quirks—over substantive adjudication. That suits automation and avoids court fights in the short term; in the long term it creates a world where access is a stack of heuristics instead of a legal right.

Consider the operational incentives. Public agencies facing budget constraints will prefer programmatic, low-cost filters to the messy work of warrants and human review. Meanwhile, activist groups and community defenders will be tempted to adopt the same cheap defensive tools. The result: a proliferation of gatekeeping tech, wielded by everyone from city parks to border agents. A small, technical how‑to becomes a civic‑scale lever.

Stadiums are the modern agora—huge crowds, lots of emotion, and plenty of money. The Big Ten’s stadium list reads like a ledger of civic capacity: from Northwestern’s 35,000 seats up to Michigan’s 107,601, you get a sense of scale and what those scales buy in terms of infrastructure and surveillance optics (USA Today).

Why does that matter to someone worrying about ICE or municipal policing? Because every extra seat is another reason to justify cameras, license‑plate readers, perimeter fencing, facial analytics pilots, and the “security” vendors who sell them. Large venues are negotiation points: teams want revenue, cities want the tax receipts, and vendors offer turnkey systems that end up being shared with law enforcement on vaguely defined grounds. Once the cameras are in—once the central monitoring room exists and the data pipelines are built—they almost never go away.

A couple of predictable, annoying outcomes follow:

• Security upgrades normalize intrusive data collection for ordinary civic events.
• Commercial motives (sponsorships, VIP zones) blur into public safety justifications.
• Data collected for crowd management becomes a tempting trove for enforcement agencies.

So while fans cheer at a game, the fabric of public surveillance tightens. The city paints it as safety; vendors call it modernization; rights advocates call it scope creep. None of them are wrong, but the people most affected—migrants, protesters, everyday attendees—are rarely asked.

There’s a flattering libertarian narrative in the GitHub project CheapSecurity: build your own CCTV stack on a single‑board Linux box, keep video local, and avoid monthly cloud fees. The repo is straightforward, AGPLv3‑licensed, and offers motion detection, telegram alerts, and local storage management—small, practical things that enable data sovereignty for households or small organizations (GitHub).

That’s the empowering half of the story: communities that have been targeted by overzealous policing or that distrust corporate clouds can gain a documentary capacity that previously required expensive vendors. Want to record a traffic stop, document a raid, or keep an eye on a private landlord? Affordable, self‑hosted cameras lower the barrier.

The darker half is structural. Cheap, private surveillance is also cheap to repurpose. Landlords, private security, and municipal agencies can run the same stack with a different intent. The very features that make CheapSecurity attractive—automatic uploads, alerts to Telegram, systemd service files for robustness—also make it easy to build a discreet, distributed sensor network. A few operational realities follow:

• Local retention reduces corporate surveillance risk but increases the danger of local coercion—seize a hard drive, and the story ends.
• A network of inexpensive cameras can turn every block into a passive sensor field for enforcement agencies, either through legal requests or informal data‑sharing.
• Open licenses and simple deployment put this power into many hands at once, which is both a civic safeguard and a recipe for uncoordinated escalation.

The choice facing privacy‑minded Minnesotans is stark: deploy to protect, or abstain to avoid contributing to population‑scale monitoring. There’s no technical silver bullet; the solution is political.

Sports are theatre, and stars are catalysts. When LeBron James chose Philadelphia—prompting a social media tidal wave and even a gubernatorial declaration of "LeBron James Day"—the city’s cultural machinery leapt into high gear (USA Today). Meanwhile, an intrasquad USA hockey scrimmage did something quieter but important: it turned a practice ice into a high‑stakes audition for adolescents hoping for a December roster (Detroit News). One is spectacle; the other is small‑scale evaluation. Both are disciplines in attention allocation.

Why mention sports in a newsletter about enforcement? Two reasons. First, spectacle concentrates resources—security, media, and public attention—around high‑value civic moments. Those are precisely the moments when enforcement agencies test new tools or claim operational necessities. Second, spectacle is a social blinder: while cities celebrate a star and sell commemorative merch, privacy‑reducing infrastructure is often installed quietly and justified as a safety imperative.

So when communities in Minnesota rally around a local team or a star athlete, remember the invisible ledger: more cameras at the arena, more data retentions in municipal systems, more pressure to centralize monitoring. Sports will continue to be a good—and profitable—distraction. That’s not inherently malicious, but it’s worth being suspicious when the price of a parade is a permanent expansion of surveillance powers.

There’s an old tradeoff in civil‑liberties work: technologies that let vulnerable people document and defend themselves also make it embarrassingly easy for authorities to do the same at scale. Cheap tools, clever heuristics, and civic spectacle are not neutral; they reconfigure power.

If you live in Minnesota or any state where immigration enforcement rubs up against everyday civic life, the action items are modest and political:

• Demand transparency before new camera systems are activated.
• Insist on clear data‑retention limits, local oversight, and subpoena resistance where possible.
• Treat automated access controls—not as neutral security—but as policies that require public debate and legal scrutiny.

A last, slightly bitter note: regulations lag because regulation is boring and cameras have good PR. Celebrities score days on calendars; log files don’t. We should legislate for the log files. Otherwise the watchtower will be built by vendors and justified by applause.