The thing about The Power Broker is that when you first see it you think, oh god, this is one of those impossibly long books people claim to have read but never actually do. But then once you actually crack it open, you’re just hooked.
It’s ostensibly a biography of Robert Moses, but it’s actually a political history of New York and the power of infrastructure.
I first read it around 1982 or 1983, practically in one sitting. It’s enriched my understanding of so much about politics, power, infrastructure, and NYC.
Robert Moses was basically the J Edgar Hoover of NY highways and parks.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
For the record, I will not be offering my election integrity course at the University of Austin.
Even imagining doing that makes me want to hide under the bed.
I’m considering, however, a course in computation theory, covering such topics as Gödel’s completeness theorem, Turing’s Halting Solution, and why they don’t want you to know whether P=NP.
If you’re a computer scientist and you’ve not read this seminal work, you owe it to yourself to do so. (Un)fortunately, it’s become hard to find platforms on which the attack can be reproduced in the form described, but it’s a transformative experience when you do.
Mastery of the buffer overflow attack - not just understanding it conceptually, but actually being able to execute it - is like developing a terrible superpower. You start to understand the problem of security in an entirely different way. @aleph_one’s paper made that accessible.
Anyway, @aleph_one’s paper, and an exercise based on it, is assignment #1 in every security course I teach.
“Why did you block my other account? You must be an asshole.” You might not be learning the intended lesson here.
For the record, I block people for a variety of reasons, my being a capricious asshole being only one of them. Mostly I block people for being abusive or excessively tiresome.
If you’re unhappy about this, please feel free to make a first amendment complaint about me to your nearest police precinct. They’ll be glad to help you. Or complain to my employer (that’s George Mason University, remember).
So, “cryptocurrency technology" means digital signatures and hashes, at a minimum. So, which public key signature schemes do we teach 11th graders? Something based on elliptic curves, maybe? And where in the curriculum do we introduce chosen prefix attacks against hash functions?
Also, we’ll really need to start these kids with a good foundation in number theory and finite fields, not to mention the basics of differential and linear cryptanalysis. Better start in the 8th grade or so.
Or maybe they mean things like securing digital wallets. Which means we better getting them started in serious hardware reverse engineering techniques by the 9th grade or so.
Maybe vaccines are “communist” because of their side effect of protecting not just recipients, but also those with whom they come into contact. Perhaps a proper capitalist vaccine should be developed that protects recipients while creating extra risk for everyone else.
But of course, if the market wanted such a vaccine, it should exist already.
Apropos of nothing in particular, pedantic insistence on a particular usage of some relatively unimportant technical term is invariably uninteresting. I’m reminded of a few years back when…
… some random stranger here made a big deal about how obviously I didn’t know what I was talking about when I used “cryptography” when I “clearly” would have used “cryptology” if I knew anything at all about the subject...
The truth is that while cryptography and cryptology can be narrowly distinguished (the former refers to encryption, while the latter to the study of the field broadly), virtually no one actually working in the field finds the distinction important, and uses them interchangeably.