Posted under Bugs & Features
It just seems like an odd contradiction that danbooru acknowledges that something like guro isn't desirable to see for most people, and makes it the default to hide these posts from search. Yet if you browse with the WASD keys, there isn't any way to skip or even blur them, as far as I can tell.
This is equally as annoying when it comes to navigating for gardening purposes and you end up on a banned post's page because banned posts break navigation. I can see why it wouldn't do that for blacklisted posts since blacklist hiding is more visual than functional (they still get paginated and all) but also agree on the front that... I don't want to be navigating and suddenly come across something terrifying, since I blacklisted it for a reason.
At present, no way to filter out blacklisted posts in A-D navigation that I know of. Builders can strap their long line of blacklists to the search but even that's not particularly intuitive.
WRS said:
At present, no way to filter out blacklisted posts in A-D navigation that I know of. Builders can strap their long line of blacklists to the search but even that's not particularly intuitive.
Does strapping your blacklist to the search eat up the 6 tag limit? Or is it a different field.
Yeah, it does. By "strap" I meant adding their entire blacklists as negations to the search. So for every line... add a "-" before the blacklisted tag and then put it into the search bar. This is an issue that affects everyone - less so Platinum and Builders due to unlimited tag searching but incredibly unintuitive.
saltsort said:
Does strapping your blacklist to the search eat up the 6 tag limit? Or is it a different field.
Builders have no limit (see help:users), so in that case it works to just add the blacklist to the search, but for gold and member levels this isn't a viable solution unfortunately.
saltsort said:
I'm curious, is this removed post = broken navigation issue in a queue somewhere to be worked on, but is just low priority? Or are bugs just generally not fixed.
It's something that can be worked around (except for pool navigation) by appending -status:banned to the end of any search query. This is a free metatag so it doesn't affect the search limit.
Related: topic #29539
Ylimegirl said:
It's something that can be worked around (except for pool navigation) by appending
-status:bannedto the end of any search query. This is a free metatag so it doesn't affect the search limit.Related: topic #29539
Thanks for the tip, this seems like the solution.
