Language analysis — the whitepaper
One rule before we start, and it decides what this block may claim. What follows is an analysis of the language of one document. It is not an analysis of the author’s language. A single technical paper of roughly 3,500 words, written in a formal register, is the weakest material a stylometrist can be handed: formal writing flattens the habits that identify a person. So we count, and we hold the result. The point of counting now is to have a baseline. When the emails and the forum posts arrive — thousands of sentences written quickly, without editing — we will ask whether the same habits reappear.
COUNTED NOW register ............. formal, impersonal sentence length ...... short for the genre terminology .......... defined once, no synonyms first person ......... rare, announcing only RECORDED, NOT READ YET spelling variants .... sample too small punctuation habits ... sample too small idiom / phrasing ..... sample too small
On spelling variants — the question everyone asks first — we say only this: a document of this length, in this register, contains too few of the words that separate one variety of English from another to support any conclusion. We have recorded every instance we found and will publish the tally when there is enough material to make it mean something. That will be after the emails, not before. The honest summary of this block is that the whitepaper is written to be checked, not to be admired. That is itself a habit, and habits repeat.
Block sources (originals): bitcoin.org/bitcoin.pdf
- +1 FINDING #8
- +1 TRACE T-008 · specification register
- 0 CONTRADICTIONS
- ○ SPELLING TALLY · held until the emails
Back to the list: the first reply
The whitepaper is read. Now the chronology resumes where we left it: less than forty-eight hours after publication, the first reply arrives on the metzdowd list — and it is not friendly. Friday, 14:10.