4 ms·
> The data length must be multiple of 32 bits. There is no padding mechanism in the encoder. Such padding mechanism should not be necessary, and the padding fr
by Aardwolf 7y ago
> The data length must be multiple of 32 bits. There is no padding mechanism in the encoder.
Such padding mechanism should not be necessary, and the padding from standard base64 is also not necessary. If you remove the ==='s you can still unambiguously decode it (despite the error some tools will give). URL-safe base64 (RFC 4648 §5) does not require padding and can represent any data length.