The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
I attached and posted a PNG image that was 424Kb png.
On my phone's file manager, it shows as 424Kb. (Android 5.1.1). In the post footer where it shows an attached image, it shows as 424k. When I sync it using Google Drive to a WIndows 7 computer, it still shows as 424kb.
However, I received feedback from other forumers that this file was over the size limit. Trace said it was 8Mb.
When I right-click on the image link in the Vanilla post, it downloads as a 7.92Mb png. The filename is different, too.
They're both 1920x1080px pngs, so I don't know what the difference is.
every person who doesn't like an acquired taste always seems to think everyone who likes it is faking it. it should be an official fallacy.
My gut feeling is that there's some compression algorithm in the original file that gets stripped after it's uploaded to Vanilla and attached in a post, but I have no direct evidence to support that.
every person who doesn't like an acquired taste always seems to think everyone who likes it is faking it. it should be an official fallacy.
Interestingly, 7.9x MB is the same exact size as a 1920x1080 32 bit .tga file with RLE off. Something's up with whatever backend saving/conversion is going on, images are being stored and served completely uncompressed.
Looks like there might be some 'processing' involved in handling image uploads if they're larger in dimensions. That might actually be stripping compression and other metadata/config/etc out of these pngs.
I wonder if it happens with pngs that are less than 1000px wide/tall ? Not sure what the exact cut off is.
not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
We re-encode all images that get uploaded in order to get rid of any injected exploits. We'd had trouble with larger images (20000px x 20000px) uploads causing thrashing on app servers, hence the conditional handling. I don't think stripping compression was intended.
Posts
the "no true scotch man" fallacy.
http://ge.tt/6Xy6hrY2
the "no true scotch man" fallacy.
time to dust off le olde NIX site I guess
http://feral.chaosnet.org/odd/Screenshot_2016-03-14-17-27-12.png
the "no true scotch man" fallacy.
compression changes would though, per pngcheck:
The compression level changed from "default" to "superfast", resulting in a change from 93% compression to -0.2% compression.
Yikes!
http://forums.penny-arcade.com/discussion/comment/34760728#Comment_34760728
Looks like there might be some 'processing' involved in handling image uploads if they're larger in dimensions. That might actually be stripping compression and other metadata/config/etc out of these pngs.
I wonder if it happens with pngs that are less than 1000px wide/tall ? Not sure what the exact cut off is.
Test