ok, i get the idea that they should be treated as opaque structures and delegated to SuperTokens for parsing/validation. however, i'm currently looking into using SuperTokens in a C# environment that doesn't yet have an official SDK, and, as such, i'm looking at needing to parse and validate the JWT. there are existing, well-tested libraries that parse and validate JWTs. however, i'm running into problems using them with SuperTokens out of the box. RFC 7519 calls for base64url encoding, but SuperTokens appears to be using the regular base64 encoding. and with respect to the claims, i'll need to recreate all of the validation routines due to the custom claim names. from the RFC: > they provide a starting point for a set of useful, interoperable claims i just find it curious that you decided to explicitly not use RFC 7519 with base64url encoding and the well-known, interoperable claim names.