[X] My Assistant

No?

You hit the little ... button and type in the percentage you want to go to. There's no guessing.

If you have no better reason jumping on specific pages (in main gallery search) than to try to guess where something is, then you have no reason at all. What we need is either a way to bookmark GID on custom search filters, or a date range filter.

Browsing "page by page" on what is technically a gallery dump is the way to go. If it has too much results, we should be able to trim it into an amount that will make sense by filters instead of randomly guessing where a certain gallery is. This is why it'll be better to know the total number of results imo. If the results are too small, there shouldn't be any problems pressing next buttons. The argument of wanting to go to specific pages would only make sense on lists like favorites/bookmarks since they are already a small list that won't get updated every few minutes without the user's knowledge. Otherwise, page numbers on the main gallery list is dynamic because new ones keep pushing the older ones down, so jumping pages through them to find something is usually a guessing game as I said, and jumping pages without any specific gallery to find is plain pointless.

This post has been edited by sakuracircle: Nov 3 2022, 19:56

People keep saying I can use GID to navigate the site chronologically.

I don't know what a GID is, I don't know the the difference between an earlier GID and an older GID.
I used page numbers for chronology and the update date.

Last page was the older result and the First page was the earliest.
So if Porno Chapter One in original japanese was released on page 5 for X artist then I know Page 1 to 5 will contain chapters 1 through the latest chapters will be contained there.

Including translations and maybe other chapters on other stories/series from the same artist.
With this new update I am stuck just pressing next hoping I get lucky.

Maybe the page number was not perfect or perfectly accurate but it provided some structure. Like a time grid or a slider to navigate, there is no option to really control my navigation... either I go forward or I go backwards wasting time and site resources because it has to keep loading results until I figure out where I am.

I understand this GID system that I do not really understand myself is improvement on the technical side but I am completely lost.

I suggested earlier to give us more filter options like "Include original language and english", sorting things like chronologically, maybe even instead of page numbers there is a grid that we select the GID code filter so when we know the range of GID we can properly navigate our search.

Is this a possible change?

The most significant and visible fundamental change is that the internal segmenting of search results is now done by gallery ID (GID) ranges rather than "pages". While this means jumping to an arbitrary "page" in the result is no longer supported, this is arguably an improvement since you can now jump to an arbitrary GID instead.

You don't need a ringer on your phone; you can pick up your phone at any time and check if anyone's calling you. Isn't that so much easier?

You don't need interrupts on a computer chip; you can just poll it constantly.

I'd understand your argument more if there was a GID entry field on the page, and maybe the highest GID on the site (or even search) was listed somewhere on each set of results. "Jump to GID: [n] (out of 2367605)"

This post has been edited by dragontamer8740: Nov 3 2022, 20:02

how do I include low power tags in my search without searching only low power tags? I used to be able to do it, but now I can't figure out how with the new search system...

Hi, posting here for the first time to say that removing the page numbers was poorly thought out and a bad update.

You don't improve UX by removing buttons and suggesting that they modify their URLs manually, has any large tech company implemented anything like that? Hell no.

Hi, posting here for the first time to say that removing the page numbers was poorly thought out and a bad update.

You don't improve UX by removing buttons and suggesting that they modify their URLs manually, has any large tech company implemented anything like that? Hell no.

This wasn't a UX redesign. This was a backend redesign that necessitated a UX change.

I agree, there should be an entry field on the page at least.

Also, I'd like if 'show expunged' still could be ORed with non-expunged results. But I'll get used to that if I have to.

Finally, if a large tech company redesigned this site they'd have done infinite scrolling with javascript, and I'd be pissed off instead of simply annoyed. "Big Tech" is a disease, and even if I don't like this redesign, I think it is still a far sight better than things like twitter.

This post has been edited by dragontamer8740: Nov 3 2022, 20:10

First time writing a comment.

I agree with others that removing page numbers with no alternative UI is a terrible decision.
An alternative UI like the one commented on this thread should have been made.

However, a lot of comments here are saying "bring back page numbers back", assuming that it's a trivial thing to do. As a server dev I know that it's actually near impossible without seriously harming the performance of the server.

To browse page 101, the server first has to know what's the first gallery of the page 101. For simple queries it can be done relatively fastly (with indexing), but with sophiscated enough queries (especially with bunch of ORs and exclusions) the only way of knowing this reliably is basically fetching every galleries in the first 100 pages.

So page browsing probably have been pressuring the DB too much. I expect that even pressing "next" 100 times in the new system, while would use more server bandwidth, will pressure DB not much more than (or even less than) simply browsing to page 101 in the old system.

In summary, yes the UI is terrible, needs to be improved, and can be improved, but "bring back page numbers" is not as easy as you guys may think. What we need is intuitive way of dealing with GIDs.

(btw for favorites page number should have been kept unless there's some shenanigans going on behind it)

This post has been edited by Dhxa: Nov 3 2022, 20:19

Might we be able to do "pagination" by month? So the server would keep a static list of which GID is the first (or last) for each month of each year, and then just add unconditional jumps to the next and previous number in that list to a requested set of results? (setting ?prev=(that id))

That'd greatly reduce the amount of time I'd spend clicking and might be a suitable compromise, right?

So far that list would have < 360 GID's in it. A lot less than the millions of galleries we are at now.

This post has been edited by dragontamer8740: Nov 3 2022, 20:41

In summary, yes the UI is terrible, needs to be improved, and can be improved, but "bring back page numbers" is not as easy as you guys may think. What we need is intuitive way of dealing with GIDs.

For this even I can say it is indeed as easy as people think if it is with a modern freely available search engine.

I understand the need for the changes, but usability for the end user must also be considered. Not all people use the search function to search for something very specific. Some want to discover something they hadn't seen before or something they may have missed during times they were not visiting the site frequently. For those kind of things the page system was really helpful. As the admins say, there are ways to do this with this new system as well, but you need to give the users the tools to make it easier to do so.

A solution that, in my opinion, can be implemented quite crudely but in a fast manner, would be to:
- display current GID position
- display GID range for the entire search (first and last related GID)
- give the user a modifiable button to jump forward or backwards a certain number of GIDs (either by user defined increments or a selector for a number multiplier [100, 1000, 10000 and so on]
- and lastly a box to jump to specific GID

As it is implemented right now, trying to search or discover new stuff within a few number of clicks of the First and Last sections is nigh impossible. And you cannot expect your users to modify urls on their own. A tech savvy user might do it, but the great majority will not.

tl;dr the changes can work so long as you give the users more visibility of exactly where they are and tools for them to navigate more easily

I was just using Sukebei and Nyaa very nicely and realized how fucked those sites would be if they removed page number. the whole "GID is better than pages" argument some people are trying to make is disingenuous, the update is extremely user unfriendly, there is a reason every site ever uses pages, you can't expect people to learn to use your specific search method based on gallery ID, it is extremely pretentious to think that.
come on... just add pages back.

For this even I can say it is indeed as easy as people think if it is with a modern freely available search engine.

Any example without bad performance?

For example Elasticsearch states "Avoid using from and size to page too deeply or request too many results at once." and "We no longer recommend using the scroll API for deep pagination. If you need to preserve the index state while paging through more than 10,000 hits, use the search_after parameter with a point in time (PIT)." with regarding to pagenation.

In layman's term they recommend the current search engine behavior.

... "GID is better than pages" argument some people are trying to make is disingenuous, the update is extremely user unfriendly, there is a reason every site ever uses pages,...

GID is better than pages in terms of not pressuring the DB too hard. Not in terms of user-friendliness or in overall.

Pagenations can be used with simple tagging system or when the result is not too much.

I do agree that the current state is terrible.

The change should have only followed after publicly discussing (ex: advanced search engine vs
dropping the pagination, talking about alternatives to pagination) the change.

This post has been edited by Dhxa: Nov 3 2022, 21:11

By the admins own admission, he won't read this, so I guess I can just write whatever the hell I want? Guess I'll scream into the void for my own amusement/venting.

Admin is clearly doubling, and tripling down on his brain-dead decision to remove any sensible, human-readable form of navigation. For all that talk about GID's, where is it in the UI? I'm expected to navigate the website using the URL itself? That is the most ridiculous nonsense I have heard this month. Hey admin, do you check your email through the command line as well? You seem the type.

On the flip side, some clever users already posted js scripts to provide us with some way of navigation! Amazing, end users could provide in a day, what the admin with full access to the source could not. If that's not incompetence, I don't know what is.

Years of content erosion, "sorry this gallery is claimed by Irodori/Fakku/whatever", and now removing fundamental pieces of the UI. What's next, gallery ordering by image hash only? I always thought this site faces only threats from the outside, never in my wildest dreams did I think it would implode from within. What a shitshow.

GID is better than pages in terms of not pressuring the DB too hard. Not in terms of user-friendliness or in overall.

Pagenations can be used with simple tagging system or when the result is not too much.

I do agree that the current state is terrible.

The change should have only followed after publicly discussing the change.

the whole point of a website is being used friendly, that is the very first thing that developers drill into your head while getting a programing degree, it is better to have a pressured DB with a completely user friendly site than a fully optimized program that people need a manual to learn how to use

The problem is that this dropped without any announcement, without any testing or feedback on how to make the experience okay. Currently anything between first and last page is essentially dead.
We don't need the exact same system with pages if it is such a big problem, but there needs to be an alternative.
Dropping this on everyone and go "just use GID" is just stupid.
This update is not user friendly. It reeks of devs making decisions based on what they find okay to navigate without any regard for a normal user (I work with many devs, so I would know).

the whole point of a website is being used friendly, ...

Agreed.

... it is better to have a pressured DB with a completely user friendly site than a fully optimized program that people need a manual to learn how to use

The latter is bad, agreed, but "a pressured DB" means that a site will be laggy. If the pagenation was kept with the OR and exclusion queries, in the worst case the entire site may be so laggy that a page takes a minute to load it's unusable.

Again, like the other person said the problem is lack of pre-announcements and feedbacks.

We could have gotten (but didn't get) a new search engine with less lag and actually intuitive UI that isn't pagenation but as easy as it.

All I wanted to say is that "bring back pages" isn't that simple.

This post has been edited by Dhxa: Nov 3 2022, 21:30

I happen to have 80-some pages of favorites sorted by favorited order. There's now no way for me to jump to a random page without counting how many times I press Next. I also can't modify the URL as it makes no fucking sense in favorited order. Am I just shit out of luck now?

Also, expunged favorites being hidden is frustrating...

Agreed.
The latter is bad, agreed, but "a pressured DB" means that a site will be laggy. If the pagenation was kept with the OR and exclusion queries, in the worst case the entire site may be so laggy that a page takes a minute to load it's unusable.

Again, like the other person said the problem is lack of pre-announcements and feedbacks.

We could have gotten (but didn't get) a new search engine with less lag and actually intuitive UI that isn't pagenation but as easy as it.

All I wanted to say is that "bring back pages" isn't that simple.

it is pretty simple, the site was slower, not "SLOW" searches never took more than a second, yeah now the stuff is done in a fraction of a second, what's the point when most of the site will be forever buried and people will only look now at the recent galleries or specific stuff they wanted to look? like I said, this completely kills discovery and tag diving.
I guess Jacob and the others are happy that the biggest hentai page just killed itself.

what's the point when most of the site will be forever buried and people will only look now at the recent galleries or specific stuff they wanted to look? like I said, this completely kills discovery and tag diving.

Other people already posted suggestions and even a working solution ( https://forums.e-hentai.org/index.php?s=&am...t&p=6202058 ) on this thread that it's possible without pagination.

Removing pagination by itself could have been fine. Lack of getting feedbacks like those while removing pagination is the problem.

This post has been edited by Dhxa: Nov 3 2022, 21:46