This JPEG is also a webpage
181–190 of 236 posts
Re: This JPEG is also a webpage
#182Re: This JPEG is also a webpage
#183Earlier quoted context omitted.
Maybe a product manager realized it didn't make sense to provide "essential squirrel facts" to a page featuring the image of a chipmunk. :-)
Author here. Rookie mistake! It's actually a golden-mantled ground squirrel. https://en.wikipedia.org/wiki/Golden-mantled_ground_squirrel A chipmunk would have a stripe going across the eye. (Today, you learned your first squirrel fact!)
I did learn something new, not just about squirrels but about chipmunks, too.
Thank you.
And here I was impressed merely by the delivery of image data in the HTML stream. Little did I realize your page is practically an Encyclopedia Rodentia.
Kudos and hats off.
Re: This JPEG is also a webpage
#184Earlier quoted context omitted.
XHTML failed because doing the old, broken, tag-soupy mess still worked exactly as well from the user perspective. You just can't get people to work harder for invisible benefits. In a sense, it's a reason, but it doesn't mean that tag soup is a good thing. I often wonder how different the internet would be if Postel's prescription never gained traction and fail-fast behavior were the norm instead.
Also because all of the tooling was terrible and extensibility was non-existent. It's easy to imagine a world where XHTML worked out better because the browsers provided clear, informative errors rather than a blank page, someone at the W3C cared enough to have a usable validator which produced helpful warnings and errors, and attention was paid to the less friendly bits of the XML ecosystem[1]. Instead, it felt like…
Writing proper XML tools is very difficult. XMLs are usually parsed without considering the dtd. It seems the dtds are just for humans to read. As you mention, XML becomes more interesting with extensibility. IMHO XSLT is the key technology for that but unfortunately there is no reasonable support for XSLT 2 because the standard is just too complex. And XSLT 1 is barely interesting to use.
By the way, there's SLAX, it's isomorphic to XSLT but with nicer syntax. Nice approach but anyways, the standards are horribly complex and stiff.
Re: This JPEG is also a webpage
#185Earlier quoted context omitted.
If it had been made as difficult as possible for enthusiasts learning a markup language to get what was essentially text document to actually display anything, it's probably not too much of an exaggeration to say the World Wide Web wouldn't have existed in its current form. It's not as if many of the web's security holes are related to whether a page displays valid HTML markup or not.
That's exactly my point. Low barrier to entry allowed the web to explode.
Or the web was ready to explode anyway, and requiring a bit more strictness would not have significantly hampered its adoption.
Re: This JPEG is also a webpage
#186I abused this concept to compress demo code in PNG files, with great success. http://demoseen.com/blog/2011-08-31_Superpacking_JS_Demos.ht... This is, at present, the most efficient way to pack demos on the web; a few characters of uncompressed bootstrap code, then the rest is deflated.
My democrew (Ninjadev) has used this technique for multiple WebGL/Javascript productions over the last few years now. You can see the final packed .PNG results here: Crankwork Steamfist https://stianj.com/crankwork-steamfist/ , Everything is Fashion https://stianj.com/fashion/ , and Inakuwa Oasis http://arkt.is/inakuwa-oasis/ . The tool used for creating both the demos and the packed .PNG is made by us and available…
Oh man, I didn't know you guys released your tools. I'm a big fan of your stuff -- awesome to see such polished prods on the web. Happy to have helped enable some amazing work!
Re: This JPEG is also a webpage
#187Can I upload such image for instance to facebook and intent to run it as html (with some JS inside)?
Re: This JPEG is also a webpage
#188Can I upload such image for instance to facebook and intent to run it as html (with some JS inside)?
They usually set the content type to that of an image so the browser won't execute the JS.
They've messed this up in the past, see this legendary bug bounty report [1]
1. https://whitton.io/articles/xss-on-facebook-via-png-content-...
Re: This JPEG is also a webpage
#189Interestingly, this page is intercepted by my router which then just sends me a redirect to one of its settings pages. Odd.
Another reason to use https, if you don't want routers filtering your website's content.
Re: This JPEG is also a webpage
#190I'm a big fan of Ange Albertini's work with this kind of stuff - https://github.com/corkami/
There's a talk called "Funky File Formats" but there's (fittingly) multiple versions of it so you're best off searching for it.