Closed csuwildcat closed 3 years ago
I'm dealing with versions of this everywhere thanks to the popularity of base58btc now, and the popularity of base64url before..... IMO, it totally sucks to have an API that requires both, so we should pick one...
Since IPFS and DID Core are newer and use base58btc... I suggest we just use that, and say fairwell to old and sad base64url without padding....
All in favor of base58btc anywhere we can?
I'm in favor of base58btc where we can ... but I'm not sure we can eliminate base64url everywhere... certainly not from other specs that we depend on/use (same applies in reverse); so I don't expect implementations to be able to get away with implementing just one.
of course we can't change JOSE, but we can choose to never use base64url again.
Per nudge from @OR13, we should probably decide on an encoding to use across the spec.