scuttlebutt-protocol-guide
scuttlebutt-protocol-guide copied to clipboard
ssbc
Protocol documentation for Secure Scuttlebutt
I noticed an interesting behaviour exhibited by Patchwork. When receiving `createHistoryStream` requests for sequence `n` patchwork returns messages with `sequence >= n`. The protocol guide seems to imply that this...
From the guide: > A Bendy Butt Message is a Bencoded list containing a collection with the following five elements, in this specific order. > 32-bit integer representing the time...
Soapdog wrote some really night documentation for commons ssb message schemas as part of patchfox. I keep searching for message schema examples and find them hard to find. So i'm...
I found a problem while implementing the "4. Server accepts" section on the documentation when computing `detached_signature_B` . I think there is something wrong in the documentation. To my understanding,...
According to https://ssbc.github.io/scuttlebutt-protocol-guide/#fetching a valid argument for `blobs.get` would be {"hash":"&KYWW5Lblhq2moFO9BJhtJ5WukFRpA7eYybOwdODTt3M=.sha256","max":5242880} However, the reference implementation is sending {"key":"&KYWW5Lblhq2moFO9BJhtJ5WukFRpA7eYybOwdODTt3M=.sha256","max":5242880} see: https://github.com/ssbc/ssb-blobs/commit/c3943338d6ee8b756d75a18e7350147aa0bf212f
In a side-note in the [want and have](https://ssbc.github.io/scuttlebutt-protocol-guide/#want-and-have) section, the Protocol Guide says that only one blob is allowed per response to a `blobs.createWants`. I see no reason for this...
According to [RFC8259](https://datatracker.ietf.org/doc/html/rfc8259) specifying the JavaScript Object Notation (JSON) Data Interchange Format: > An object is an unordered collection of zero or more name/value pairs, where a name is a...
Context: https://github.com/ssbc/ssb-classic/pull/2
Heyo Figured I'd open up a discussion about the protocol documentation's [current section on metafeeds](https://ssbc.github.io/scuttlebutt-protocol-guide/#metafeeds). How do people feel, should it remain part of the protocol docs when considering its...
