• 1 Post
  • 6 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle


    1. Choose an instance where the rules don’t forbid the content you want to post. If you’re looking for exposure of your own art, you’ll particularly want to avoid choosing an instance that has onerous rules. (One example of such a rule might be that porn needs to be posted as “unlisted” or followers-only.)
    2. Mark the media as sensitive. How you do this will depend on what interface/client you’re using.
    3. Use the “content warning” feature. This is not a place for a full description. Instead, imagine it from from the perspective of someone who would not want to see it. What keywords or descriptors would be useful to allow them to know that they shouldn’t click to show it? (A useful minimum would be something to indicate that it’s illustrated or RL, that it’s furry or feral or whatever, the apparent sexes of the characters, and any extreme fetishes depicted.)


  • 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.