1.3.1. With so much material available, why another FAQ? 1.3.2. No convenient access to archives of the list....and who could read 50 MB of stuff anyway? 1.3.3. Why not Web? (Mosaic, Http, URL, etc.) - Why not a navigable Web document? - This is becoming trendy. Lots of URLs are included here, in fact. But making all documents into Web documents has downsides. + Reasons why not: - No easy access for me. - Many others also lack access. Text still rules. - Not at all clear that a collection of hundreds of fragments is useful - I like the structured editors available on my Mac (specifically, MORE, an outline editor) - 1.3.4. What the Essential Points Are - It's easy to lose track of what the core issues are, what the really important points are. In a FAQ like this, a vast amount of "cruft" is presented, that is, a vast amount of miscellaneous, tangential, and epiphenomenal material. Names of PGP versions, variants on steganograhy, and other such stuff, all of which will change over the next few months and years. + And yet that's partly what a FAQ is for. The key is just not to lose track of the key ideas. I've mentioned what I think are the important ideas many times. To wit: - that many approaches to crypto exist - that governments essentially cannot stop most of these approaches, short of establishing a police state (and probably not even then) - core issues of identity, authentication, pseudonyms, reputations, etc.
Next Page: 1.4 Who Should Read This
Previous Page: 1.2 Foreword
By Tim May, see README
HTML by Jonathan Rochkind