This feature request has similar goals to another one I made, but involves the search bar instead of the blacklist. Here's the blacklist version for reference: https://e621.net/forum_topics/27292
.
.
Requested feature overview description.
Connect metatags to specific tags multiple times in a search. For example, 'connecting' a metatag to a tag by wrapping them in quotations or something like that. Say you were running a regular post-based metatag like favcount:>100, but you wanted a specific tag to only appear if it had way more than that. Let's say over 500. So you'd run a search that looks like this:
favcount:>100 "Exampletag -favcount:>500"
So everything in the result's favcounts are over 100, but that example tag only shows up if its favcount is over 500.
But the real fun would be being able to have multiple of these in a search. Such as:
favcount:>200 "exampletag1 -favcount:>600" "exampletag2 -favcount:700"
And being able to keep adding those until it caps out at 40, I guess. Hopefully everything between the quotations would just count as one. Are there plans of increasing the cap from 40? Probably greedy for asking~
By the way, I went with favcount because that seems to be a bigger number than 'score' on most posts I see. But yes, it would be cool to also be able to do this with the various other metatags if you wanted to. You'd just add quotations (or whatever you think is better) and the specific tag you're asking for.
.
.
Why would it be useful?
The first three reasons are similar to the ones I gave in the first thread; except instead of being site-wide, this time they only apply to a single search run you'd frequent.
1.) It would be great for keeping everything up to personal standards 'constant' right down to specific tags that maybe you have higher standards for.
2.) Would be really helpful if you're trying to slow the endless flow of new stuff (so you aren't behind, having to catch up too often, or wasting too much time as it is), especially if the specific tags are really common.
3.) Maybe you only use the site for a handful of tags and block everything else, but if some posts have too high a favcount/score to miss out on, you can allow those through at least.
4.) Maybe this is an easier way to 'do this kind of thing' than the blacklist version's bag of worms. Or maybe it's just as difficult. I'm not a programmer so I wouldn't know, haha.
5.) Another way it might be better than the blacklist version is while a heavy or broad blacklist can make some pages look empty, a search is going to pack the page full of whatever applies to the search. Depending on whatever images-per-page you've chosen, of course.
6.) In the blacklist version, you might not see a post you'd like until it's passed Page 1 (because that's how long it took to reach the favcount you required to see it). Since an involved search produces a page that moves slower than the default Posts page with nothing in the search bar, you're given more time to see that potential post before it passes Page 1. So it's like while jogging on a path that temporarily has a nice view of the sky, locking your speed at the perfect amount so you can enjoy the view of the sun before it sets completely. ...Yes I just compared a jogging routine to a porn browsing routine. I'm all about only soaking in the best visuals, okay?
.
.
What part(s) of the site page(s) are affected?
The search bar and all the Posts pages it's used for.
.
.
One thing I'm not sure about.
I noticed I wrote my examples the same way you'd write exceptions for tags in the blacklist. So I'm not certain if the search bar version would have the - (minus) symbol like that, because the search bar doesn't work the same way the blacklist does. But, since this is just an idea, I'll let the more experienced folks pick what makes more sense. Minus or no minus. Or neither. I dunno :P
.
.
.
EDIT:
Thanks to bitWolfy for some info on both my feature requests in this thread: https://e621.net/forum_topics/27380
Updated
