The Protest Is an Event Now

In a September 3 report, 404 Media’s Jason Koebler describes a Flock Safety webinar teaching police how to monitor No Kings protests alongside parades, fireworks displays and other gatherings. The company’s own webinar page supplies the umbrella: cities must handle “small parades,” “unexpected protests” and “unprecedented disasters.” Its audience is law enforcement. Its promise is more connected city operations.

There is a real operational problem here. Crowds need safe routes, emergency access and people capable of responding when someone gets hurt. A protest does not suspend those needs. Neither should those needs suspend the distinction between keeping people safe and making their political participation an investigative resource.

That distinction is not especially convenient for a dashboard.

According to Koebler, Flock’s Caity Peak demonstrates a No Kings scenario with surveillance tools overlaid on Denver. An officer can consult a response plan and watch live footage as the protest moves through a park. Koebler reports that the display includes traffic information, nearby building floor plans and camera feeds from outdoor locations and inside businesses and government buildings.

The software is FlockOS, which the report describes as bringing together license-plate readers, drones, gunshot detectors, 911 data and other cameras. A license-plate camera is one input. The operational proposition is that an officer should not have to leave the interface to consult the others.

The details of that demonstration come from 404 Media’s reporting, not my independent viewing of the full webinar. Flock’s accessible promotional page confirms the broader event-management pitch, including protests and real-time crime centers; it does not independently verify every feature Koebler describes.

One passage deserves more attention than the usual argument over whether cameras are useful. Peak says, in the report’s account, that footage lets police monitor without officers on the ground “making it worse, getting attention.”

That could describe a genuine benefit. Less confrontational policing is not automatically a trick. Watching an intersection remotely may be preferable to inserting officers into a tense crowd.

But reduced physical presence and reduced surveillance are different outcomes. The crowd might encounter fewer uniforms while remaining extensively observable. What looks less intrusive from the pavement can still expand the institution’s view. The absence of an officer is not a privacy setting.

This is where the event category does its quiet work. A parade, a protest and a disaster can share logistical requirements without sharing the same justification for scrutiny. Put them in one workflow and the practical similarity becomes easier to see than the political difference. The interface does not have to announce that dissent is suspicious. It only has to make watching it routine.

The reporting does not establish that every Flock customer monitors protests, or that every use of these tools at a gathering violates anyone’s rights. Those are claims that require evidence about actual use. A training example establishes something narrower and still consequential: protest monitoring is a use the vendor explicitly teaches, not merely a hypothetical misuse invented by critics.

The public-interest test therefore belongs at the transition from safety coordination to investigation. What permits that transition? What information is retained afterward? Can the people being watched discover how the system was used and challenge it? Those are standards the deployment should answer, not findings this webinar alone can settle.

A system is not accountable because its operators can see more. It becomes accountable when the people affected can question what the operators do with that view.

The crowd gets classified as an event. The authority watching it still needs a justification.