Preview vs Source - Image display

[SaySayTakamura]

Is your feature request related to a problem? Please describe.

One thing that i have seen around here is people chatting about the Image Compression/Rescale issue (#1101), and out of the loop i have seen some people complaining about this as well.

And i came here to suggest something i saw on Twitter quite the time ago.

Describe the solution you'd like

When i used to gather references for my Studies i would check and download some pics from Twitter, but when i saved the image from directly from the post (preview)(right click when hover the post's image) it would save an horrible and compressed version of the image which for me was a no-go, then i found out you could save from the full-image page (clicking on the image to open it and then saving it using right click), this solved my issue all images downloaded using that method where in their true-size and with their respective file format.

Which means we have images in two modes:

• Preview Mode
• Source Mode

Preview mode is the mode that all posts display on the feed and Source mode is a link to the original file.

I saw on the mentioned issue that you guys cache the upscaled version if the original file overrides the maximum size limit.

You guys could allow the user how that works: Give them an option if the image displayed on the feed is resized to avoid high memory/storage and network usage or if they would like to keep seeing full-res images, by default would be a compressed version of the image.

When the user actually opens the image it loads the original image from the reference on the metadata(this is not affected by the option mentioned above, except for videos which is a different option).

Note: for videos the behaviour would be the same, but the options would be the resolution the video would be displayed, one option for feed (preview) and one for the full (Display)

This would be the metadata in question

   {
     previewImage: "C:/path/to/the/image.format" //Stored locally(cached) on user's machine, compressed on save.
     displayImage: "https://bsky.app/source/link-to-the-originally-uploaded-image.format" //Stored on Bluesky Servers, uncompressed and untouched.
   }

Of course both of those would be NULL in case it's a Text Post.

Additional context

I am opening this issue since i noticed even Pixel Arts are blurry to see, most of those are PNGs.

I will end with a question, you guys plan to remove the 2000*2000 image limit or is it a permanent thing?

Well sorry for the bothering yet again, i think this is the last issue for now, hope this is useful for someone else and thanks for your time and for reading.

[gaearon]

We're planning to fix the upscaling (that isn't supposed to be happening) soon.

[SaySayTakamura]

We're planning to fix the upscaling (that isn't supposed to be happening) soon.

Great to hear that, sorry for the bothering and thanks for the response

[coredumperror]

We're planning to fix the upscaling (that isn't supposed to be happening) soon.

This was said 7 months ago. Did you ever get around to fixing it? Or adding some other way to retrieve the originally uploaded image?