Topics discussing when software code acts as a form of policy, what Lawrence Lessig , author of Code and Other Laws of Cyberspace would call (US) "East-coast-code meets West-coast-code".

secret testing for public elections

As far as I know, most if not all Canadian voting machines are certified to US standards, in the absence of any Canadian ones. This testing is done by three secretive US testing labs.

In a good Computer World story E-vote at Risk, they report

One of the most critical aspects of the voting system development process is the testing and certification of hardware and software to ensure that they meet voluntary federal voting standards for security and reliability. Three vendors act as so-called independent testing authorities (ITA). However, IT experts are highly critical of the testing process because of its secrecy.

Code=Law: Computer Problems Already Affecting Florida Voters

An article on SlashDot titled: Computer Problems Already Affecting Florida Voters prompted me to write an article about ICT fraud in the DCC mailing list.

As I am drafting my mini auto-biography I have also written down related thoughts in the Code is law section.

Voting machine "humour": the Florida vote

This site tries to demonstrate one problem with voting machines in a humourous way.

New topic area: Code=Law

In his book, CODE and other laws of cyberspace, Stanford Law School professor Lawrence Lessig introduced the idea that software code acted as a form of law. If code is a form of law that regulates us, why must we treat that code as simply another product? Should we not be questioning this highly pervasive form of governance? Should we not be demanding the same level of transparency and accountability for this code as we do other regulation?

Syndicate content