Skip to content
Permalink
Browse files

Slightly flesh out the section on my work (#3)

  • Loading branch information...
AljoschaMeyer authored and ahdinosaur committed May 20, 2019
1 parent 605fb46 commit 35489bf20193a6ab819aa178cf92a1476d700668
Showing with 5 additions and 4 deletions.
  1. +5 −4 newsletters/2019-02-01.md
@@ -45,11 +45,11 @@ This was all well and good, the bindings to `ssb-legacy-message` work, but they'

### Aljoscha: A Well-Specified Scuttlebutt

Aljoshca spent time writing specifications: [spec.scuttlebutt.nz](https://spec.scuttlebutt.nz)
Aljoscha spent time writing specifications ([spec.scuttlebutt.nz](https://spec.scuttlebutt.nz)) as well as implementing them in rust.

He did valuable work [fuzzing](https://en.wikipedia.org/wiki/Fuzzing) the current implementation and found a lot of edge-cases.
He did valuable work [fuzzing](https://en.wikipedia.org/wiki/Fuzzing) the current implementation and found a lot of edge-cases, prompting a couple of fixes in the reference javascript implementation.

Highlights From his [wrap up post](https://viewer.scuttlebot.io/%25VKuA6aX1KMx2azGYcDGOs0jfl9XiJRh95SRYbJWE%2F2w%3D.sha256):
Highlights from his [wrap up post](https://viewer.scuttlebot.io/%25VKuA6aX1KMx2azGYcDGOs0jfl9XiJRh95SRYbJWE%2F2w%3D.sha256):

> In general, I produced four different kinds of outputs:
>
@@ -58,7 +58,7 @@ Highlights From his [wrap up post](https://viewer.scuttlebot.io/%25VKuA6aX1KMx2a
> - test data sets
> - long discussions
>
> The first big block of work was about cleanly defining the message format that is currently used by ssb. There is a full specification of the format here (repo). If it contradicts the protocol guide, chances are the specification is right and the protocol guide is wrong - I've done some pretty thorough fuzz-testing (more on that later).
> The first big block of work was about cleanly defining the message format that is currently used by ssb. There is a full specification of the format [here](https://spec.scuttlebutt.nz/) ([repo](https://github.com/sunrise-choir/spec)). If it contradicts the protocol guide, chances are the specification is right and the protocol guide is wrong - I've done some pretty thorough fuzz-testing (more on that later).
>
> The spec is composed of three parts:
>
@@ -85,6 +85,7 @@ Highlights From his [wrap up post](https://viewer.scuttlebot.io/%25VKuA6aX1KMx2a
>
> I did a write-up on Merkle trees applied to ssb. There's some pretty good information on the topic in the discussion it triggered, but the overall result was that we can't simply throw Merkle trees at ssb to completely solve the problem of verification for partial feeds.
Aljoscha dropped the full-time work in the sunrise choir for personal reasons, but continues to be excited about the raw potential of ssb. He is however deeply traumatized by the json intricacies of float encoding and string escapes, and hopes his work will protect future developers from suffering the same fate.

### Piet: A Big Bite of Rust: Flume Follower and SQL View

0 comments on commit 35489bf

Please sign in to comment.
You can’t perform that action at this time.