Maybe it's me, but it seems like lately I've been seeing a lot more huge photos being posted in threads. Not just the threads that are just about pictures, but ordinary conversation threads. They're so large, i.e. wide, that they exceed my browser width. Since text wrapping adjusts with the widest size, it means I end up having to scroll sideways just to read posts. Good example here: Where Should the Load Go. That one big photo fucks up everything else for me. I was wondering if it's possible to set it up so that oversize photos automatically scale down to fit screen width, rather than the other way around? If not, perhaps oversize photos could be forced-scaled to a pre-set maximum size (e.g. 80 hex 600), and the user could click on the photo to see it in "full" size? Maybe it's just me. But I'm guessing if I'm annoyed by it, others also are.
I have suggested something like this before, I can't find the thread right now but I do seem to remember that Drew either said it would be a lot of work or that he didn't have the time (or both). Ideally, photos would automatically scale (down, not up) to the width of the table the posts are in, which in turn scales according to the browser window size. But that would require some sort of script which would have to run and I'm sure those are expensive or complicated or something of that sort since in fact I haven't seen them in use in many places. To "future proof" ADT regarding images it would be great however, since we could upload images with high resolution and then have them automatically fit the browser window, or even configure display size ourselves (with an option to expand for those interested). Right now it can be a bit of a pain to figure out which resolution to scale images to before uploading. You might want one to display as big as possible in one thread, while in another you might want it to be smaller to fit along with a series of photos, and etc...
When you see a large image in a post it's because someone uploaded a photo that's typically print-quality instead of web quality. 300+ DPI vs 72 DPI. Our image uploader script is written to ensure it can't consume too much memory on the server manipulating images. So these huge images are ones the script exited due to too much memory being consumed. I should change it so it just deletes the image off of our server instead. As for auto-resizing, that's not going to happen for lots of reasons all of which are technical and not economic. Sites standardize on a certain number of image sizes for many reasons, the primary being that it's much faster for a browser to render a page when it knows the size of the placeholder for an image. A browser first fetches the HTML page and that HTML tells the browser which images it also needs to get from the server. If the HTML tells the browser the height and width of the image it allows the browser to start building the page right away instead of waiting to figure out the size of the image after it's fetched from the server. Sure, images can be resized in script but that typically means delays in page loading times and transmitting lots of extra data from the server to your browser. It's a huge waste of bandwidth.
If you restrict the img width attribute to, say, 800 then adjust the height attribute proportionately, the browser will take care of resizing the image and still be able to layout the page before the image is loaded. I don't think this would affect the server load or amount of data transmitted.
My past is a foreign country. Most things are different there, including word usage. 503 Posts 12/06
Posted - Mar 23 2012 : 4:53PM
I use Opera as my browser for accessing the ADT forum. It has a web page viewing option called "Fit to page", which I invoke. Opera (on the fly) resizes the page that has an image that is too large and I never have to contend with scrolling (left to right) to view the entire page.
There are dozens, sometimes hundreds of requests made by a a user's web browser to the server for a single web page. It first requests the HTML and parses the page to see if there are any resources not already cached locally in the browser. If the browser finds images it needs to fetch it fires off separate requests for each image. When the HTML calls for specific height and width attributes on an image those are just rendering hints for the browser. As you indicated, modern browsers will set a placeholder of width x height in the layout of the page before requesting the contents of the image from the server. Say the image is uploaded and stored on the server as a 1280 x 960 pixel JPG file. The HTML page attributes for that image call for 80 hex 600. The browser requests the image from the server. The server sends the data over the internet for the full 1280 x 960 image. The browser then shrinks it to 800 x 600. That's a waste of bandwidth. The server could reprocess the image on the fly to meet the requested image size but that's inefficient because the processing step would have to happen every time the image is requested from the server. It's far more efficient to resize the image one time at upload and have no further processing requirements. I see these kinds of problems frequently when visiting Wordpress blogs.
Even better. I didn't realise this is what you are doing, so thanks for clarifying. I guess the issue then is that the maximum width allowed is too big for some of us. Perhaps an option in user settings to reduce the maximum width would be the best solution, and apply that to the generated HTML in addition to the resizing applied at upload. A minor issue in the grand scheme of things, but when you have a great site already, it's the little things that count.
What is your screen resolution? When we made the switch to allow images that are up to 1024px wide it was based on the assumption that the vast majority of our users have screen sizes of at least 1280px wide.
Screens might be bigger then they used to be, but that does not mean that people are browsing with that larger resolution. You can see in Google Analytics what resolution is actually used. My experience on our sites is that a lot of people still use 1024 width for their browser. I use 1200 width myself and I have to scroll sidewise too sometimes. Jacco
Yeah, with a huge monitor you usually don't have a browser window maximized. I actually have two side by side (but I have a very high resolution monitor so I can still view huge pics).
1920 pixels wide, but my browser at the time of writing is 1132 pixels. Text is easier to read in a more columnar layout, which is why newspapers are layed out the way they are. If this site was just text, I would narrow the browser width further.
Looks like the size maximum for quickie image uploader got changed from 800 pixels wide to 1024? I've also been seeing some way oversized images posted this week and came to this thread to see what that was all about. I guess I have the answer. Edited by - HeyNow on 1/23/2013 4:47:55 PM
I did some tweaking a few days ago. Yes, it's 1024 now. It's an experiment to see what's going on with those huge images making it through. I haven't figured out how they are making it past the image resizer. There's essentially two steps in the upload: 1) get the file onto the server via HTTP and 2) process it (resize, rename, move it, etc.) I don't know how it's missing the resize step. It only seems to be on huge images. The odd thing is that the script completes! I dunno.
The 1024px wide experiment is killing me. 1024px wide makes the posts wider than the screen, which screws up the thread width. It means that you have to scroll back and across, back and across as you read any post that's over a couple of words long. And when people quote a 1024px image the thread gets even wider. As a reader and as a moderator, it's annoying as fuck. Can we go back to 800px please? Otherwise I predict that no one will want to read or write a post more than a couple of words long any more, effectively turning adultdvdtalk into adultdvdimagepostingsite.
"You have sacrificed nothing and no one." 3689 Posts 8/10
Posted - Feb 16 2013 : 9:52AM
I've always re-sized images I upload to 800-pixels wide maximum before I upload them. I've always felt I get a better result this way (as opposed to an auto-resizer), anyway.
^ I do the same Goldstein, for the same reason. Drew has switched the max back to 800px wide now, so it will help some of the scrolling back and forth problems I was complaining about above. I said thanks in another thread, but I'll say it here too: Thanks Drew.
I'm curious if it makes a difference still to resize prior to uploading? I am using a different resizing method now that should result in better quality resized images.