← Back

Seattle Surveillance Walking Tour: Privacy Risks Uncovered

A walking tour documents Seattle's hidden surveillance cameras and Wi-Fi tracking. HN commenters debate language and practical tools like OpenStreetMap.

Seattle's surveillance infrastructure is hidden in plain sight—cameras on traffic poles, Wi-Fi sensors in streetlights. A new walking tour, documented on Coveillance.org, maps these systems block by block. The tour has sparked a heated discussion on Hacker News, with commenters both praising the effort and criticizing its academic language. Here's what you need to know.

What the Tour Reveals

The walking tour takes you through downtown Seattle, pointing out automated license plate readers, police cameras, Wi-Fi tracking sensors, and even Amazon's Sphere's facial recognition (allegedly). Each stop describes the technology and its data collection implications. The tour is part of the Coveillance project, which aims to make surveillance visible.

Key players include the Seattle Police Department, the Washington State Department of Transportation, and private companies like Amazon. The infrastructure is often disguised: cameras on traffic poles, sensors in streetlights. The content mixes technical details with theoretical language about "gazes" and "social agreements."

Why HN Commenters Are Split

The Hacker News thread (score 85, 23 comments) shows a split reaction. Some commenters appreciate the effort and point to practical tools. For example, one commenter wrote:

"With mapcomplete.org/surveillance, anyone can easily see and update surveillance cameras in OpenStreetMap."

That's a concrete takeaway: you can contribute to and browse a public map of surveillance cameras.

But others criticized the article's language. One commenter said:

"Lots of po-mo art-school language on this site about 'encoding ways of seeing' and 'gazes.' The content itself is somewhat interesting but imo plain language would be more accessible."

Another wrote:

"The phrase 'kinds of gazes' strikes me as the sort of thing that's only going to make sense to people trained in a very particular and idiosyncratic flavor of ethical critique."

This tension is recurring: academic jargon may alienate the technically-minded audience who would find the information valuable. There's also a technical correction: one commenter pointed out that modern devices use broadcast probes rather than directed probes to avoid leaking past network lists, contradicting the tour's claim about probe packets revealing your history. For more on Wi-Fi probing, see the Wikipedia article on MAC address randomization.

Key Takeaways for Privacy Tool Builders

The walking tour raises awareness, but the language criticism is fair. To reach engineers and policy makers who can change how surveillance is deployed, use plain language. The substance, however, is important.

Concrete Implications for Your Projects

  1. OpenStreetMap as a data source: The MapComplete project shows that OpenStreetMap's surveillance tagging is a living database. Use the Overpass API to query it. For example, to get all surveillance cameras in Seattle:

    [out:json];
    area["name"="Seattle"]["admin_level"=6]["type"=boundary];
    node(area)["surveillance"="camera"];
    out;
    

    This could feed an app that alerts users near known cameras.

  2. Wi-Fi probe request privacy: Even modern clients that randomize MAC addresses still broadcast probe requests for previously connected networks. If building a Wi-Fi scanner app, consider not logging probes, or inform users how to disable probing.

  3. Facial recognition concerns: The tour mentions Amazon's Rekognition in the Sphere. Whether that specific claim is accurate, cloud providers offer cheap facial analysis. If you use such APIs, be transparent.

  4. Accessible language matters: Document your privacy tools with clear, jargon-free explanations. The academic tone of the original tour may limit its impact.

Conclusion: Should You Care?

If you live in or visit Seattle—yes, this is your neighborhood being mapped. If you're a developer building privacy or mapping apps, this is a real-world example of the problem you're solving. If you're a technologist interested in surveillance, the crowd-sourced OSM map offers more practical value than the tour's theoretical prose.

The conversation is a reminder that how we talk about surveillance matters as much as the data itself.