Is there any way I can change so that I can view more pictures om a page instead of pressing "next" every time?

You can change that in your user settings:

https://e621.net/user/edit

Butterscotch said:
You can change that in your user settings:

https://e621.net/user/edit

Where? I can't find it

TheHuskyK9 said:
Where? I can't find it

http://i1242.photobucket.com/albums/gg524/dfx09/test.jpg

It's the first option below the blacklist section.

Wow people actually do the whole "Next picture" thing?
You can go back to the index and just go from there, its just faster, and you don't have to view every single image in post number order.
On that note, why is it that when you type in a specific search and then go on the picture, and click next, it doesn't go to the next image in that search criteria? Why will it only go to the image with the next ID#?

Moon_Moon said:
Wow people actually do the whole "Next picture" thing?
You can go back to the index and just go from there, its just faster, and you don't have to view every single image in post number order.
On that note, why is it that when you type in a specific search and then go on the picture, and click next, it doesn't go to the next image in that search criteria? Why will it only go to the image with the next ID#?

Because reasons

Can anyone get more than 150 results per page? That seems to be the most I can get despite the max supposedly 320.

Moon_Moon said:
Wow people actually do the whole "Next picture" thing?
You can go back to the index and just go from there, its just faster, and you don't have to view every single image in post number order.
On that note, why is it that when you type in a specific search and then go on the picture, and click next, it doesn't go to the next image in that search criteria? Why will it only go to the image with the next ID#?

They claim it's for performance reasons, each time someone clicked on the "next picture" button the search would have to be repeated, and that would be too big a burden on the servers.

That argument doesn't really hold water though. It would be easy to cache the results of a search in a cookie or with client-side storage, and then the next and prev post buttons could just move through that list of posts. No need to repeat the search at all.

Wyvrn said:
They claim it's for performance reasons, each time someone clicked on the "next picture" button the search would have to be repeated, and that would be too big a burden on the servers.

That argument doesn't really hold water though. It would be easy to cache the results of a search in a cookie or with client-side storage, and then the next and prev post buttons could just move through that list of posts. No need to repeat the search at all.

Whatever you said just went right over my head. I'm not all that "tech-savvy".
Along with that, how is that any easier than just pressing the back button and seeing the main post page and going from there? It's 2 clicks...

Moon_Moon said:
Along with that, how is that any easier than just pressing the back button and seeing the main post page and going from there? It's 2 clicks...

This.

Wyvrn said:
. It would be easy to cache the results of a search in a cookie or with client-side storage, and then the next and prev post buttons could just move through that list of posts. No need to repeat the search at all.

the problem with that is you would have to code the previous and next buttons to read off of that information and it would cause problems for anyone who doesn't allow cookies or caching

Sollux said:

the problem with that is you would have to code the previous and next buttons to read off of that information and it would cause problems for anyone who doesn't allow cookies or caching

True, but the buttons could easily be programmed to fall back to the current behaviour in that case. Inconsistent browser support is nothing unusual in web development, and it's not a problem as long as intelligent fallbacks are in place.

Hell, I think I'll implement this as a userscript. Put my money where my mouth is.