So wack new tags don't need to be added to blacklists every time

E.g.
*_(lore) to blacklist all lore tags
or forced*
etc.

creampieguy69 said:
So wack new tags don't need to be added to blacklists every time

E.g.
*_(lore) to blacklist all lore tags
or forced*
etc.

Most "group" tags you can already get rid of the entirety of by blacklisting the root implication. All vore tags implicate Vore, all forced tags implicate Forced, all franchise character tags indicate the source franchise, yadda yadda. This seems unneeded,

votp said:
Most "group" tags you can already get rid of the entirety of by blacklisting the root implication. All vore tags implicate Vore, all forced tags implicate Forced, all franchise character tags indicate the source franchise, yadda yadda. This seems unneeded,
[/quote

votp said:
Most "group" tags you can already get rid of the entirety of by blacklisting the root implication. All vore tags implicate Vore, all forced tags implicate Forced, all franchise character tags indicate the source franchise, yadda yadda. This seems unneeded,

What about *_(lore)

Does this really not already work?

creampieguy69 said:
What about *_(lore)

Lore tags are completely informational. The presence of a lore tag doesn't change anything about what you see in the image (e.g. an ambiguous_gender character would look identical regardless of someone added a male_(lore) or female_(lore) tag). Though I do believe there's a way to search/blacklist based on the number of tags in a category, so you could blacklist when the number of lore tags is greater than 0; I just can't remember how.

I believe this feature is intentionally left out, especially due to the fact that pretty much anything that has a plausible reason to be blacklisted can be blacklisted a better way than using wildcards (like forced rather than forced*)

I don't see any possible practical reason for blacklisting tags ending with (lore) so it's really not an argument for why this feature should exist.

Since you for some reason want to do it, there's actually only 11 lore tags so it's pretty easy to add them to your blacklist. I even listed them all below for you.

nonbinary_(lore)
trans_woman_(lore)
trans_man_(lore)
maleherm_(lore)
herm_(lore)
gynomorph_(lore)
female_(lore)
andromorph_(lore)
incest_(lore)
trans_(lore)
male_(lore)

faucet said:
I believe this feature is intentionally left out, especially due to the fact that pretty much anything that has a plausible reason to be blacklisted can be blacklisted a better way than using wildcards (like forced rather than forced*)

I don't see any possible practical reason for blacklisting tags ending with (lore) so it's really not an argument for why this feature should exist.

Since you for some reason want to do it, there's actually only 11 lore tags so it's pretty easy to add them to your blacklist. I even listed them all below for you.

Ok figured I might be banned if I specified the wack tags I actually wanted to glob, so I just used examples, but they'd be

transg*
trans_*

Since the tags relating to these seem to change quite often. Globbing would futureproof my blacklist, in a sense

creampieguy69 said:
Ok figured I might be banned if I specified the wack tags I actually wanted to glob, so I just used examples, but they'd be

transg*
trans_*

Since the tags relating to these seem to change quite often. Globbing would futureproof my blacklist, in a sense

Logically, wouldn't just trans* get rid of both versions? I believe that the old tags are aliased to the current ones whenever something is changed, regardless, so if you blacklist whichever one it is now it should remove them for the future. If the tags aren't having prior names aliased when they're changed, bad tagging crew, no cookies for you.

votp said:
Logically, wouldn't just trans* get rid of both versions?

It would, but then it would also get rid of tags he might not mind and could even want, such as translucent_clothing or translated.