Topic: A way to filter to posts w/o "Character" (green) tags?

Posted under General

Hi, every time I visit the site, I notice an enormous number of Pokemon posts featuring fan characters with their own character tags, but that lack the fan_character tag, making blacklisting fan_character quite useless. I initially wanted to start tagging these as I see them, and I did tag a few, but the fact they're interspersed alongside all the other Pokemon posts makes it pretty annoying to do, especially on mobile, which is my only option. Is there just a way to filter posts that have any of the character/green tags at all in my searches? Unless I missed something in the search cheatsheet, I didn't see any way to do this, so I figured I may as well ask here. This would at least make bulk tagging require far fewer click-throughs to check for the tags, even if it would still demand paying attention to when it's only official characters present.

There's also a lot of posts with fan characters with no character tags or the fan_character tag but I've given up trying to find some way to deal with those.

Additionally, is this something that falls under the domain of things appropriate to make a tag implication request for? These fan characters have their own tags, so it seems sensible to have them be associated with the tag specifically for fan characters, but I don't know if the relatively low post count but high volume of character tags would warrant something like that.

You can use chartags:0. That way you can filter out all character tags.

Updated

Watsit

Privileged

cephalopodica said:
There's also a lot of posts with fan characters with no character tags or the fan_character tag but I've given up trying to find some way to deal with those.

Aside from peoples' fursonas, many pieces of art (particularly pokemon) just contain generic one-off characters that don't have a name. Tagging these unnamed one-offs with fan_character will make the tag little more useful than searching or blacklisting tags like pokemon itself.

Though I don't really find fan_character that useful as it is. How would it be useful to tag post #4287871 with fan_character, simply because the zoroark and lucario were given names (and have some external background lore, which isn't present in the post), while not post #4961922 because the zoroark and lucario are generic and nameless (but are in a similar act)? I also find it too broad and lacking nuance when applied to species that are used in someone's own story. How could you distinguish wanderlust posts that contain canon vs fan characters to the wanderlust setting in specific, separate from them all being pokemon "fan characters" in general?

Updated

slyroon said:
You can use chartags:0 .that way you can filter out all character tags.

Thanks! Not sure how I missed that.

watsit said:
How would it be useful to tag post #4287871 with fan_character, simply because the zoroark and lucario were given names (and have some external background lore, which isn't present in the post), while not post #4961922 because the zoroark and lucario are generic and nameless (but are in a similar act)? I also find it too broad and lacking nuance when applied to species that are used in someone's own story. How could you distinguish wanderlust posts that contain canon vs fan characters to the wanderlust setting in specific, separate from them all being pokemon "fan characters" in general?

I agree for purely external lore and whatnot, I'm specifically talking about where it is present in the images, not external lore - "tag what you see" stuff, like features that deviate greatly enough from the designs to be identifiable from others of the species, or when unique names are being spoken in the piece itself. I think those, even if one-off, still belong in that tag, since they are still fan characters.

As for Wanderlust though, I have nothing as I've never even heard of that project. If anyone more knowledgable than I wants to figure that out they can. I'm more thinking of the perspective of blacklisting than for finding, so it's tough to say what the solution should be.

Updated

  • 1