I’ve had a request for the ability to add tags to topics when posting by email. This could work by adding a line as follows starting with tags: and then a comma separated list.
tags: tag1, tag2, tag3
I can see potential for difficulty, e.g. because there is no autocomplete people won’t know tags that are already being used and create duplicates, but I also think it can be quite powerful and help people to indicate organization they’d like without having to log in - and in my community many people just want to stay in their email.
We (@mcwumbly and I) would really benefit from a feature like this also. Was anything ever implemented that enables tagging topics that are created via email?
I’m with you, Jeff. My opinion has changed since posting this request back in the day. Let’s keep it simple, and let the moderators garden and fix tags etc. If people want to indicate in their message where it should go that’s fine too.
Here are some thoughts to address the risks that you identified:
The feature should respect that tags site settings, including “minimum trust level to create tags” If that is higher than the user’s trust level, then the tag would just get dropped if it doesn’t exist (which could be due to a typo).
If the user’s trust level allows them to create tags, then the new tag would be created (which could be a misspelling).
Yes, the chance of these errors is higher without immediate feedback, but on the other hand, this is a pretty “advanced” feature anyway, so I wouldn’t expect a huge onslaught of tagging mayhem were it to be added.
It’s a pain in the behind to implement properly (allowing for localization and some leniency with format), a feature that is impossible to discover and dealing with edge cases is hard.
That said, I don’t see why not allow the community to send through a well specified PR, cause it is kind of important for mailing list parity.
Several proposals were made from the original “add a line starting with tags: followed by a comma separated list of tags” to use x+tag@forum.example. Although I like the first one, since the second one is bound to break existing group and categories email-in configurations, I also understand the difficulty of having to deal with tagging errors.