Finding the source in the header was obvious, but I can't figure how to decode that properly. I can see the rules for body{} and @keyframes{}, but no idea where all the text (the before/after rules) are hiding..
I ran the decoded base64 string through a CSS beautifier; this might help: https://gist.github.com/ldjb/8c6b6d83f2acd3cef01fcf56b36d65f...
Edit: Nevermind. I tried like 10 different online base64 decoders before, till I found one wich didn't show just garbage (maybe they all hiccup on the emojis?), but even that one didn't decode properly as it seems. Either the eleventh one now told me the whole truth, or I should've used curl -i from the start instead of copy/pasting from Firefox's developer tools.
You may toggle the "raw" switch in the upper-right corner, or Firefox will trim the header like "jh6…W5n".
curl -SsI https://danq.me/wp-content/no-code-webpage/ | \
grep -i ^link: | \
cut -d, -f2 | cut -d\> -f1 | \
base64 -d
(curl -SsI https://danq.me/wp-content/no-code-webpage/ | \
grep -i ^link: | \
cut -d, -f2 | cut -d\> -f1; echo '==') | \
base64 -d
btoa() should be base64 to ascii
atob() should be ascii to base64
Edit: it’s other way around, lolwut. https://developer.mozilla.org/en-US/docs/Web/API/atob
> The btoa() method creates a Base64-encoded ASCII string from a binary string (i.e., a string in which each character in the string is treated as a byte of binary data).
https://developer.mozilla.org/en-US/docs/Web/API/btoa
So the naming makes sense after all.
btoa() is binary to (base64 encoded) ascii.
But I’m still not gonna remember this either :^)