[X] My Assistant

Hi, I have been using the EHViewer app exclusively since it is just a way better user experience on mobile. If solely for the fact, that you can full screen and that it automatically loaded the next x search results when scrolling down a search.

The app hasnt been updated and is not working with the new update anymore. Is there any way to actually get to a next page via the search field? I have tried next=some number, but I genuinely have no idea what numbers I would put there, since the app doesnt event show any IDs. How many didgitd are they, or did I miss interpret how to go to another page? This whole thing 8s just really frustrating and sad,, since this was by far the best experience I have ever had with doujins.
From the viewing experience this kinda feels like youtube slowly getting rid of features over time (IMG:[invalid] style_emoticons/default/sad.gif)

EhViewer is an unofficial app, you should go to GitHub for support.
AFAIK several builds have adapted to the new change.

Attention!

[github.com] EH-Page-Scrobbler

Now has pre-fetched pagination.

[github.com] https://github.com/Meldo-Megimi/EH-Page-Scr...ment-1310296587

People have pointed out this particular weakness, so I'm looking into a different approach of dealing with weak tags. Stay tuned for that.

Great, with a way of informing us how deep into a search result we are already on the to-do list that would mean all the big "losses" from this update for me personally are being worked on now. Time will tell if it'll be as good as it used to be but all the neat stuff we got leaves plenty of goodwill for compromise there.

Thanks for putting in the effort to check this thread on top of all other work you do.

This post has been edited by Glovelove.: Nov 10 2022, 19:58

My main gripe with this is that it killed my ability to write a brainless script to pick a random page in my favorites. I had a script with a button that picked a random page and then another script with another button that picked a gallery from that page. Can we get some sort of official random favorites page button or a button like nhentai has where it picks a random gallery from all of your favorites? Since it works by GID now, could the button just reference some list of user favorites gallery GIDs and choose a random one?

[hentag.com] https://hentag.com/

I don't understand why this site search this site but can do pagination?

[hentag.com] https://hentag.com/

I don't understand why this site search this site but can do pagination?

Well, I tried searching with the title "chinese" and the tag "big breasts", and it took 15 seconds to show the page, so my guess is it probably couldn't even with a small fraction of the traffic and even though their index is half our size..?

In general, the answer to questions like that will be along the lines of "yes, but now try doing it 10000 times per second".

My problem with the new search is that it doesnt accept incomplete words. Searching using a tags like

f:cont
f:exhib

will return 0 results unlike before so the user needs to type out the whole word.

f:control
f:exhibition


Any way this can be fixed in future updates?

My problem with the new search is that it doesnt accept incomplete words. Searching using a tags like

f:cont
f:exhib

will return 0 results unlike before so the user needs to type out the whole word.

f:control
f:exhibition
Any way this can be fixed in future updates?

Try:

f:cont*
f:exhib*

A change to how weak tags are handled, as well as some other minor tweaks and fixes:

- When searching for tags (or titles+tags) where there is just one tag match and you have that tag filtered, the system will now specifically ignore that filter. If you actually want the tag filtered, you can use the title: qualifier.

- The search engine will now stop looking for more results if more than 1000 galleries have been filtered. (This is mostly relevant in edge cases where you are intentionally searching for things you heavily filtered.)

- Fixed search warnings not being displayed for favorite searches.

- Added a setting to remove the "Your default filters removed XX galleries from this page" message.

- Added a new qualifier "weak:" to search for weak tags. This replaces the "Search Low-Power Tags" checkbox. Using weak: in front of a keyword works the same as using tag: except it will search weak tags (<10 power) instead of active (10+) ones.

This change allows for some additional flexibility, since you can now search for various combinations of weak tags and active tags - for example, all galleries with an active parody tag from a particular series, and weak character tags from said series.

Weak tags cannot be used for exclusions or searched in favorites. Additionally, if you are using OR searches, either all or none of the OR terms must use the weak: qualifier.

It is not possible to search for both active and weak instances of the same tag at the same time, or mix normal and weak OR terms in general, since they use different indexes. These are not artificial limitations. The weak tag search is there to aid in tagging and cleanup in order to either get rid of them or make them into active tags, not to get "more results" in casual browsing.

why is "browse expunged galleries" checkbox turned on by default? it reactivates every time i refresh or open a new window

why is "browse expunged galleries" checkbox turned on by default? it reactivates every time i refresh or open a new window

Can't reproduce. Some outdated userscript probably?

Can't reproduce. Some outdated userscript probably?

seems like it, although i dont remember installing any scripts for e-h. i turned off tampermonkey and now everything's fine, thanks

How do i search gallery with low tag ?

How do i search gallery with low tag ?

- Added a new qualifier "weak:" to search for weak tags. This replaces the "Search Low-Power Tags" checkbox. Using weak: in front of a keyword works the same as using tag: except it will search weak tags (<10 power) instead of active (10+) ones.

weak:f:"very long hair$" etc.

When you search by specific tag now, just let the page open where you left it, or bookmark it, the galleries that you see on that page will be the same tomorrow or even after a month if not deleted.

Not a solution, what if i view the site on another device? What if i forget to bookmark or close the tab? What if I just want to use the site like I did normally without any issues.

Not a solution, what if i view the site on another device? What if i forget to bookmark or close the tab? What if I just want to use the site like I did normally without any issues.

So many what ifs... you can't be serious right?
What if you forget which page you were on?

What if you view the site on another device?
- Use a browser with sync feature.
What if you forget to bookmark or close the tab?
- Use browser history.

Don't know if this suggestion was made. But I could really use information like "20 galleries ahead, 40 galleries after" next to the information on how many galleries were found/filtered. I like to seek to specific date with new navigation and then it's a good information on how much pages/results i will comb through. Is something like that possible? Honestly, would it be easier to cache the full index from a search like "f:big breasts" and do filtering on client side? Increases traffic I assume but that can't be more expensive than serving one png file. Maybe i'm talking out of my ass, I'm not a web dev.

Quick idea about "bookmarks"
For each Tagset, just remember the GID on server side for "Watched" browsing, and start from that page by default while jump to first page navigation is fast and easy.

The addition of the 'or' function and the search only by exclusions are very helpful and very welcome, indeed.

It feels like the only thing missing now is the exclusion of the namespaces, any information if it will/can be implemented too?

It feels like the only thing missing now is the exclusion of the namespaces, any information if it will/can be implemented too?

I don't think that would be particularly useful, at least not enough to justify the effort of implementing it. The only real use case I can think of is looking for yuri and yaoi since those are the only things that wouldn't have tags in the "wrong" namespace, but you can already do that with the males/females only tag.