I been going through with all of these. Except Hermaphrodite. Since we have a gynomorph community and it puts hermaphrodites under it's label, I simply use gynomorph for both gyno and herms for anything containing either that I post in c/femyiff.

Never used S/G/L/B/T/I/Inc(inclusive has everyone in it). Even though those might be sorta fine to use in cases like an image with 4 or more people in a orgy or a gangbang. So we're not doing what I have been doing where I put M/M/M/M/F/G/M/M/M/A/U to represent everyone in the image. That way it could be labeled as [G Threesome],[T Threesome], [B Orgy], [Inc Orgy], [S Gangbang], [I Gangbang]

i like it and it's shorter 👌 ty 💙

Unfortunately, client-side keyword filters aren’t community or even server-specific. (Nor do they have context of when a post was made.) They’re a setting that’s global to everywhere. This makes reusing tags extremely problematic, especially when changing to drastically different meanings that are very likely to be on the opposite side of what someone might want to seek out versus avoid seeing.

Consider the following cases: I do not want to see andromorphs or gynomorphs. However, I also really don’t want to risk filtering out gay content and I don’t want to filter ambiguous characters automatically either.

I really don’t want to have to start swinging the block community hammer in order to filter out places that use G or A to mean things I absolutely do not want to see.

I believe quite strongly in promoting common-ground communities and infrastructure based on people being able to filter out what they don’t want to see in a granular way. Inverting tag meanings undermines that to an extent that I think is not justifiable.