I'd like to think we would all--cperciva included--welcome specific criticisms or errors, but by claiming they exist without naming them, you're asking us to take your word over his. Your score reflects the fact that you haven't earned that.
I very much respect Colin and fully expect him to kick my ass in arguments, but, in particular, I find a good portion of his advice does not square with my professional experience; in other words: he's saying things that lay developers have already heard, and, empirically, lay developers produce very bad crypto.
Even that is more than required by the fundamental message I'd hoped to convey; which is "making something and sharing it can be useful; giving non-specific criticisms from a noncommitted, unassailable position is not useful." Reputation is simply bayesian evidence with which one can weight an otherwise-unsupported claim.
[1] http://en.wikipedia.org/wiki/Planning_fallacy [2] http://en.wikipedia.org/wiki/Reference_class_forecasting
Where are those?
replacing actual knowledge of why and why not with useless favorism and indoctrination
I provided some explanation of why and why not in the talk. Slides != transcript.
EDIT: And no, the downvote didn't come from me.
As presentations are normally held, the slides are just key excerpts from the one hour talk he was holding while the slides whizzed by.
I would not recommend this particular presentation to anyone.
add.: Thanks for the downvote, Colin :D Oh boy...