Fellow Lemmy users,

Some days ago, I made a post asking for feedback on adding a tag system to Lemmy. Thank you to everyone who shared thoughts and suggestions!

After reading through the responses, I’ve written up a new RFC trying to incorporate the different ideas:

New Flexible Tag System RFC

I’ll repeat the message from last time in case someone has additional ideas to contribute.

The Lemmy development team is considering adding a new tag system that would allow us to tag posts with keywords. This could make it easier to search for and find content on Lemmy.

Before implementing this, the team would like more feedback from users.

Please share your thoughts on whether you’d find a tag system useful, and if so, how you’d want it implemented. The dev team reads all feedback and will use it to decide how to proceed.

You can comment or vote here or on the GitHub issues to provide input. You can vote on whether or not you want the feature, and give opinions on the different implementations, so we can see which proposals are most popular.

Thanks for helping shape Lemmy! This is our community, so please speak up.

Looking forward to hearing your thoughts.

Eager to get everyone’s perspectives on this proposed new feature!

  • bloopernova@programming.dev
    link
    fedilink
    English
    arrow-up
    9
    ·
    1 year ago

    If some tags can be standardized, then perhaps we can replace the catch all term “NSFW” with better descriptive terms. Like NSFL, XXX, etc etc. That might help moderators with better mod tools.

    I’m all for tags/taxonomy! I hope that others can come up with more specific moderation use cases.

    Tags based on source might help too. A post marked with “mastodon” might invoke code that cleans up the title links and hashtags, then place them in the post body.

    There may also be a benefit to per-community automatic rules that tag new contributors. Or tag comments made by spammers or known trolls.

    (I guess I should read the RFC, lol!)

    • Brazzburry@lemmy.world
      link
      fedilink
      arrow-up
      8
      arrow-down
      1
      ·
      1 year ago

      Man id just settle for nsfl/xxx. I don’t know how we got to the point where horrifying decapitation is the same as you might see a nipple. But I hate rolling those dice.

    • bloopernova@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Each one of those features I mentioned is a lot of work. I don’t want to just throw ideas out and expect them to magically happen!

      I haven’t looked at the Lemmy codebase. Are there plans for an API or extension framework? That could allow other devs to implement features while the core devs focus on performance and security.

  • SzethFriendOfNimi@lemmy.world
    link
    fedilink
    arrow-up
    7
    ·
    1 year ago

    What about having a tag class and subclass.

    So you can have something like

    notsafe.gore and notsafe.nudity and notsafe.violence

    Or info.contributor or info.some_other_info

    E.g. the top level “classes” would be somewhat standard and have a “meaning” while the subclass would be for more granular details.

    So clients/servers can just look at the first token for simple filtering (no nsfw) or more granular (I’m ok with nsfw of this but not that)