piegames

The problem with ProtoBuf is that it does not have first-class support for self-describing messages: https://developers.google.com/protocol-buffers/docs/techniques#self-description msgpack is conceptually a drop-in replacement from JSON, whereas trying to use ProtoBuf would...

I did a quick code dive and found some answers too: - All error messages I could find are some kind of protocol errors. I don't know how IO errors...

So the most important question is: "should we restrict `error` messages to be in direct reply to client messages?". If yes: - This will simplify some things on the client...

I just noticed that this has implications for our new permissions system too: what does it actually mean for the server to "error out"? - We could say that there...

I propose the following changes and clarifications to the spec: 1. Error messages that contain the `orig` field are in direct response to some other message, those that don't happened...

> Given this, it might make more sense to spec particular responses to any message-types that currently lack an explicit response (where the client needs to make some sort of...

Which people with which disabilities and what changes in the protocol?

Some thoughts about the UX: - Every client generates a UUID and also a human-readable username - Connections between clients that support Wormhole Seeds will exchange their IDs and other...

Working on this again, and some design questions coming up: - Should the clients store a *nameplate* or a *mailbox* to find each other? - If the latter, how does...

Thank you for the input. I noticed that handling identifiers is more tricky than I initially thought: since anybody can take anyone's UUID, there still be some collision handling required....