The image served by the forum is different (probably "optimised" or "sanitized" by Discourse or Cloudfront CDN) than the one uploaded.
A year ago, the images were intact. At least the small ones.
I've checked the old thread but images with blocks as EXIF data, are now distorted to the extent visible to the naked eye.
Huh, I see. That seems like a pretty recent change, though the feature still isn't as described. (which is optimization for only large enough files...) Well, I've turned that off, but png optimization was already off.
I am moderately confused by the pic returned by the forum is about 11K less than the one exported from Snap!, but it does seem to have metadata with it still. So, something is still processing the file...
I'm getting a CORS warning when I directly want to import this script pic from this page, so I need to download it first. Could we maybe make it so we CORS-allow our own site (s.b.e) to directly access scripts pics on the forum? That would be awesome!
Oddly enough, Chrome.v103@Win10 works for me, even for images served by "d1eo0ig0pi5tcs.cloudfront.net". The dragged images seems to be encoded as file object not the URL as expected.
The link to an image, with blocks embedded, served by a CORS proxy.
Edit.1 something goes wrong at first try. Now served by "allorigins".
Still not works for FF. Seems that browser must be instructed to "engage" CORS and force image re-download to overcome cache (crossOrigin='anonymous', procesdrop@morphic).
I just tested it in safari, and ios chrome (brave), and it works. If I recall correctly, it didn't yesterday.
Edit: nevermind. It's working fine for importing scripts, but it doesn't work for importing images. I guess the metadata isn't in the image itself?
Edit: nevermind again. Apparently scaled down images are on the domain https://cdn.forum.snap.berkeley.edu/ don't work. This one, however, is on the snap domain, so you (the snap team) can cors allow this.