I think we are going to need this for our Discourse instance as well. I think it could work by giving it some specific context like (+1) just to be clear that it’s not someone who wants the +1 to show up as a comment. Though… maybe you don’t want people on your forum to be able to leave just +1 as a comment.
Not every feature has to be immediately self-evident (or is that actually the policy for adding features?). There can be a guide to learn advanced commands, and they can be passed on through word of mouth.
I’m not sure why you would have to use a footer for this anyway. You don’t have to do anything you don’t want to. If putting the suggestions in the footer is a bad idea, then don’t do it!
BTW, you can do sub-bullets on Discourse but there’s nothing in the UI that tells you how. In fact I would expect it to work like other software where you double up the character to make a single bullet but it turns out that’s not the case, you have to put a space before the dash.
There is something in the UI that tells you that; it is the default placeholder text in the editor that says
use Markdown or BBCode
So if you know Markdown (or BBCode), this bit of it to produce bullets is quite standard across implementations. It is like saying
use English
It is a known language.
I am not sure I like @DeanMarkTaylor’s idea of spamming every user with instructions but a help command that sent an email reply with the list of possible email commands (if you can guess what the help command is) would be OK.
Without disagreeing with your sentiment Sam, I know that once any solution is in place, I’m going to append it the instruction in our email footers, regardless. If nothing else, they may be wondering why they never got their +1 reply email back, and who knows if they put 2+2 together to see that a like had been added to the post on their behalf.
Parsing emails has proven very difficult (we get many emails which include signature and full body of the reply in the next post, and with all the languages that “me too” can be translated to, the hit & miss magic is going to include a lot of miss.
You should be reporting issues with email footers appearing in a new topic so they can be resolved.
“me too” is not a reply I see this feature supporting.
“me too” in English does not appear to be / read as a command.
This would also usually fall below the minimum post length.
Minimum post length should still be enforced after “commands” are extracted and email footers are removed.
FYI: I’ve been reporting this (email signatures appearing in posts) for several months now and providing sources of raw emails, but unfortunately no fixes have been discovered and/or successful yet despite efforts.
I don’t think trying to increase the portfolio of already-brittle email-in functionality is the right approach here. Rather, we should be trying to get people on to the web site to take full advantage of what Discourse has to offer.
Understand that it’s something to be added to the template regardless, but my anticipation is more for this as a first step toward the proposed behavior in the RFC (clicking) more so than the like-by-reply.