vogon

the evil "Website Boy"

member of @staff, lapsed linguist and drummer, electronics hobbyist

zip's bf

no supervisor but ludd means the threads any good


twitter (inactive)
twitter.com/vogon
bluesky
if bluesky has a million haters I am one of them, if bluesky has one hater that's me, if bluesky has no haters then I am no more on the earth (more details: https://cohost.org/vogon/post/1845751-bonus-pure-speculati)
irl
seattle, WA
You must log in to comment.

in reply to @ticky's post:

I tested and I got PNG for both the MIME and the file on both files so either that was a typo or something REAL weird is happening with browser detection

But this raises the question of what process lead to the creation of a 3072x3072 PNG created by starting with another PNG, shrinking it and then blowing it up again?!

I guess Safari is explicitly advertising JP2 support?

In any case, it seems that they’re based on high resolution originals (you can delete a portion of the final image URL to get the full res original), the final image is asked to shrink to the proper size, but the placeholder is not assigned a proper size, so it has a pixelated effect applied but is not actually shrunk