143 karma · joined June 2, 2009
It sounds like a better approach then many regulations that lead to very little.
It seems like a somewhat precarious decision to let you use Lisp for this project. There's nothing supremely special about the problem you are attacking that warrants Lisp (outside of your comfort level which you clarified very clearly in your post).
Perhaps I'm just old and cynical but I've been on too many projects where the first (and therefore "lead") developer chose a particular language and architecture that in the long term was not sustainable.
Frankly, most people's data is really not that important and the cinderblock attack is what truecrypt and similar crypto systems prevent. Every time you see a news item about "a million social security numbers have been compromised " - its always due to the cinderblock attack.
The "only" way to secure your data is to put your computer it in a vault (unplugged from AC outlet and no network access) with multiple physical security and surrounded by people with guns. If your data is that important and you can afford this sort of security...then the evil maid attack is irrelevant.
One thing that I wonder is how is a self reinforcing transaction affected when the third parties that used to mediate it are shut out. For example, certificate authority companies that are no longer needed.
Furthermore, the "all hands" in the room as opposed to secret ballot voting - while on the surface it is self reinforcing from a social perspective it wouldn't really work (i.e. the coercion he mentioned and also the lemming effect where someone votes with their crowd delaying raising their hand just enough to see what the consensus is).
Finally, the collusion and breakage of a self-reinforcing system like the pirate example shows that a self-reinforcing protocol is situationally dependent. What are the chances that at least one pirate will collude with the captain? (I bet the chance is quite high considering the nature of pirates) As opposed to the property tax example which seems to be a very good use of such a protocol.
And what a suave picture :-)
All kidding aside - how could you systematically enforce guidelines on applications when the universe of applications is wide open? In other words, there's no baseline so how could you create test case?
Wouldn't it make more sense to have a group of iphone users (i.e. folks that like to play with anything on the iphone) and have them vote on the app? (apple could reward these users with the app for free or some other random goodies - itouch, ipods, etc...)