You are reading content from Scuttlebutt
User has not chosen to be hosted publicly
User has chosen not to be hosted publicly
User has chosen not to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@Anders %gSVs0yJt7HmjnGEe/ec31YEgF/BPlBGMz+I0aoUKb/c=.sha256
Re: %VcB0Bt+MY

Another idea is a project I was made aware of yesterday called zenroom where the crypto could be specified in language neutral wm and be shared between the different implementations. This does not mean that we don't need tests, just that the really tricky crypto stuff can be written once.

User has not chosen to be hosted publicly
@Dominic %KU9dJrtgvUR0yi3lBf0FyB5JTtUS5XcDs+732pmiIzw=.sha256
Re: %VcB0Bt+MY

We don't really need to make the cli authorative, whats more important is to make the RPC the authoritive thing. However, the CLI is just a muxrpc client - and there are already more than one cli, node.js's and @cel's sbotc.

So we could run the tests using one server and a different client. Implementing a client covers muxrpc, shs, box-stream, so you are making some good headway to get to that point.

I think the next step is getting at least something from the various clients passing the test. Like, if they can just answer whoami that's something.

User has not chosen to be hosted publicly

Show whole feed
Join Scuttlebutt now