I’d like tags, but they’d have to be something different than just communities / categories, since that’s already what communities are for.

I’ve build multiple CMS like systems. and how I’ve implemented tags before, and liked the most was as a node tree - Since a lot of the comments are focused on NSFW, to illustrate an example:

• SFW
• NSFW
  • NSFW/Porn
    • NSFW/Porn/Straight
    • NSFW/Porn/Gay
  • NSFW/Gore

This allows users to use tags as a sort of searching mechanism with an hierarchy, and fine-tune how specific they want to search for a specific thing. Do you want all NSFW stuff, or something more specific.

The downside is that it could get complicated to maintain a good tag structure, plus you might run into scenarios where 1 subtag might fall under more categories. In that case a “Parent 1-x> Child tree” doesn’t work anymore, and you’ll end up making an “Parent x-x> Child structure” - which is even more difficult to maintain

The argument against tags, is that posts are already categorized by communities. Though not everything, and not every niche thing needs it’s own community in my opinion. Look at /c/programming for example - a “general purpose community”. Just taking the top 2 posts there, you could still create a similar note-tree tag structure there like:

• Programming
  • IDEs
    • VSCode
      • VSCodium
  • Code Style
    • Tabs VS Spaces

These tags could still be “communities”, but communities are non-hierarchical, and at what point to we really need an extreme niche “Tabs VS Spaces” community? If there would be a tag system like this, people could select the “Code Style” tag, and see posts under that tag plus all child tags.

This is just an idea for tag structuring, the concepts of ACLs of “who can make these tags” and “who can move around tags” or “who can append new child tags” - and “Introducing new child tags could require reordering the parent content into those tags” is an whole other discussion