Topic: [Feature/Denied] Blacklist doesn't work with set metatags

Posted under Site Bug Reports & Feature Requests

This topic has been locked.

Bug overview description.

Can't blacklist metatags for sets. I have a couple intended uses for this. One of them being a case-by-case blacklist.

(I also can't blacklist fav:hungryman, which I would like to do to reduce clutter)

What part(s) of the site page(s) are affected?

search / blacklist

What is the expected behavior?

equiv: -set:hmblacklist

What actual behavior is given instead?

equiv:

Time of incident (if applicable).

N/A

Can you reproduce the bug every time?

Yes.

What steps did you take to replicate this bug?

1. Make a set (hmblacklist) (it's private)
2. add set:hmblacklist to blacklist
3. find a bad pic (e.g. what order:score)
4. Add a pic to the set

Example*: post #378180

5. Double-check pic was added, refresh and re-search.
6. Pic is still there.

  • note: Pic was algorithmically selected to remain impartial.

Errors or other messages returned (if any).

N/A

Updated by KiraNoot

Lots of meta-tags don't work with the blacklist, and the blacklist code is a mess so I doubt it's gonna change anytime soon.

Updated by anonymous

This requires sending you the list of sets that every image is in. In a practical sense, it isn't feasible to do this. It's the same reason that the blacklist doesn't have a large number of metatags, as it means looking up large amounts of data and sending it to the client on each request.

Updated by anonymous

  • 1