Every time this search filter -fav:<username> is used with fav:<username> you'll get sent (or back) to the recently uploaded page.

I am pretty sure this is a bug because they're so many other search filters that work conjointly with each other I couldn't think why these two wouldn't.

Edit: Actually I could think of one reason, why.

I just tried this and yep, it just shows you the index as if you haven't typed anything.

Just one question
post #1329431

That aside, let's take a look
inpool:true -inpool:true (no pools)
-inpool:true inpool:true (pools)
id:<50 id:<1000000 (id:s 1000000-)

Also if you fav something recent you'll notice it doesn't show up in your rather peculiar search. Reverse the search and it should show only your favs.

Hypothesis: you cannot search for the same meta-tag twice, and if you do it only looks at the last one.

MyNameIsOver20charac said:
Hypothesis: you cannot search for the same meta-tag twice, and if you do it only looks at the last one.

Confirmation: you cannot search for the same meta-tag twice, and if you do it only looks at the last one.

MyNameIsOver20charac said:
Why tho

I mean, I used to search for images that were favorited by another user but not myself when the other user had similar tastes to mine. I always did their favorite list after negating myself, though, so I still got their fav list and just didn't mind that mine popped up a few times.

fav:username -voted:me could work, as long you vote on most pics you see.

Testing with fav:Furrin_Gok -voted:me and it works quite nicely.

Furrin_Gok said:
I mean, I used to search for images that were favorited by another user but not myself when the other user had similar tastes to mine. I always did their favorite list after negating myself, though, so I still got their fav list and just didn't mind that mine popped up a few times.

-.- I didn't consider that <username> could be two different ones. Now I understand the problem.