2018-12-04

had a bad time getting patchbay installers working. was meant to be a quick build test of scuttle-shell, but didn't get anywhere near. needed work for being able to build isntallers for new version of dark-crystal, but not fun.

2018-12-05

started into a refactor which will hopefully allow for more comprehensive testing of version support for all the shard and replyies etc.

2018-12-06

swapped in fetch+mend for recombine and watched it work. fixed some minor bugs that it hadn't caught but all tests passing. feeling a little insecure about how much work it's taken and waiting to see if it's a net win payoff. I'm hoping some of the investment will come into its own with things like ephemeral keys.

it's certainly helped clarify requirements for me. e.g. we need versions on reply messages like :

• version - the layout of the message (as dictated by invite-reply)
• shardVersion - what is the content I'm receiving
• replyVersion - what sort of reply is it. Is that that shard with shardVersion X just unboxed and bare (like our v1 replies) or is it an ephemeral return I should by trying to unbox with some ephemeral key.

I think @peg was gonna have a look into some of that? (or at least we talked about these ideas). I'm not sure what the ideal solution is or if there's a clearer place all of this info should exist. Maybe it should be referrer to in the request (invite) message ... but it would be nice for there to be a symmetry between forwarded messages and reply messages (IMO)