[X] My Assistant

weak:tag: not working isn't a parsing error, it replaces tag: .

No, it doesn't.

searching for weak:tag:<tag name>
should (according to the new wiki, where there is even an example) search the weak <tag name> in all tagspaces (instead of only searchin in the one explicited, like "male" or "female" or whatever).

But instead it simply returns all existing galleries !

weak: and tag: are qualifiers, not keywords. The original post says you can use weak: in front of a keyword. It doesn't say anything about using it in front of a qualifier.

So the wiki is wrong. What I meant is that there's nothing in the original post that says you can use weak:tag. It says to use it instead of tag:.

~tag:exhibitionism ~weak:exhibitionism does give an error message: "You cannot combine OR searches for weak and strong tags."
weak:tag: gives undefined and varying results depending on the rest of the query.

Both "electric shocks$" and weak:"electric shocks$" work for me.

I believe all the electric shocks galleries can be found across these two searches, unless it's not tagged, only in the title.

You can also make those searches with the 'browse expunged galleries' option turned on for some more results.

This post has been edited by romanicyte: Nov 19 2022, 05:14

Yes. You can do weak:m:"electric shocks$" or weak:f:"electric shocks$", and weak:"electric shocks$" returns all the results across both namespaces. It doesn't require tag:, it replaces tag:.

weak: and tag: are qualifiers, not keywords. The original post says you can use weak: in front of a keyword. It doesn't say anything about using it in front of a qualifier.

So the wiki is wrong. What I meant is that there's nothing in the original post that says you can use weak:tag. It says to use it instead of tag:.

~tag:exhibitionism ~weak:exhibitionism does give an error message: "You cannot combine OR searches for weak and strong tags."
weak:tag: gives undefined and varying results depending on the rest of the query.

Yes, the Wiki is wrong, in the sense that the behaviour described in the Wiki is not what the search engine does now.
That could be the cause the Wiki description is wrong (and I have already posted in the Wiki bug thread about it) OR it may be that the Wiki is theoretically right, but the combination of these two qualifiers doesn't work as intended.

The result is consistent, not varying; using qualifiers "weak:tag:" before ANY tag will return always all the galleries, notwithstanding what follows. Only the Categories selected are respected (obviously, since they are applied before everything else).

"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."

It's not intended to ever combine those qualifiers. It's redundant to do so.

weak:tag:foo returns all galleries.
~bar ~weak:tag:foo returns 258 results

If the empty string always matches all galleries, then adding OR <empty string> to a query should also return all galleries.
It does not, therefore the behavior is inconsistent.

The only bug is the parser not recognizing weak:tag: as unintended input and printing an error about it. It looks like any stacking of qualifiers behaves the same way, e.g. tag:tag:tag:foo.

This post has been edited by Necromusume: Nov 19 2022, 05:35

"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."

It's not intended to ever combine those qualifiers. It's redundant to do so.

weak:tag:foo returns all galleries.
~bar ~weak:tag:foo returns 258 results

If the empty string always matches all galleries, then adding OR <empty string> to a query should also return all galleries.
It does not, therefore the behavior is inconsistent.

The only bug is the parser not recognizing weak:tag: as unintended input and printing an error about it.

If it was redundant , then using "weak:foo" or using "weak:tag:foo" would give the same result. This is exactly what the wiki says, but it's not what happens; the first gives the relevant galleries, the second gives all the galleries. Therefore the "weak:tag:foo" string is replaed with a null string silently by the parser, before running the query. The risult of a query with the query box empty is all galleries, QED.
Also "~weak:tag:foo" returns all galleries, because it is substituted by the parser with a null string.

This happens the same in your example : the parser sees [ ~bar ~weak:tag:foo ] in the query box, and substitutes it with [ ~bar ] that gives obviously the same number of results as directly writing [ ~bar ] in the search box.

So the behaviour is completely consistent; it just is not what is described in the wiki example, and it happens silently without warnings or errors.

This post has been edited by mundomuñeca: Nov 19 2022, 05:42

[nypost.com] Sheep filmed walking in circle for 12 days straight in China

To only match gallery tags, prefix the term with a tag namespace, or tag: for all namespaces

Using weak: in front of a keyword works the same as using tag:

It's redundant because weak already searches all namespaces.

Forgive me if i'm just too much of a noob to have learned this - but it was said
" make them into active tags" - How do you do that for stuff that has weak tags? Does that require some sort of material to get a LOT of votes?

It only requires 10 power for a weak tag to become active, so generally 1-2 users' votes would be enough.
You can check your power at https://e-hentai.org/home.php.

i tried this script [github.com] https://github.com/Meldo-Megimi/EH-Page-Scrobbler

and its really good this should be implemented to the site.

There was a beta. It was rolled out slowly. Read the thread.

Than it was not a good beta test, when it became official and get a ton of shitstorm... And then you suprise this thread is full of complaining...

As I said, why not make a public beta test? Like Gmail last time, when they forced everyone to try the new look, but give chance to go back to the last design (and now forced us to use it...) and can give feedback.

If it was redundant , then using "weak:foo" or using "weak:tag:foo" would give the same result. This is exactly what the wiki says, but it's not what happens; the first gives the relevant galleries, the second gives all the galleries. Therefore the "weak:tag:foo" string is replaed with a null string silently by the parser, before running the query.

So the behaviour is completely consistent; it just is not what is described in the wiki example, and it happens silently without warnings or errors.

It probably should error out if there are unparseable or syntax-invalid terms, yeah. And while weak:tag: is redundant, I'll make the parser a bit more forgiving about redundant qualifier usage.

complaining

Maybe you should go read the things that are specifically highlighted to read before you provide your "feedback".

Edit: Disregard, my eyes are messed up at the moment so I didn't see the hyperlink indicator in the "Explanation etc" bit in the first post and assumed it was just talking about the post it was on.

My bad, yeah there were no great options, sorry bout that.

This post has been edited by Alex Denton: Nov 19 2022, 20:12

Can jump/seek be combined with search so don't have to search first?

Maybe you should go read the things that are specifically highlighted to read before you provide your "feedback".

Maybe you should read some suggestions and not saying others to read through 70 pages.

Can jump/seek be combined with search so don't have to search first?

I suppose it would make sense to add a date field in the Advanced Search pane to skip a step, I'll look into it.

Maybe you should read some suggestions and not saying others to read through 70 pages.

Those clueless ramblings, most of which were fundamental misunderstandings and all of which have been addressed in the thread already, were supposed to be "suggestions"? Maybe you should start with a dictionary and work your way up from there.

Sorry guys... I will not use the platform anymore unless the page numbers are back.
I understand your intention to make it better, always, but this time you made it REAL BAD... 3 days and nothing... so I'm quitting. Moving to HentaiFoundry, HentaiEra, DeviantArt... (IMG:[invalid] style_emoticons/default/cry.gif) (IMG:[invalid] style_emoticons/default/cry.gif) (IMG:[invalid] style_emoticons/default/cry.gif) (IMG:[invalid] style_emoticons/default/cry.gif) (IMG:[invalid] style_emoticons/default/cry.gif) (IMG:[invalid] style_emoticons/default/cry.gif) (IMG:[invalid] style_emoticons/default/cry.gif) (IMG:[invalid] style_emoticons/default/cry.gif) (IMG:[invalid] style_emoticons/default/cry.gif)

It's redundant because weak already searches all namespaces.

Yeh, I've reworded it a bit better. I made a mistake on how it works, sorry about that

So I'm guessing this update has something to do with removing the preview pic while hovering over the text? Only way to see what the pic is, is to go from Minimal to Extended. NM that is just IE messing up guess I got to use Chrome or Firefox now...

This post has been edited by microwater: Nov 19 2022, 15:09

The fuck happened to the search page.
The fuck has the "search for low power tags with one click" go...