Can you do it?

I'll answer my own question and say no because I still see my favorites pop up when searching (ex: dragon) and I'd rather not have to spend a tag on removing my favorites when I could add it to the blacklist without a second thought.

Of course, unless I'm doing it wrong and you are getting a different result, I'm curious as to why you can't blacklist your favorites.

...Why would you want to blacklist your favs o_O. Also kind of makes sense: assume that you hate cub art, but before you blacklist it you find ONE cub pic that you absolutly love, and fav it. You have obviously said that 'I love this picture' and it makes sense that that's prioritized above 'I generally don't like this theme on posts'. Atleast that makes sense to me.

Many metatags don't work on the blacklist, including this one. Sorry.

MyNameIsOver20charac said:
...Why would you want to blacklist your favs o_O. Also kind of makes sense: assume that you hate cub art, but before you blacklist it you find ONE cub pic that you absolutly love, and fav it. You have obviously said that 'I love this picture' and it makes sense that that's prioritized above 'I generally don't like this theme on posts'. Atleast that makes sense to me.

If fav:username or voted:me could be blacklisted, I could use it to not see any of my 129,068 favorites when I do a search.

MyNameIsOver20charac said:
...Why would you want to blacklist your favs o_O.

Say I'm searching through random images with my favorites scattered about. Instead of including the tag '-fav:Mdf' and hiding my favorites that way, I could blacklist it to get the same result without needing to use one of the six or eight tags that members are allowed to search at a time.

If I really wanted to see it, just check the number of blacklisted posts in the sidebar, then 'toggle blacklist'.

Lance_Armstrong said:
Many metatags don't work on the blacklist, including this one. Sorry.

Bleh, that bites, any idea as to why?

Mdf said:
Bleh, that bites, any idea as to why?

Dirty messy code probably. They have to be made to work on a case by case basis.

Isn't it also the case that the data necessary to do fav: filtering is not present in the post/index pages to begin with?

For example, here's the html for the item currently at the front of post/index/ :

<img alt="2015 absurd_res anthro armband balls bdsm bear black_and_white bondage bound bracelet canine claws collar cum cum_in_mouth cum_inside cum_on_face dialogue digital_drawing_(artwork) digital_media_(artwork) domination duo english_text erection fellatio fur hi_res jewelry male male/male male_domination mammal monochrome musclegut muscular muscular_male nipples nude oral overweight overweight_male penis pipe plaguedobsession sex simple_background smoke smoking smoking_pipe spiked_collar spikes text wolf wrist_cuff

Rating: Explicit
Score: 1
User: meowmcmeow
Date: February 16, 2018" class="preview has-children pending" id="i1458129"
src="https://static1.e621.net/data/preview/9b/f6/9bf6d9d235452e886577dad355a037c5.jpg"
title="" style="" width="150" height="132">

(this already was fav'd by one user when I copied this HTML)

tags, rating, score, user, date, status, id, md5. Not image width or height, or total pixel count, but possibly (approximate) image aspect ratio.

savageorange said:
Isn't it also the case that the data necessary to do fav: filtering is not present in the post/index pages to begin with?

For example, here's the html for the item currently at the front of post/index/ :

<img alt="2015 absurd_res anthro armband balls bdsm bear black_and_white bondage bound bracelet canine claws collar cum cum_in_mouth cum_inside cum_on_face dialogue digital_drawing_(artwork) digital_media_(artwork) domination duo english_text erection fellatio fur hi_res jewelry male male/male male_domination mammal monochrome musclegut muscular muscular_male nipples nude oral overweight overweight_male penis pipe plaguedobsession sex simple_background smoke smoking smoking_pipe spiked_collar spikes text wolf wrist_cuff

Rating: Explicit
Score: 1
User: meowmcmeow
Date: February 16, 2018" class="preview has-children pending" id="i1458129"
src="https://static1.e621.net/data/preview/9b/f6/9bf6d9d235452e886577dad355a037c5.jpg"
title="" style="" width="150" height="132">

(this already was fav'd by one user when I copied this HTML)

tags, rating, score, user, date, status, id, md5. Not image width or height, or total pixel count, but possibly (approximate) image aspect ratio.

This is the closest to the right answer. The data is not present, and pulling it in is expensive. I'm amazed we even allow for filtering on favorites at all, and that when you do that it actually works as fast as it does.

So it isn't a sloppy codebase thing, but a "this is way too much information" case.

Even if it was added it would add a huge amount of extra information to send, and the only thing you are interested in is if you are in the list in 99% of cases.

It can be done with virtually zero performance hit.

Just save favs on the client side in the local storage and filter results based on that data on the client side too. Desync would be an issue, but a button to sync favs could be added to user prefs and/or favs could be synced every 50 requests or so. Overall, it would work good enough and wouldn't cause any performance issues.

The only drawback is that nobody is going to waste so much time on a feature which only one user needs. 😁

KinkyGlutamate said:
It can be done with virtually zero performance hit.

Just save favs on the client side in the local storage and filter results based on that data on the client side too. Desync would be an issue, but a button to sync favs could be added to user prefs and/or favs could be synced every 50 requests or so. Overall, it would work good enough and wouldn't cause any performance issues.

The only drawback is that nobody is going to waste so much time on a feature which only one user needs. 

I am sure that comparing ~150k favorite ids against each post visible will have zero performance impact. If done as a map to prevent iteration I'm sure it will consume no memory either. :P

KinkyGlutamate said:
The only drawback is that nobody is going to waste so much time on a feature which only one user needs. 

That's where you're wrong.

Here's a short little userscript that I whipped up to do this. It works on my machine™. Haven't tried it on anyone with > 2500 fav's so I don't know what its performance will be, or if it can store all of the data.

https://gist.github.com/Sasquire/7ffacf92dca2bcd5cc6eccf349f1c41a