00:19 <isd> Some unsolicited feedback about the usability of the websession API: It's really obnoxious. It's a dramatically large amount of work to wrap it into something that I can present to a web app that expects a standard-ish interface (in this case Go's net/http, but same would apply to python's wsgi or even cgi and such).

00:21 <isd> In particular, the the way that it encodes so much information about specific status codes, methods, etc. means that I have to handle all those different cases separately.

00:23 <isd> The way I would implement this would be to just take (status, headers, body) and do the appropriate filtering on the other side of the connection (documenting what's done). The downside is capnp isn't doing the checks for you, but IMO it's worth it for how much easier it would make talking to the thing.