Brannon Dorsey

Alrighty, I hear y'alls requests and have made a public key registry on GitHub at [brannondorsey/chattervox-keys](https://github.com/brannondorsey/chattervox-keys). Would love it if y'all would go through the motions of adding your keys...

@jedahan I'm glad to hear you got things up and running on MacOS. I assumed this would be possible but haven't mentioned as much in the documentation yet given that...

@jedahan re: meeting up & doing a workshop, absolutely yes to both! I'm a huge fan of SFPC and Recurse as well and would jump at the opportunity to lead...

That's an interesting idea, but it doesn't work in this case as the signatures generated via [elliptic.js](https://github.com/indutny/elliptic/) are deterministic. ```javascript const EC = require('elliptic').ec; const ec = new EC('p192'); const...

I would have to agree. I favor a solution that doesn't require a reliable connection. Consider a scenario where a station broadcasts a weather beacon each hour. The protocol should...

Right on :balloon: > My suggestion is to include the previous ("deepest") message in the message body and sign that. A sequence of messages will build up and if a...

I'm leaning towards implementing this in the next version of the Chattervox protocol. Any objections or comments? Specifically, I'm planning on including the timestamp field as a 32-bit unsigned integer...

Very excited to see discussion around this topic! I think a solution for preventing replay attacks is a must with the next update of the protocol and I'd love to...

I've opened an RFC to include a timestamp in the chattervox protocol https://github.com/brannondorsey/chattervox/issues/19.

It appears that multi-line messages aren't handled well on the receiving end either, as the user's prompt is not redrawn after receipt.