request: "show original image" switch in url

葉月 said:
But then I have carefully to parse each danbooru URL, and moreover, I need to *know* about such function. Again, I don't think you should be the one to decide how I see things on my screen.

Is this a real user constituency that should be designed around? The guy who can't click bare image urls because his computer will explode? Or is the more common scenario the user with gigabytes of memory, who could load a hundred large images without breaking a sweat?

Are you sure it *stops* loading the sample? Hiding it doesn't necessarily imply the browser won't fetch it anymore and that it frees all the buffers it allocated. And I'd rather it didn't keep 10k x 10k buffers around when I didn't ask it to.

This is kind of ridiculous.

alfred said:
Is this a real user constituency that should be designed around? The guy who can't click bare image urls because his computer will explode? Or is the more common scenario the user with gigabytes of memory, who could load a hundred large images without breaking a sweat?

There's not really any *critical* problem here at all. I'm just saying I hate it when this happens:

Bapa wants to send a post to someone, but the image is particularly large. So, he has to tell the other person to find/click the 'Resize image' link so they can view it properly. Otherwise, if the other person doesn't know about this, they'll only see a small, cropped section of the image (which they'll have to scroll through), and won't be able to appreciate the full impact of the post - since they can't see all of it at once.

It's not a matter of somebody's computer exploding at all. Again, it's just that of convenience (hate having to tell people to click the 'Resize image' link =P). Y'know?

alfred said:
Is this a real user constituency that should be designed around? The guy who can't click bare image urls because his computer will explode? Or is the more common scenario the user with gigabytes of memory, who could load a hundred large images without breaking a sweat?

*I* ask to be served samples for a reason. I don't see that reason being invalidated just because *you* want the full view. Which part don't you understand?

Danbooru defaults to resized sample and fit to browser window for guests, I believe. That would let him always be able to view the full picture, at worst with vertical scrolling. If the user wants something else, they can make an account and specify it.

doublequot Are you sure it *stops* loading the sample? Hiding it doesn't necessarily imply the browser won't fetch it anymore and that it frees all the buffers it allocated. And I'd rather it didn't keep 10k x 10k buffers around when I didn't ask it to.
endquot
This is kind of ridiculous.endquot

post #543258 28.8 MB
post #539926 12.8 MB
post #542316 21.7 MB

I didn't even hunt for these, they just looked hard to compress on page 1 of 'huge_filesize'

If it were up to me it would not even be an option to disable server-side sampling. Many pictures on danbooru are sizeable downloads. People grabbing them and then having their browser resize them are sinning against poor children in ethiopia without two bits to rub together!

This isn't a movie sight where you can tell the difference between the HD quality the server has and the crappy stream you get on your computer. Server sample size is 100% size of of most browser windows, and not much less of the rest, and full quality. The only reason anyone would ever download the full size is because they plan to print it, which they wouldn't decide before seeing the picture.

Hunted and couldn't quite find a 10kx10k, lots of 10k x (<10k) though.