3 ms·
Any guesses as to why the source code look the way it does? I was expecting a traditional website inside the noscript tags, but instead I found an obfuscated so
by ezequiel-garzon 6y ago
Any guesses as to why the source code look the way it does? I was expecting a traditional website inside the noscript tags, but instead I found an obfuscated soup letter between them.
- wizzwizz4 6y agoIt's an inline SVG image. That alphanumeric soup is the coordinates of the points (and handles) of a line. Scroll past that, and you get the website. I have no idea why they made the SVG image inline but the CSS style external, though. That same image is used on every page.
- londons_explore 6y agoAncient webserver that didn't serve the correct mime type for svg?
- wizzwizz4 6y agoPerhaps… but calling the SVG a `.png` and transcluding it into a smaller inline SVG file would still have worked in the vast majority of browsers.
- bangonkeyboard 6y agoOnly inlined SVG can have its elements styled by CSS.
- mr_toad 6y agoAnd in-line SVG can have it’s DOM modified, allowing the image to be interactive. Of course, you’d need to have JavaScript enabled to do that...
- reanimus 6y agoYeah, putting out obfuscated content while making a statement against client-side JS is very ??? to me