watsit said:
That would cause difficulty finding consensual and non-consensual posts, then. If you want to blacklist non-consensual posts, you couldn't just blacklist forced for instance, because some may also be consensual_(lore). If you want to search for non-stuff, you couldn't just search for forced either. It would also mean posts like post #1205088 wouldn't be tagged consensual_(lore) because it's not and shouldn't be tagged forced/non-con, even though that seems to be the kind of case it's trying to cover (even if forced is changed to not indicate non-con anymore, then we're back to presuming consent, and consensual_(lore) is still unneeded as there would be no tags indicating non-consent to contradict it).IMO, all the consent-related tags should be together, whether it's as general questionable_consent/forced tags, or lore dubious_consent_(lore)/non-consensual_(lore) tags. And while I can see the argument for making them lore tags, since it's hard to really "see" (non-)consent, it is occasionally possible, like with post #3062567. And splitting them between general and lore tags would make them unwieldy for their purpose.
Genuine apology for quoting a two year old post, but this is the most pertinent place I could find to chime in, since I asked this a little while ago in the "Do we have a tag for that" thread. If this discussion was picked up elsewhere or a final verdict was dropped (couldn't find in a search), let me know and I'll take a look.
I'd genuinely appreciate a lore tag for cases where characters are nonconsenting without satisfying TWYS, for people like me who would really benefit from the ability to blacklist it. It's most common in comics/pools or other sequences, but sometimes also in included stories that go along with an image. Especially in cases where a character is drugged/coerced such that TWYS would imply the acts were actively consensual (but the character is unable to consent). Blacklisting forced and related tags removes most of this, but sometimes a few images from a pool/sequence "leak through" as a result of there being no lore tag.
For instance, I found post #4134746 in a search recently and really enjoyed it out of context, and wanted to read the rest of the pool until I realized that the context was, uh, really bleak/genocide-y (not to invalidate people who enjoy the fiction). On a good day, I just blacklist the artist and move on (blacklisting pools isn't possible AFAIK, and blacklisting all posts piecemeal isn't practical for large pools). On a bad day, it can lead to an anxiety attack that'll cost me some sleep. I understand this ain't the average person's experience.
Here are some other examples. These are all forced-fem since it's the most common culprit here, but you get the idea--even though in context the characters involved aren't consenting or are unable to provide valid consent, the drugged/coerced characters would be considered consenting by TWYS standards. pool:26542 pool:27483 pool:26598
There are a lot of challenges involved, mostly with where to draw the line on what's "appropriate evidence"--I'd say that it's reasonable to draw the line at public stories/descriptions directly paired with the public post as well as any images that are related to it in a comic/sequence, without factoring in deeper lore than that (since that opens up a whole can of worms for debate, such as whether the artist's canon applies to the image, etc.)
I know that there's an issue of ergonomics if there was a split between nonconsentual as a lore and non-lore tag, but I also think it makes sense to keep the non-lore tag as some people only care if the nonconsent is explicitly present (especially those seeking noncon content). Perhaps the lore tag should be named differently to distinguish it as being based on the context of the image itself? "contextually_nonconsensual_(lore)". Kind of a mouthful, but something like that is what I'd really appreciate.
IMO the lore tag would be here to serve people who want to blacklist the content, far more than those interested in actively searching for it (they'd probably prefer to search directly for forced). Hope I did an OK job of explaining my position on it--thanks for reading.
