COPY: improve 'dominating_topic' and 'get_a_room' warnings

approved
#1

COPY: improve ‘dominating_topic’ and ‘get_a_room’ warnings

cf. How to suppress the warning that a user is contributing too much to a topic - support - Discourse Meta

diff --git a/config/locales/server.en.yml b/config/locales/server.en.yml
index dca7552..ac6b045 100644
--- a/config/locales/server.en.yml
+++ b/config/locales/server.en.yml
@@ -430,16 +430,16 @@ en:
 
       This topic is clearly important to you – you've posted more than %{percent}% of the replies here.
 
-      Are you sure you’re providing adequate time for other people to share their points of view, too?
+      It could be even better if you got other people to share their points of view, too. Give it a shot and invite them over!
 
     get_a_room: |
-      ### Consider replying to more people
+      ### Invite others to get involved and reply too
 
-      You’ve already replied %{count} times to @%{reply_username} in this particular topic.
+      You’ve replied %{count} times to @%{reply_username} in this particular topic!
 
-      Have you considered replying to *other* people in the discussion, too? A great discussion involves many voices and perspectives.
+      A great discussion involves many voices and perspectives. Can you get anybody else involved? Give it a shot!
 
-      If you’d like to continue your conversation with this particular user at length, [send them a personal message](%{base_path}/u/%{reply_username}).
+      And don't forget, if you’d like to continue your conversation with this particular user at length outside of public view, [send them a personal message](/u/%{reply_username}).
 
     too_many_replies: |
       ### You have reached the reply limit for this topic

GitHub sha: a0df6761

#2

This commit has been mentioned on Discourse Meta. There might be relevant details there:

#3

hmm did we break subfolder with the bottom change to remove {base_path} @ZogStriP

1 Like
Follow Up #4
#6

probably we will get it sorted out.

#7

Yup, thanks to @gschlager, the build failed after that commit and I immediately fixed it

3 Likes
Approved #8