I think the real question is - why does NSA make their own in-house training manuals for programming languages? Seems likely to get outdated fast. Do they have internal tutorials for Ruby, TCL, Lisp?
I adore governments' classification system which can state things are classified as 'unclassified', and by extension to hijack the meaning of 'classified' to mean 'top secret'.
On a topic relevant note, from the original twitter feed [0] which announced/released this (as part of FOIA) a helpful person also mentioned a lightweight download of the ?same document[1] (18MB vs 118MB).
That's apparent to the guy you're responding to. He's pointing out that the so-called "unclassified" is actually the class "non-secret". A truly "unclassified" object would not have gone through the process of classification. It would not have a class.
Of course in English this is fairly common. The object of price zero is said to have no price. Yet clearly it has a price, it is just zero.
I have to say that's an amusing observation and sort of reveals the type errors that occur when we model real world things in type systems.
True, but there are documents that have information that is at multiple levels of sensitivity and/or classification. When you work with such information, having such granularity of classification is a good thing (no matter how awkward it looks).
The United Kingdom's previous system for marking school exams (GCSE) had a marking scheme from "A*/A" to "F", and then "U". Where "U" was Ungraded. Clearly it was graded, but as a "U".
There’s probably nothing to this, but when I try to screenshot the pdf (https://ia802805.us.archive.org/7/items/comp3321/comp3321.pd...) on iOS Safari, my phone locks up for a moment with a black screen and spinner and then I have to unlock the phone. Doesn’t happen on other PDFs on archive.org or after I’ve saved it to iBooks. Can anyone replicate? Is this perhaps the result of some byzantine configuration state in the PDF spec that Apple has chosen to implement or that their implementation is choking on?
When taking a screenshot in safari on iOS 13 it also tries to save a pdf of the entire page. If you open the little screenshot overlay in the corner there is an option to save as the full page as pdf instead of a screenshot.
Maybe the pdf is just too big to be re-rendered and saved as a new pdf and it crashes somehow.
