When a user makes a post and someone wants to reply to the post, the “Reply” arrow as you show above means you are replying to that particular person’s post. The other Reply button is to reply to the topic. To reply privately, you would send the person a PM (Private Message). To do this, after clicking on the reply button at the bottom right of the post you want to reply to and the editor pops up, click on the Reply arrow by the user’s avatar - as your image shows. A menu will pop up giving the option to send a private message to that user.
If you have a “How-to” category for your forum, you can create a Wiki post that can be added to from time to time explaining details such as this. Or you can create a new topic under this category for a more “individualized” way of explaining things. Instead of a “How-to” category, you can use a FAQ category to assist your users. But getting them to read such categories is another task altogether… your “side rant.”
It’s nice that you could do that for your users. I have to admit that there are some that seem to need to be held by the hand as they’re walked through. I’ve seen similar tutorials for m8software. The developer made some really nice tutorials… walking users slowly through them with his voice explanation as he went through how to do things. That was really going all out for his software users. Kind of like the old DOS help files that literally explained what each function does, how to use it (and any switches), and how to troubleshoot it… and without having to be online. Which makes me laugh when someone can’t connect, goes to Windows “help” to troubleshoot the problem and Windows tries to connect - because MS’s help files are only online now.
I would be inclined to pin a topic that says something like ‘this is a public forum, unless you create a new personal message, you are relying publicly’ or similar
Or maybe don’t worry about this case too much? I think for most people who use forums it’s pretty clear that hitting reply in a forum topic will lead to a reply being posted in the topic, to everyone who has access to that topic. For those who are surprised by this, they will learn as soon as they save their reply.
@sjmscott How many people have complained about this in your community? It has never come up in my community before and we’ve been using discourse for 5 years.
5-6 users have complained that they don’t know when something will be a public or private reply. We are a mostly in-person community and many are over 60.
I use the Personal Message Bubbles theme component to make it very clear visually when someone is using a DM/PM and when they’re using a normal topic post. It seems to help reduce confusion.
Ahhh, maybe that’s the feature request then, when in a PM, the Reply button should always say Message like that. I know @osama is working on making the composer editor glyph at upper left more dynamic
… can you take this change to the submit button as well, please?
It seems like the submit button for replying to private messages has been changed as well. This means we could customize the text of the submit button for posts without affecting the messages composer. We could change “Reply” to something more explicit like “Post Reply” or “Reply Publicly”.
I’m not fully convinced that this entirely solves the original issue, though. When replying to a specific post, the row at the top of the composer still looks like you’re sending a reply to a person rather than the community. The button where you can change the type of post/reply is still hardly identifiable as a button.
I’d strongly oppose such a change, as it’s visually noisy. The outline sufficiently conveys a button, and now that the icon changes more for each post type, the dynamic nature of the button is illustrated more vividly:
What Discourse could do, for new users, is pop up a small education panel (unless you opted out at sign up) that explains what the button is, and what it is for, cc @tobiaseigen. It’s another example of just-in-time education, though IMO a bit of a weak one as this is meant to be advanced user functionality.