# My users think a reply will be a private reply
**URL:** https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305
**Category:** UX
**Created:** [8월 31, 2019, 6:31오후 UTC](https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305 "2019-08-31T18:31:51Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@sjmscott](https://meta.discourse.org/u/sjmscott)
#### Post date: [8월 31, 2019, 6:31오후 UTC](https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305/1 "2019-08-31T18:31:51Z")
> [@Reply to Topic vs. Reply to Last Post](https://meta.discourse.org/t/reply-to-topic-vs-reply-to-last-post/103453/4):
>
> Just wondering if perhaps Discourse has split the js.topic.reply.title so we can easily rename the two Reply buttons to Reply to User and Reply to Topic?
My users are very confused by the two different reply buttons. In particular, many users think that when they see this. . .
they think that it is going to be a private reply.
I’d hate to do it, but I think there would be more clarity if I was able to add “Public Reply to User” or “Public Reply to Topic”
# Update
I’m playing around with bother of these options, but I dislike both
# Side Rant
I LOVE Discourse, but I’m SO tired of trying to train users.
---
### Author:  [@JimPas](https://meta.discourse.org/u/JimPas)
#### Post date: [8월 31, 2019, 7:00오후 UTC](https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305/2 "2019-08-31T19:00:48Z")
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.”
---
### Author:  [@sjmscott](https://meta.discourse.org/u/sjmscott)
#### Post date: [8월 31, 2019, 8:59오후 UTC](https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305/3 "2019-08-31T20:59:00Z")
> [@Reply to Topic vs. Reply to Last Post](https://meta.discourse.org/t/reply-to-topic-vs-reply-to-last-post/103453/9):
>
> 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
Yep, I have tons of tutorial videos and instructions. Some of my
“digital immigrants” with the new-fangled Discourse.
Here is a tutorial that I made to help solve the problem. Having everything redacted for this forum makes it difficult to read.
---
### Author:  [@JimPas](https://meta.discourse.org/u/JimPas)
#### Post date: [8월 31, 2019, 10:10오후 UTC](https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305/4 "2019-08-31T22:10:12Z")
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. 🙄
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [9월 1, 2019, 4:24오전 UTC](https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305/5 "2019-09-01T04:24:19Z")
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
---
### Author:  [@JimPas](https://meta.discourse.org/u/JimPas)
#### Post date: [9월 1, 2019, 4:46오전 UTC](https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305/6 "2019-09-01T04:46:06Z")
Or maybe a sub-banner? That would take up less real estate I think. Either way is better than nothing since most people talk before they think anyway. 😇 🙄
---
### Author:  [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [9월 1, 2019, 5:01오후 UTC](https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305/7 "2019-09-01T17:01:07Z")
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.
---
### Author:  [@sjmscott](https://meta.discourse.org/u/sjmscott)
#### Post date: [9월 2, 2019, 11:43오후 UTC](https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305/8 "2019-09-02T23:43:17Z")
> [@tobiaseigen](#):
>
> 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.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [9월 2, 2019, 11:50오후 UTC](https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305/9 "2019-09-02T23:50:54Z")
Assume all replies will be public unless you see strong visual indications otherwise… on Discourse this is primarily the envelope glyph.
This brings up a good point, when composing a message, the reply glyph at upper left should arguably change to the PM glyph
But the “actually post this” button has the PM glyph also, so…
---
### Author:  [@tomtjes](https://meta.discourse.org/u/tomtjes)
#### Post date: [3월 17, 2021, 3:51오후 UTC](https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305/10 "2021-03-17T15:51:13Z")
제 사이트에서도 동일한 문제가 발생했습니다.
> [@sjmscott](#):
>
> 특히 많은 사용자가 이것을 보면…
>
> 
>
> 비공개 답장이 될 것이라고 생각합니다.
그 외에도, 비공개 메시지 교환 시 편집기가 정확히 똑같이 보인다는 점이 떠올랐습니다:
해결책으로는 게시 메뉴에 추가 버튼을 넣어 공개적으로 답장할지 비공개로 답장할지 선택할 수 있게 하는 방법이 있습니다. 이런 아이콘이 적합할 수 있습니다.
[https://www.flaticon.com/free-icon/email\_480334?term=reply&page=1&position=87&page=1&position=87&related\_id=480334&origin=search](https://www.flaticon.com/free-icon/email_480334?term=reply&page=1&position=87&page=1&position=87&related_id=480334&origin=search)
또 다른 아이디어는 편집기 하단에 “비공개로 답장” 버튼을 추가하는 것입니다.
---
### Author:  [@Jonathan5](https://meta.discourse.org/u/Jonathan5)
#### Post date: [3월 17, 2021, 5:41오후 UTC](https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305/11 "2021-03-17T17:41:44Z")
이 모든 버튼의 텍스트를 편집할 수 있습니다.
다만, "답장"이라는 텍스트가 약 6개나 있어서 서로를 구별하기가 어렵습니다.
---
### Author:  [@downey](https://meta.discourse.org/u/downey)
#### Post date: [3월 17, 2021, 7:03오후 UTC](https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305/12 "2021-03-17T19:03:02Z")
[개인 메시지 버블](https://meta.discourse.org/t/personal-message-bubbles/147994) 테마 구성 요소를 사용하여 누군가가 DM/PM을 사용 중인지, 아니면 일반 토픽 게시물을 작성 중인지 시각적으로 매우 명확하게 구분합니다. 혼란을 줄이는 데 도움이 되는 것 같습니다.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [3월 18, 2021, 6:59오후 UTC](https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305/13 "2021-03-18T18:59:39Z")
> [@tomtjes](#):
>
> 비공개 메시지 교환에서 편집기는 완전히 똑같아 보입니다:
그렇지 않습니다. 속삭임과 메시지 모두에서 제출 버튼을 변경했습니다:
 
속삭임의 경우 제출 버튼에 **속삭임** 이라고 표시되고, 메시지의 경우 **메시지** 라고 표시됩니다 – 그리고 글리프도 다릅니다.
---
### Author:  [@riking](https://meta.discourse.org/u/riking)
#### Post date: [3월 18, 2021, 7:13오후 UTC](https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305/14 "2021-03-18T19:13:26Z")
그들은 총리에게 보낸 2번째 또는 3번째 답변에 대해 이야기하고 있으며, 해당 답변에는 일반적인 답변 기호가 있습니다.
이 경우, 해당 주제의 가시성을 확인해야 합니다.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [3월 18, 2021, 7:51오후 UTC](https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305/15 "2021-03-18T19:51:22Z")
아, 그러면 그게 기능 요청이군요. 개인 메시지(PM)에서 답글 버튼을 누를 때, 버튼에 항상 "메시지"라고 표시되도록 해야 한다는 거죠. @osama 님이 왼쪽 위 작문 편집기 글리프를 더 동적으로 만드는 작업을 하고 있다는 건 알고 있습니다.
.. 이 변경 사항을 제출 버튼에도 적용해 주시겠어요?
---
### Author:  [@Osama](https://meta.discourse.org/u/Osama)
#### Post date: [3월 19, 2021, 6:52오후 UTC](https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305/17 "2021-03-19T18:52:05Z")
다음에서 수행됩니다:
>
>
> See a video of the change in the PR: https://github.com/discourse/discourse/pull…/12449.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [3월 19, 2021, 7:26오후 UTC](https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305/18 "2021-03-19T19:26:07Z")
좋습니다, 혼란을 줄여줄 수 있는 훌륭한 변경 사항입니다. @sjmscott 님, 상기시켜 주셔서 감사합니다 🍻
---
### Author:  [@tomtjes](https://meta.discourse.org/u/tomtjes)
#### Post date: [3월 19, 2021, 10:00오후 UTC](https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305/19 "2021-03-19T22:00:27Z")
정말 좋습니다, 감사합니다!
개인 메시지에 답글을 보내는 제출 버튼도 변경된 것 같습니다. 👍 이렇게 하면 메시지 작성기에 영향을 주지 않고 게시물의 제출 버튼 텍스트를 사용자 정의할 수 있습니다. "답글"을 “답글 게시” 또는 "공개 답글"처럼 더 명확한 표현으로 변경할 수 있습니다.
다만, 이것이 원래 문제를 완전히 해결하는지에 대해서는 아직 확신이 서지 않습니다. 특정 게시물에 답글을 작성할 때, 작성기 상단의 줄은 여전히 커뮤니티가 아니라 특정 사람에게 답글을 보내는 것처럼 보입니다. 게시물/답글 유형을 변경할 수 있는 버튼도 여전히 버튼으로 식별하기가 어렵습니다.
---
### Author:  [@renato](https://meta.discourse.org/u/renato)
#### Post date: [3월 19, 2021, 10:13오후 UTC](https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305/20 "2021-03-19T22:13:27Z")
> [@tomtjes](#):
>
> 게시물/답글 유형을 변경할 수 있는 버튼은 여전히 버튼임을 알아보기 어렵습니다.
아래로 향한 캐럿 아이콘 ⌄와 같은 간단한 시각적 단서가 이 요소를 드롭다운으로 식별하는 데 도움이 될 것이라고 생각합니다.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [3월 20, 2021, 5:16오전 UTC](https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305/21 "2021-03-20T05:16:18Z")
이러한 변경에 대해 강력히 반대합니다. 시각적으로 노이즈가 많기 때문입니다. 아웃라인만으로도 버튼임을 충분히 전달할 수 있으며, 이제 각 게시물 유형에 따라 아이콘이 더 다양하게 변하므로 버튼의 동적인 특성이 더 생생하게 드러납니다:
Discourse가 신규 사용자를 위해 할 수 있는 일은, 가입 시 선택적으로 비활성화하지 않았다면 버튼이 무엇이며 어떤 용도로 사용되는지를 설명하는 작은 교육 패널을 팝업으로 표시하는 것입니다. @tobiaseigen님 참고 바랍니다. 이는 적시에 교육(just-in-time education)의 또 다른 예시이지만, 이 기능이 고급 사용자용 기능으로 의도된 점을 고려하면 제 생각에는 다소 약한 예시입니다.
[Next page](https://meta.discourse.org/t/my-users-think-a-reply-will-be-a-private-reply/127305.md?page=2)