Not Important

owls-parliament:

insufficientlyadvanced:

what a good example for a race condition

this is why I lock my fridge before going shopping

Wait a second, why is the trip home-shop 10 minutes but shop-home only 5? Is the shop uphill?

Testing something again, if this shows up on your dash it’s probably going to be a broken image

http://s3.amazonaws.com/data.tumblr.com/f802c9315254b84447a7d4a71d7e0139/tumblr_mihxi8d0nJ1qj0qtoo1_100.png

http://s3.amazonaws.com/data.tumblr.com/aecc62099f868b885960bb4c672f4682/tumblr_mihxi8d0nJ1qj0qtoo1_r1_100.png

Oh hey, turns out it was just tumblr shitting itself

OH WELL

1st: http://25.media.tumblr.com/f83669c9d51950d022da60859f1a010f/tumblr_mi41d10hWd1qj0qtoo1_1280.jpg

Testing JPG Compression - The original image is a 4.887.524 byte 5000x5000 JPG, 4:4:4  Q100 / Floating Point DCT / Progressive / Optimized / Restart Markers (You know, i really needed that extra 500 kb)

Result: The image was (as expected) reduced to 1280x1280, the subsampling was preserved but the DCT switched from progressive to baseline. The filesize was reduced to 434.550 byte

2nd: http://24.media.tumblr.com/c955f40ea32c6cf7a8b3e032559d0b9a/tumblr_mi41d10hWd1qj0qtoo1_r1_1280.jpg

Testing JPG Compression - The original image is a 4.465.961 byte 1280x1280 JPG, 4:4:4  Q100 / Floating Point DCT / Progressive / Optimized / Restart Markers

Result: All the parameters preserved, Including Progressive DCT and filesize (4.465.961 byte)

-

-

So what? Well, for starter every image that does not fit the _1280 container (width over 1280 pixels, height over 1960 [iirc] pixels) is automatically converted to JPG with baseline DCT and (if a subsample isn’t specified, as with non-jpg files) 4:2:2 chroma subsampling.

So don’t give tumblr images too big or it’ll wreck it into a mess of artifacts. Doesn’t matter the size in bytes, but the actual width and height. If you must, resize it yourself or cut it down in smaller images and upload them separately in the same photoset (former is better for large JPG or GIF, latter is better for PNG files)

or, you know, upload them somewhere else. You can then link them in your tumblr. A lot of people do that.

[ Except Zerochan. Don’t use Zerochan ever. Ever ]

Testing something

1st: http://25.media.tumblr.com/84c18531675f0976019560df13e66be9/tumblr_mi1qzrGiFE1qj0qtoo1_1280.png

2nd: http://25.media.tumblr.com/a2958b9a0e2f10df60e00e41a4af79d1/tumblr_mi1qzrGiFE1qj0qtoo1_r1_500.png

3rd: http://24.media.tumblr.com/a8a5ae61bab572333fb46690ceb9ad67/tumblr_mi1qzrGiFE1qj0qtoo1_r2_1280.png

2nd and 3rd one have been re-encoded as a shitty jpeg because they’re “big png files”. They’re both uncompressed PNGs, 2nd is 1.43 mb 3rd is 4.17 mb

4th: http://24.media.tumblr.com/cd11fd3cba63a549e08cbf3ccfce51db/tumblr_mi1qzrGiFE1qj0qtoo1_r3_500.png

5th: http://25.media.tumblr.com/6c2600b9acc9501527a8d1da8c877585/tumblr_mi1qzrGiFE1qj0qtoo1_r4_1280.png

4th and 5th are the EXACT SAME IMAGES of the 2nd and 3rd, but compressed. They have been correctly put up as lossless PNGs. 4th is 570 bytes, 5th is 300 kb

The current image system is a fucking mess. Beside i can upload anything without tumblr noticing because the /image/[post number] thing only shows the most recent revision (r[n]) so anyone could edit the image and keep the links in the post, like i did right here (This is a fucking necessity NOW, before all revision could be accessed easily and the tumblr filename was the only thing needed to access any image on the AWS). Tumblr support can’t apparently access those without knowning the hash either. How convenient.

I am now wondering if “big jpg files” are also re-encoded. If you can’t handle the bandwidth necessary to serve out big images don’t set the maximum filesize to 10mb just to smear shit all over people’s uploaded images.

“It looks like our last response never got to you - Could you clarify what you are trying to do that you used to be able, which the new hashing system (used to combat spam) prevents you from doing any longer?”

Real smooth tumblr

Reeeeal smooth