Of Course “changeme” Is Valid Base64 (2020)
susam.in
susam.in
Interestingly "change_me!" is no longer legal, but the decoder might drop illegal characters and decode it anyway...
We all start ignorant.
Interesting idea about the underscore, I'll try to keep that in mind.
Thanks for the put down though.
My hair had already started thinning at 16, though it's a slow process.
One day I'll replace my pattern of scalp growth with a permanent base 64 underscore, and then everyone will be happy.
I thought if you're older than 16 (even in their 40s like I am), being called 16 again could just amuse you. After all, it's not really relevant to my point.
My point is: we all start somewhere. Think twice before belittling the ignorant; either educate them or ignore them.
Where are you putting your self value if you belittle the ignorant while doing nothing to uplift them?
True about ignorance, if you asked me, I don't know how GZIP works (I skimmed through the explanation, it looked hard, I didn't bother with it further), although recently I learned how the JPEG compression works (with discrete cosine transformations), and yeah, to agree with you, that's more than 2 decades after I started tinkering with computers.
It's bad to think "I'll put 'changeme' here because that won't be valid base64", because instead of admitting you don't know how base64 works (and maybe spending 5 minutes to look it up or at least experiment with it), you've pretended you do know and written some nonsense code based on that false assumption.
The smartest people I know are some of the best at knowing when to say "I don't know".
Python’s infamously does that which can be a nasty surprise the first time you stumble upon it.
Validation of the input alphabet is opt-in (and somewhat recent), the default is stripping (probably originally for simplicity with respect to MIME) and will only error on padding check failure.
Somewhat oddly given the alphabet validation thing, the stdlib does not support unpadded base64 whether as input or output.
Unless you are using the "url-safe" variant (rfc 4648)
And the RFC explicitly says:
Implementations MUST reject the encoded data if it contains
characters outside the base alphabet