New update that adds comment scores, tag categorization (which can be disabled), and more! View the changelog
You could do this using cookies, storing 2 ids (previous and next ones), when the user clicks next, the next id is loaded and the same for previous
So let me get this straight: your search results look something like this:
2 3 5 7 11 13 17 19 23 29
User navigates to post 7. A cookie is created with field "prev" = 5 and field "next" = 11. So far, so good. User clicks next. Now they're viewing post 11, and the cookie has...what? Since they came from post 7, we can set "prev" to 7, and that works out okay. But what do we put in "next" now? The only way to figure that out is to run the search again, which runs into the whole "excessive server use" problem that this system is supposed to avoid.
in the bottom right corner, there is a couple of dots shaped like a triangle, with that you can expand the box as much as you want
Hi there, fellow Chrome user!