like with the other exif stripping feature request, another thing to look out for again is color profile information (maybe image rotation too…?). A lot of applications that generate thumbnails (e.g. slack, discordapp, etc.) will discard this data, so you get pictures that look very different in thumbnail form and when expanded. (this is a pet peeve of mine. discordapp in particular never even shows you an un-thumbnailed version in the desktop app, so everyone except mobile users will see distorted colors unless you manually convert to srgb before uploading. but if you do that then you lose all the extra color gamut…)
(though, like, generally, given cohost’s support for more unusual image formats like heif and avif, which support hdr color, this may actually be kinda difficult…)
Yes please! I'm on a prepaid plan and cohost eats up so much data.
Really need this. The site now has more users, it takes forever to load up a page with dozen of images.
I would like to add that, for those who have to pay for data transfer, it would be a great benefit for them to be able to see what the full size image's actual filesize is as an indicator of some sort.
I'm not sure of a good UX for it besides just, like, putting it as a little box in the corner of each thumbnail, which I don't think most users would want to see by default, so I think that making this indicator be optional, something you can enable in your settings, would be great.
To take it a step further, since opt-ins are hard to socialize if they're for niche use cases, I think that if a user is new, then the first time they come across a large file, a modal or tooltip should pop up to tell them that if they want, they can enable the indicator. That will ensure that for most users they only need to dismiss something once and never think about it again, but for people who have to pay for data, they'll be much more likely to notice and use the feature, all while preserving a default experience that doesn't have indicators that could potentially make the visual appeal of the site decrease a bit.
Currently, every post containing images on Cohost features the full-sized image, used for both the scaled-down preview (dimensions: 260x197 on my computer) and the scaled-up version in the lightbox.
This means that, in the extreme case, I could embed four ten-megabyte images, and someone scrolling past my post would have to load forty megabytes of data. I use Google Fi and it would cost me forty cents just to scroll past that post on the bus. This presents similar issues for people in developing countries who may have slower, less reliable, or similarly expensive Internet connections.
As a photographer I am pleased that Cohost doesn't recompress my images for full-size display, but other than perceptually instant full-size images (since they're preloaded), I don't see any benefits for users of using the entire full-size image as the thumbnail. Serving thumbnails until an image is expanded would presumably also save a tremendous amount of bandwidth on Cohost's side.
A pixel artist might have an edge case here, but this could be handled with an on-by-default checkbox, or clearly-documented heuristics on what to always serve full-size (pixel dimensions, format, filesize, etc).
21 people like this idea