Nope. The limit is there to make the server not explode.

and there isn't a better, and way more efficient way of searching that deep without consuming the servers resources?

This is the better and more efficient way of searching that deep.

Idk if it helps, but I figured out you can search through deep posts in more manageable 5-15 page chunks by doing some tag voodoo.


For reasons, I'm currently digging through the record of uncensored pussy images from oldest to newest so I'm searching using the tag combinations "pussy uncensored id:<20000" for the oldest of the oldest posts and after I run out of pages (from highest page to lowest page) I go with "pussy uncensored id:<40000 id:>20000" which gives the next 20000 tag id's, this way you can keep the searches in smallish page amounts. Just add 20000 after each section of searches to the search bar for both numbers.

id:<40000 id:>20000
id:<60000 id:>40000
id:<80000 id:>60000


etc etc.

At the start of each new search go to the back page to continue with the oldest to newest stuff.

this is just getting stupid. Why the hell can't we just donate enough $ so the host can get a big enough server so we don't have to deal with this bullshit? I'm getting really fucking tired of having to do this, with each result having WAY TOO MANY FUCKING DUPLICATES OF POSTS THAT I"VE ALREADY SEEN!!!

We aren't using a host's servers. We own the physical servers that Gelbooru runs on, and have to pay full market price for any hardware upgrades. Sticker sales are indeed going toward such upgrades as soon as we sort out our need for increased bandwidth, which is an entirely separate issue from what made us implement the depth limitation, and which is currently much more pressing.

I still can not go to the beginning of my posts even if I go there page by page!

gelbooru.com/index.php?pa...%3arobblu+id%3a%3c3000000

Alternatively: gelbooru.com/index.php?pa...%3arobblu+sort%3aid%3aasc

Does this workaround still work to search past the limit?

Yes, but while we're on the subject and there are a few threads active about this already, can someone explain to me like I'm 5 why this limitation is even a thing? I get that its a hard coded limit to stop the servers exploding, but why would the servers explode in the first place? Is it a hardware/software limitation? Or is it a spaghetti code problem. Why is it that similar websites to this don't have this same issue? Is it something to do with how you guys started developing the site versus how someone else started developing theirs and at this point you are too far along to easily change the foundation of how the site works and brings up information?