Don’t repost my comment onto github issue 317, I’ve commented there already.
A tagging is something that would be very nice to have and I’m in full support of it. Anyways here are the parts that I’d like to see implemented:
- Communities can have inbuilt tags that apply to every post
- Users can add tags of their own to a post
- There should be reasonable limits to how many tags can be placed and federate (I suggest 5 of each type)
- Communities should optionally have a filter list of what tags are permitted to be assigned and anything outside of that is discarded from the post
- Instances can maintain a list of “popular tags in the last day” etc. (a /trending page)
- The endpoint for aggregating local, subscribed and Fediverse posts by tag is a big feature and should be prioritized. e.g. server.com/t/gaming
- An endpoint for filtering posts by tag is desirable: server.com/c/community/t/discussion for example. This could be implemented similarly but separately as a flair, possibly.
- Tags should be a separate field entirely to the post body if possible, otherwise they should exclusively be written at the end of the body, to avoid parts of the body text incorrectly picked up as a tag
- An instance’s slur filter should apply to the tags
- Users should have the option to not display tags
- Backwards compatibility doesn’t have to be perfect but should be kept in mind (e.g. can the tagged and untagged versions of lemmy still federate, etc.)
- How tags on Lemmy will federate and display on other ActivityPub servers is a consideration.
I’ll add: I think having a limit on number of tags, not just the number displayed is important, to ensure people actually curate their topics correctly, it limits stupid tags like #lol that you’d see on tumblr and it prevents bots that tag everything with 100 tags from appearing everywhere.
You’d love something like misskey…