zlacker

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.

>>ezequi+(OP)
It'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.

>>wizzwi+r
Ancient webserver that didn't serve the correct mime type for svg?

>>wizzwi+r
Only inlined SVG can have its elements styled by CSS.

>>london+N
Perhaps… 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.

>>bangon+P1
And 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...

>>ezequi+(OP)
Yeah, putting out obfuscated content while making a statement against client-side JS is very ??? to me