[deleted]
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)
bloopernova@programming.dev 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 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 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.