You are reading content from Scuttlebutt
@Dominic %fFBGx4sdoGKKTfiE2R4elADRi7+Xzoyi70g37cAyg9Q=.sha256
Re: %e3Dc8z56h

@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.

Join Scuttlebutt now