varanauskas

OpenAPI uses JSONSchema to define object (e.g. request, response body) schemas, so it would be more accurate to say it:

Extracts the JSONSchema based on path+method+response type from OpenAPI and then converts that to typescript

I’m trying to achieve generator-less mapping from OpenAPI to Typescript types at https://github.com/varanauskas/oatx

For those wanting to infer Typescript types from JSONSchema itself there is: https://github.com/lbguilherme/as-typed

AFAIK according the draft HTTP request signing rfc [1] defines explicit instructions for normalising, serialising and signing HTTP headers (not body). However, you can use an HTTP Digest header for example, that is a hash of the plaintext body to authenticate the body

[1] https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-mes...

Just to add to this restaurant based allegory, Spotify is like an all you can eat buffet that tries to serve out lots of sodas so you get bloated and don’t eat the expensive stuff they have

String addition = concatenation

String subtraction = ??? => Number subtraction

Still I think 2 way calls would benefit customers by reducing lag and Apple by reducing server load if using p2p

I recently did a write up [1] of the Lithuanian vaccine certificate after finding a flaw on it.

What impressed me was that the verification was done fully offline in a privacy preserving way

[1] https://tadas.varanauskas.lt/posts/forging-lithuanian-vaccin...