| Age | Commit message (Collapse) | Author |
|---|
|
The text uses "scheme" and "version" a couple of times. The formal
protocol says "type". The terminology should be consistent. IMO
"scheme" is the best word to use. "version" is particularly bad.
Change all references to "type" and "version" to "scheme".
|
|
Done by grepping for "cell" and making sure it was accurate in every
place where it occurs. In tor-spec, I also searched for "message".
Part of #253.
|
|
|
|
This mostly updates formatting and links. I added a little bit of new
context, primarily a disclaimer and updated benchmark info for
analysis-discussion.md
|
|
Formatting and structural edits to try and make the common-protocol
section go together. Ended up repurposing parts of 'overview' for
an introduction here, and deleting the separate overview section.
|
|
This started as a formatting-oriented edit pass, but much of this was
badly in need of fresh context now that the protocol is implemented and
we have a more fully developed idea of what performance characteristics
to expect.
|
|
This retains the overall structure and order from before, but everything
is reformatted into Markdown, with some minor edits and some fresh context
and fresh hyperlinks.
The data formats for the descriptor the and intro extension have moved out
of the PoW spec entirely back into the main Tor spec, so those sections
have been replaced by terse descriptions and links.
|
|
|
|
This establishes a new outline for the hspow-spec. Otherwise, it's just
cut and paste without any content edits. This also does not yet fully
disentangling the common and v1-specific pieces of the document.
|
|
|
|
This will be broken up into sections by future commits.
|
