Skip to the main content
Filtering at the Wisconsin State Capitol

Filtering at the Wisconsin State Capitol

(updated 2/28)

From the Herdict blog:

Here at Herdict, we spend a lot of time looking at website blockages abroad, whether it be complete network shutdowns in Egypt or the ongoing blockage of sites like Youtube in China. But blockings occur at home as well, where their unexpected nature can make them a lot more insidious. For example, Amtrak offers wireless internet on its luxury Acela trains but routinely blocks sites it deems “inappropriate” as well as all streaming video which would slurp up the shared and discrete bandwidth available to all customers.

Monday, pro-union site announced that it was being blocked on the guest wireless at the Wisconsin Capitol Building.

CNN reported the Governor’s spokesperson saying this was nothing nefarious, and in fact all new sites are blocked on the network:

“The Department of Administration blocks all new websites shortly after they are created, until they go through a software approval program that unblocks them,”

Let’s think about how this would work. We don’t think they mean all new sites to the internet, which would be challenging, costly, and unnecessary (why bother finding and blocking sites that no one is trying to get to). We believe they mean new sites relative to their network, so a site commonly visited on their wireless internet, like, would appear on the white list and would connect automatically, while a site that had never been accessed from their network, like, say, (ok, we made that up, but some one should create that site), would be entered into a queue to be approved. This is a very restrictive and potentially expensive solution. Would all sites in this queue have to be manually checked for both “appropriate” content as well as lack of malware? If there is a manual process, we think we may have found a place for Wisconsin to cut its budget. If it’s automatic, then we want to know what software they’re using to process these requests, how long the queue is, what the average delay is between a request for a site and its approval, and what criteria is used to determine an “appropriate” site to be served on the guest network. We have further concerns about what metadata is collected on the users who are requesting these sites. Are such requests personally identifiable? What happens to these requests once they are processed? Is the information discarded, or retained, and for how long?


Also, Nancy Scola asked for help understanding the situation and posted a nice round up of the responses on the techPresident blog: The Results: Our Experiment in Crowdchecking the "Wisconsin WiFi" Claim.

Update, February 28: The Herdict crew is looking for help testing the hypothesis that the Wisconsin Capitol building guest wireless blocks Websense's "advocacy" category: A Herdict Experiment for Wisconsonites.

You might also like

Projects & Tools 01


Herdict collected and disseminated real-­time, crowdsourced information about Internet filtering, denial of service attacks, and other blockages.