Wow awesome stuff! Just had a look and I think some of the nice illustrations and explanations can be reused in the user guide. Like e.g. the follow graph illustration.

Now that we have these great docs for the protocol, we need to keep them accurate.
Therefore proposed changes to the protocol should be represented as Pull Requests to the protocol documentation.

I must also say that I am personally quite thrilled that you spent the grant money on a boat!

@vtduncan wow. absolutely beautiful documentation :).

@vtduncan wow, what a pain in the git!

Btw, did you hand-write the source as html? it looks like markdown (with occasional html for tables) would be convienient...

I am thinking about process for governing changes to the protocol - i.e. submitting improvement proposals - even if "acceptance" just means enough implementers implement the change, you still want clear specs. Also, since more than one proposer might be working on proposals concurrently, we want these to merge cleanly, and not have css conflicts.

hey @duncan your website seems to be down, can you link out to the git repos where this lives?

HERE:

• https://ssbc.github.io/scuttlebutt-protocol-guide/
• https://github.com/ssbc/scuttlebutt-protocol-guide