[X] My Assistant

First post here, well done for the motivation. Absolutely horseshit update and navigating the site is the most disgusting experience, that's about all there is to say.

Ability to save specific spot is definitely good, people just need more convenient navigation like years range and skipping more than 1 page.

I understand the technical limitation although the solution pains me. There are two annoyances: first one is knowing "how far you are when browsing randomly through galleries" and second one is "I don't know exactly what I want, but it was roughly there when searching x/y/z"

For "how far you are", would "eyeballed" page numbers be possible? Like one based on your current session: "before hitting next, you were at page 2 of results, now you're on page 3" (while preventing browsing through pages) or "based on density and gid, you're roughly at results number 2000 which is a rough page x" (most recent result is GID x, oldest result is GID y, you're at GID n and we eyeballed p results, so you're roughly around there)?

For the second one, if you logged in, would it be possible to store the last gid of reference of a search and gives a "resume your last search from there"? Wouldn't solve everything, but could alleviate some issues.
I think the biggest issue people have is not having any kind of "landmark" to where they are when browsing because, sadly, people do not browse lists like database do.

I do get it's rough, and it's the thankless job of making a quite well used site/archive survives despite certainly limited ressources and layers of legacy code over legacy code.

This is stupid as hell.

Please reconsider removing page numbers.

I just want to add my voice to the complaints about the page selector change.

I systematically used page selectors to do many things at once:

- See how many pages a specific tag/author has
- See results uploaded in a timeframe without having to specify the timeframe ("I'll just jump to page 50")
- Find new authors and artists (especially ones that didn't produce stuff for years) through randomly jumping to a page
- Much more

Now I either have no idea how to do it with the new search mode or I would be forced to do these things separately.

Of all the things, I don't understand why -as users- we should see this as an improvement.

I'm cool with the backend stuff, and very much empathize with the performance improvements - earlier I was puzzled how EH managed to do page-based pagination with its scale of results and tags and users. ID-based pagination is all fine by me, efficient and stable! However.

Display dates. The dates of the first and last result would set the limits of the search to the user, as currently the experience is very "there's some results, and there may be more". Counts would really be nice, but I do understand why they're out, so "Most recent result is in 2022-11-02, oldest result in 2019-05-10" or such.

At least (as others have noted) there should be UX to input a date to seek to, which should be trivial backend-wise.
IDs are very nice for machine things, but the majority of the frowning here is "why do I have to remember which ID belongs to which date to jump in time", so give them dates.

Edit: Oh, but favorites ought to have pages or at least a count. It just feels so blind.

This post has been edited by MRX-II: Nov 2 2022, 23:55

So how do I effectively browse "pages" now? I might not he the smartest guy out there but it's not very clear from the OP
Can you only move one page at a time now?

(IMG:[i.imgur.com] https://i.imgur.com/QnF1XiS.jpg)

I understand why you removed the pages it sucks balls but I understand.

But please for the love of god let me search for galleries while including expunged and low power tags. I now have to search THREE times to see everything for a single search which makes it take far longer to go through.

Ability to save specific spot is definitely good, people just need more convenient navigation like years range and skipping more than 1 page.

this still doesn't fix the navegability problem and burying tons of galleries, just add the pages back or atleast an option on the settings so it is not that loading heavy. I hope they listen to the people and just add them back or revert this

The people have spoken, Tenboro: we hate the new format. And like I said said before, the mouse and index finger weren't meant to endure all that clicking

This post has been edited by sr331: Nov 3 2022, 00:05

New update is ass and admins should feel ashamed of themselves for even trying to defend it. Complete downgrade

If I simply search for "Futanari" (with my filters on), I get 70,062 search results. Obviously if I disable my filters there can be more. If I wanted to go to Page 32, how the fuck am I supposed to do that?

I know for a fact I have about ~50 pages worth of favorites. Again, if I wanted to go to a certain page, let's say; page 12, because I know certain shit is on that page, how am I supposed to get there without endlessly clicking "Next >" a dozen times?

Sorry, I don't bookmark specific pages like you guys supposedly want us to do now.

click click click click click
*cracks knuckles*
click click click cli- ∞ made it to my page 70 clicks later surely this is more efficient than having a proper page selector... (IMG:[invalid] style_emoticons/default/rolleyes.gif)

Everything between the first and last page is dead now.
There has to be another solution.

I don't understand why the favorites are treated the same way. Is searching through favorites that RAM intensive? And I think unavailable galleries should show up in the favorites. Sometimes you favorite something which later gets taken down but you at least want to know that thing existed. Now I have a number of unavailable galleries which does not show up in the favorites but still gets counted with no way to figure out what it was nor remove them from the favorites. (IMG:[invalid] style_emoticons/default/cry.gif)

I can't believe they removed the page feature that 90% of users rely on! First of all, we need to understand what search is? It's a way for users to quickly and accurately find the content they want, instead of spending more time and traffic clicking on the next page.

The original search worked fine, is this an update? Why does it feel like a stupid regression
Was this update created so that users could not find the results they were looking for?
Or was it created to make users repeatedly click on the next page
The results I want are on hundreds of pages, do I have to click next page hundreds of times?

This post has been edited by w67879017: Nov 3 2022, 00:58

Just use a GID from that period, it doesn't matter if its not in the results. Took about 10 seconds /?f_search=ahegao&next=800000

It's even better, because that will always be positioned at the same place, without new galleries moving it further back, you can just bookmark the 1 url and not worry about it like you used to with page numbers.

In that case, it would be best if someone can update the wiki with GIDs corresponding to particular years and months. Or suggest an increment in GID that would correspond to "next 50 pages" (doesn't work with tag filtering though).

the pros are definitely less than the cons, or better worded, paging is a really basic feature for a site like this, a really big one to remove

REMOVED (it was a mistake double post)

This post has been edited by omega necross: Nov 3 2022, 00:18

I'm not sure what the technical side of this search engine looks like, but I've used ElasicSearch with huge datasets (similar tagging structure as EH here too) with no problems. I'm talking over 1mil documents in the index. Pagination still very easily a thing and never took my server down. Not crazy hardware either.

I'm with the majority of commenters here missing the page numbers.

My use case was to basically 'roll' a random page or two and see what's good on that page. Can still do that much at least now by just picking a random number, but being able to then just only to even/odd pages (stupid, I know, but I did it all the time) was much nicer.

I also had a much easier time finding stuff that I knew was around page XX and just explored a bit. Can't do that anymore.