You are reading content from Scuttlebutt
@aljoscha %O8aEFQ3FJQir6ogLs5KA/+BDM+NnceR3eIbzXnlCBEA=.sha256
Re: %ZBzVJhKOY

Dev Diary 06/10/2018

(Not a full day of work)

  • Fun, so much fun! %ZOosXgU...
  • Aside from the two blocking issues on the js side of things (utf8 decoding and object entry order), the rust implementation of json legacy message content is now fully functional and passes the couple of thousand test cases the fuzzer generated.

Next up:

  • bother @Dominic until utf8 decoding and object entry order are resolved in js ssb
    • optional subgoal: create js bindings to the rust json codec for usage by js ssb, if so desired (warning: AGPL code, but I might be willing to relicense it if that helps js ssb to do order-preserving json decoding in rpcs)
  • publish the test data (depends on how utf8 decoding and object entry order get resolved)
  • implement the cbor encoding of legacy message data

I'll do the cleanup, thorough documentation , and actual releases, once both json and cbor legacy message data are fully specified and implemented. I'll tackle legacy metadata afterwards. And when that is done, it's time for #hsdt

Join Scuttlebutt now