SSB Log Entry 753

Pigeon Protocol Daily Update, June 5th 2020

Note to folks just tuning in: I do daily updates related to #pigeon-protocol - a project with similar goals to SSB.

Done

I am (finally) done renaming sigils.

The new messages look like this:

``` author USER.XE50J6A292KXRT1TRPR3DGQKTASDD9WMKGVQM5RFX9N06T7YAR7G depth 12 kind example-entry lipmaa TEXT.J59CT9PW3FHR4BQAHAE5M4EMBDCRWW03FBBYN7M3114QMC1YDTMG prev TEXT.HBX5PHVGKKQ3NVPSVD2HMESYVNR3YWKWXNAG4XG0MCFPB04VW40G

example-string:"596c18e0-b1d6-47ba-9f61-d330f7b9228e" just-a-blob-i-guess:FILE.ET9C7B9N82XR0F021CXEWSPDH23H4CHMX866WWA3R2PXEFZM67PG my_friend:USER.DD9WMKGVQM5RFX9N06T7YAR7GSATKQGD3RPRT1TRXK292A6J05EX FILE.7Z2CSZKMB1RE5G6SKXRZ63ZGCNP8VVEM3K0XFMYKETRDQSM5WBSG:"want"

signature XVP9R…(redacted)…S8E08 ```

TODO

Now that the message format has been adequately tidied, I really need to focus on the sharable parts of the project.

Go back to writing documentation.
Publish the Rubygem.
Write an implementation in Go that will serve as the "most official implementation". Ruby was great for trying out ideas, but it is not very portable and I've had trouble sharing Ruby code with non-Rubyists in the past. More people would be able to try stuff out if static binaries are available and Go will make that easy while not getting me too bogged down in things like memory management or learning what a borrow checker is.