Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

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..


The header " The Page With No Code " is in the html::before content property. The first paragraph "It all started when..." is in the body::before content. The second paragraph "This web page has..." is in the body::after content. And finally, the footnote "* Obviously there's some code somewhere..." is in the html::after content property.

I ran the decoded base64 string through a CSS beautifier; this might help: https://gist.github.com/ldjb/8c6b6d83f2acd3cef01fcf56b36d65f...


I found those in the inspector, sure. But I can't find them in the base64 encoded header.

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.


  curl -SsI https://danq.me/wp-content/no-code-webpage/ | \
    grep -i ^link: | \
    cut -d, -f2 | cut -d\> -f1 | \
    base64 -d
The Base64 encoding is invalid, or at least not ideal, as the '==' padding has been removed [1]. Restoring it works:

  (curl -SsI https://danq.me/wp-content/no-code-webpage/ | \
    grep -i ^link: | \
    cut -d, -f2 | cut -d\> -f1; echo '==') | \
    base64 -d
[1] https://gist.github.com/Dan-Q/fc308a8a4aca2934312939f92eaa9d...


> ... 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".


FYI browsers have built in functions for decoding base64, btoa() and atob(). Although I can never remember which is which.


Guessing from the names:

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


No-one uses these often, and you have a 50% of guessing right every time!


This other page has some more details

> 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 :^)




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: