for example, this image:
gets reconstructed to this:
uh oh.
If you use a Pixel phone and you've posted screenshots on cohost: you should check them to make sure nothing's getting leaked from them. cohost is one of the only social media sites that doesn't recompress your images, which means it's possible for something to have gotten leaked via this bug. Same deal with Discord.
Wait, this is a surprise? The cropping tool outright tells you that "you can always undo these changes" if you Save instead of Save as Copy.
That is not how it’s supposed to implement that haha. For comparison, Apple Photos stores the original and the edits, but if you export from the library (share photo, etc) the edits are baked in irreversibly.
thats also how google handled it, but they fucked up and accidentally included parts of the image in the "cleaned" vresion
i sure am glad i crop naked me out of a whole bunch of otherwise benign things 🙃
It's starting to get kinda suspicious that the pixel security update is taking so long to come out this month, usually it's within the first week of the month but we're in week 3, with a ton of disclosures happening, and nothing
how the fuck does one screw up IN THIS WAY of all the ways. how do you not notice the files NOT BECOMING SMALLER i-
oh, if twitter recompresses even the PNGs then I don't have to delete every tweet since 2018, so that's good at least. I should probably still check that that gets rid of enough data, but. at least theres that.
Looking it up, apparently Twitter preserves PNGs under 900x900 - probably not likely to be screenshots, but they could be. I was under the impression it only preserved 256 colour PNGs, which is really unlikely for Android screenshots. https://twitter.com/NolanOBrien/status/1281639467992748032
it looks like they still get reconverted, none of my screenshots are popping up as having extra data, but other people shouldn't take this as evidence since i've only checked 8
