[X] My Assistant

We got an extra 20 horse power boys, but we had to remove the wheels.

I understand that pagination rapes the servers, but that's a reason to improve it rather than just ax it entirely

New search is extremely unfriendly and unintuitive. Do users really have to look up a 3 pages of rules on some forum post to search for galleries? These new features are cool, but you completely broke existing navigation. How do i look how many results are there? With pages it was easy, as well as looking for something in between, like page 20 to find gallery by date out of 70 page result.
Also a lot of simple tags search do not work. Please change it back. If you want to add some niche syntax for extremly precise searching, do not ruin everything else.

This shit fucking sucks and why the fuck would i use third party programs to fucking search in something i want to fucking see?

And who the fuck gives a shit about what sankaku or other sites are doing with their shit?

I want to have numbers so that i don´t have to click next a fuckton of times ffs,,,

And no i don´t fucking want to use that shitty whatever it is gdi if i´m searching for a artist and want to see some olde ruploads bcs they were uploaded years back...

So to make this short, change it fucking back and you make fucking money with this site and you make that through us the fucking users, and we´re not happy, so FUCKING CHANGE IT BACK

I know it's being brigadeered, but some amount of the complaints are of course organic. However, since page 5 or so it's just people spamming about page numbers, and I can't keep replying to that.

I get that people feel strongly about it, but as a tradeoff between functionality and performance, this is pretty much the best I can do. The old search engine isn't actually working anymore despite people claiming otherwise, and the alternative was a severe reduction in functionality.

You mention Nyaa, which has page numbers, but you can only see 1000 results per search, is that really what people want?

And I'm not sure why people act like they can't use the dates of the posted galleries to "know where you are in a search".

(I'm actually busy with making some additions to the search engine, so I won't keep posting.)

Have you considered the possibility that this is such a shit update from the user's perspective that people who never post are actually going out of their way to complain about it?

Okay for server.
EXtremely bed for user.

My suggestion:
How about the search time limit? Such as waiting 10 seconds if want search again. Also can reduce the pressure of server.

This post has been edited by Arcticbat: Nov 4 2022, 02:46

Aren't search engines supposed to be user friendly? This is the exact opposite of user friendly.
How did we go back 20 years in time, having to manually edit URLs?

Some suggestions. Trying to be positive for enhancing the user experience with the new engine.

General: Don't assume people are going to use GID. They don't give a fuck or don't know what they are. As a friend told me: when they're horny, even the smartest users don't have brain anymore (he's a web dev for porn websites).
Use dates instead. When there is a few results, simulate or regenerate page numbers from the results.

- Display the date matching the current GID on the current displayed result page.

- Add a way to jump to a specific date that will jump to the matching GID

- Restricted page numbering on general gallery (?): make something like the server generates the previous 20+next 20 pages or so, display those as numbered pages, and if the use reaches page 20, then generates the next 20. It looks like it's only a matter of generating the pages like "next" is clicked 20 times at once. I don't know the internals of the engine so it's only a suggestion. It's kind of "fake" page numbers but yeah, a lot of people use websites that way.

- Favs: exception. Generate all page numbering from the results except if there's too much (like 5000 results or so). Dates are absolutely not relevant in favs.

- Cache results as much as possible with a small TTL. Like for instance, caching search results and page numbering for favs during 30mn should be good enough. Empty the cache if the user add/remove favs.

- Record the highest GID available from the last user visit. When the user comes back, you then highlight any new post from that GID.

- Add a "random" button that will jump to any random page/GID from the results.

This post has been edited by kxk: Nov 4 2022, 02:43

No, it doesnt need to fetch any galleries. It only needs to look at the resultset it got anyways. There is a "limit" clause in most languages for a reason.

By "fetching" I meant how many rows should be looked at. In the perspective of DB itself.

DB engine is not a magic. If the result set before limiting is large and the query is complex enough that the index can't be used properly (full scan) then # of rows has to be found with pagination with "offset" and "limit" would be linear to "offset+limit" which is the problem.

Many RDBMS provide cursor mechanism which is... basically identical to using GID. So for me this seems like the dev implementing something intuitive to them without considering what users would experience.

This post has been edited by Dhxa: Nov 4 2022, 03:07

i never asked for this

Just do a rollback. This is horrible!!

Came for the first time to see what broke the site. Thought it was a bug, sadly it was a feature (IMG:[invalid] style_emoticons/default/sad.gif)

If I understand correctly the problem is not the overall volume of searches, but when some searches get too many results/pages?
If so couldn't you just make those searches look within parts of the database, instead of the whole thing?
For example. Because of the search terms used, we expect a large number of results. Therefore, this search will only check within section A (last two years, or gallery ID numbers 70k-90k or whatever). Toggle this switch to search again in the next section - B, C. Etc.,

People who search by creator/series would still search the whole database because expected results/load is small.
And people who look for newer content in large tags will be fine.
Only those who want to suffer by searching for something within poorly defined 100k results, because they don't save history/bookmark/favorite, or want to play archeologist, be affected.


This post has been edited by MoonMasterXY: Nov 4 2022, 03:37

Maybe the site wouldn't be struggling as much if it weren't for the fucking image set spam by the gp farmers.
Like someone else said earlier, introduce monthly quotas and reintroduce gallery update limits (fuck you pork-zero).

If large searches were the problem, couldn't you just make those searches look within parts of the database, instead of the whole thing?
For example. Because of the search terms used, we expect a large number of results. Therefore, this search will only check within section A (last two years, or gallery ID numbers 70k-90k). Toggle this switch to search again in the next section - B, C. Etc.,

But people who search by creator/series would search the whole database because results are small

there's a billion things they could've done instead of this, but they already dismissed any critics as "brigading" and called it a day. way to kill a site to be honest

I'm not actually reading this thread anymore due to the heavy brigadeering. I get that it broke your favorite viewing tool, but all the reasons for why "bring back page number" isn't long-term technically feasible was already answered in the first few pages of the thread.

There are some bugs being fixed (missing galleries in favorites, some uploader search stuff and some navigation stuff), as well as a function to address the (ostensible) biggest gripe about not being able to jump to the middle of search results, but these things aren't written, tested and deployed overnight. I will however hold off on deploying the update to EH until it's ready.

Brigadeering? An userbase being angry at idiotic decisions isn't brigadeering, stop sniffing your own farts.
You broke navigation "to save computations and ram". That's not fixing the issue, that's causing more unnecessary pageloads to find where and when you are and want to be, not to mention the new userscripts to restore this BASIC functionality of a search engine. Good job, here's a cookie. Posts 539 and 551 put out a good sum-up of what you COULD have done instead. I'm not linking to it, you should know the post ID, right?
You made an absolute, full-blown, dogshit dumb-as-fuck decision and the half the entire userbase is calling you out because of it. Maybe you should've looked around how other image websites do it, maybe actually read up on newer and more efficient techniques.

or maybe you just have a hate fetish, in which case sasuga, gg no re very basado, couldn't have done it better

This post has been edited by KoningWilders: Nov 4 2022, 03:55

Based on the excellent job of FabulousCupcake, I tweaked it a little bit, now it should work with compact/extended list and will show the span of gid shown.



[gist.github.com] https://gist.github.com/OceanS2000/0849a058...71958944883b4df

does it not work with thumbnail yet still? I just see a giant green bar with the top number being 2367831, and the bottom being null.

There isn't even an option built into the UI to skip ahead to where gallery [insert number] is for those that wanna roll the dice, so you have to manually alter the url. Nuking page numbers with zero alternatives feels like a rushjob

This post has been edited by Small Waves: Nov 4 2022, 04:03

This is like YouTube removing dislikes all over again. Even though this update is hated by almost all the users, people will keep continuing to use it. Fact is, there is no other site which has as much content as e-hentai. This and Hitomi.la are the only sites I know with artist CG, western, gameCG and doujins in one place. Hitomi.la is absolute cancer to browse on mobile and has almost no social features. Though it does have page numbers despite its size. If their search is working fine there's no reason e-hentai's shouldn't

this is the worst update ever please roll it back and at lat try to communicate huge changes like this ahead of time and at last set testing or duel use BEFORE activation