Here's another thing I like about PASETO: because it's versioned, communicating about insecurities found further down the line is much easier. With JWT you hav

Here's another thing I like about PASETO: because it's versioned, communicating about insecurities found further down the line is much easier. With JWT you have to say stuff like "ensure that alg can't be 'none' and that your JWT library doesn't accept arbitrary alg fields". This is messy. With PASETO you can just say "be sure to use v3 or later" (assuming someone finds a flaw in v2, files that issue, and that is then addressed in a v3 of the spec). Similarly, implementations can just write "supports versions 1 through 3" on their README.