# Could we implement this option ...? **URL:** \ **Category:** Site Feedback\ **Created:** [August 10, 2024, 3:32pm UTC](https://boards.straightdope.com/t/could-we-implement-this-option/1005532 "2024-08-10T15:32:01Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![pjd](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/pjd/32/3009_2.png) [@pjd](https://boards.straightdope.com/u/pjd)\ **Post date:** [August 10, 2024, 3:32pm UTC](https://boards.straightdope.com/t/could-we-implement-this-option/1005532/1 "2024-08-10T15:32:01Z")
It’s a known ‘feature’ that when a post has one reply immediately following it, the reply doesn’t show the ‘replying to’ symbol (in the top right corner). This has often led to confusion about whether the reply _actually is_ a reply to the previous post, or is a reply to the original post. This thread from the Discourse Meta site appears to show how this can be cured :- > **[Replied post doesnt display as such](https://meta.discourse.org/t/replied-post-doesnt-display-as-such/214841)** > > Apparently replying to certain posts doesn’t create a “reply”-post but just a normal-looking post despite the fact that I even got a notification about a reply from someone. I cannot fully reproduce the behavior but it seems to happen more often... Maybe this should be in Site Feedback… No doubt i’ll find out soon ! ---
**Author:** ![engineer\_comp\_geek](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/engineer_comp_geek/32/504_2.png) [@engineer\_comp\_geek](https://boards.straightdope.com/u/engineer_comp_geek)\ **Post date:** [August 10, 2024, 4:16pm UTC](https://boards.straightdope.com/t/could-we-implement-this-option/1005532/2 "2024-08-10T16:16:52Z")
Moved to Site Feedback (from ATMB). And I will see if we can get this turned on. ---
**Author:** ![TriPolar](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/tripolar/32/3008_2.png) [@TriPolar](https://boards.straightdope.com/u/TriPolar)\ **Post date:** [August 10, 2024, 4:32pm UTC](https://boards.straightdope.com/t/could-we-implement-this-option/1005532/3 "2024-08-10T16:32:52Z")
Be a good idea. Requires the bare minimum of notice, just a symbol as an indicator is sufficient. ---
**Author:** ![wolfpup](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/wolfpup/32/10618_2.png) [@wolfpup](https://boards.straightdope.com/u/wolfpup)\ **Post date:** [August 10, 2024, 4:39pm UTC](https://boards.straightdope.com/t/could-we-implement-this-option/1005532/4 "2024-08-10T16:39:39Z")
This is a great idea. The ambiguity of whether a post is replying to the OP or to the immediately preceding post is a real nuisance. And worse, if you quote the immediately preceding post in full, Discourse “helpfully” removes the quote! ---
**Author:** ![Lumpy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/lumpy/32/446_2.png) [@Lumpy](https://boards.straightdope.com/u/Lumpy)\ **Post date:** [August 10, 2024, 10:19pm UTC](https://boards.straightdope.com/t/could-we-implement-this-option/1005532/5 "2024-08-10T22:19:17Z")
> [@wolfpup](#): > > This is a great idea. The ambiguity of whether a post is replying to the OP or to the immediately preceding post is a real nuisance. \<\>worse, if you quote the immediately preceding post in full, Discourse “helpfully” removes the quote! Unless you edit the quote if only to remove a punctuation mark, because someone once upon a time decided that Discourse shouldn’t have verbatim repeats of posts. ---
**Author:** ![Thudlow\_Boink](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/thudlow_boink/32/320_2.png) [@Thudlow\_Boink](https://boards.straightdope.com/u/Thudlow_Boink)\ **Post date:** [August 10, 2024, 10:23pm UTC](https://boards.straightdope.com/t/could-we-implement-this-option/1005532/6 "2024-08-10T22:23:08Z")
> [@wolfpup](#): > > The ambiguity of whether a post is replying to the OP or to the immediately preceding post is a real nuisance. Agreed. ---
**Author:** ![LSLGuy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/lslguy/32/5813_2.png) [@LSLGuy](https://boards.straightdope.com/u/LSLGuy)\ **Post date:** [August 11, 2024, 11:40am UTC](https://boards.straightdope.com/t/could-we-implement-this-option/1005532/7 "2024-08-11T11:40:56Z")
Agree it’s an irritant. And that if there is a config setting to address this shortcoming we should flip that switch. E.g.: This post is entered as a reply to **Thudlow\_Boink** ’s post just above. But doesn’t look like it. I deliberately used the traditional bolding rather than the @ syntax on their name in this post to avoid creating the @ notification to them and thereby muddying the waters of whether they’re notified for by being replied to versus notified for being @-ed. ---
**Author:** ![LSLGuy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/lslguy/32/5813_2.png) [@LSLGuy](https://boards.straightdope.com/u/LSLGuy)\ **Post date:** [August 11, 2024, 11:42am UTC](https://boards.straightdope.com/t/could-we-implement-this-option/1005532/8 "2024-08-11T11:42:55Z")
My own workaround is _not_ to quote the entirety of the preceding post then diddle a space or period into the quote. IMO that’s dumb and overkill. If a partial quote of the preceding post is relevant, use that where it fits in your own post and you get the right result for the wrong reason. If a partial quote isn’t appropriate to what I’m writing I’ll start my post with something like: @LSLGuy just above … Blah blah blah Which notifies them and makes it clear to every reader who/what I’m talking to / about. ---
**Author:** ![The\_Other\_Waldo\_Pepper](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/the_other_waldo_pepper/32/12370_2.png) [@The\_Other\_Waldo\_Pepper](https://boards.straightdope.com/u/The_Other_Waldo_Pepper)\ **Post date:** [August 11, 2024, 11:48am UTC](https://boards.straightdope.com/t/could-we-implement-this-option/1005532/9 "2024-08-11T11:48:22Z")
> [@LSLGuy](#): > > My own workaround is _not_ to quote the entirety of the preceding post then diddle a space or period into the quote. IMO that’s dumb and overkill. > > If a partial quote of the preceding post is relevant, use that where it fits in your own post and you get the right result for the wrong reason. If a partial quote isn’t appropriate to what I’m writing I’ll start my post with something like: > > @LSLGuy just above … > > Blah blah blah > > Which notifies them and makes it clear to every reader who/what I’m talking to / about. My workaround is to quote it in its entirety. ---
**Author:** ![pjd](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/pjd/32/3009_2.png) [@pjd](https://boards.straightdope.com/u/pjd)\ **Post date:** [August 11, 2024, 4:18pm UTC](https://boards.straightdope.com/t/could-we-implement-this-option/1005532/10 "2024-08-11T16:18:54Z")
> [@wolfpup](#): > > And worse, if you quote the immediately preceding post in full, Discourse “helpfully” removes the quote! Well, what do you know … it appears that this can be cured too ! > **[Removal of full quotes from direct replies](https://meta.discourse.org/t/removal-of-full-quotes-from-direct-replies/106857)** > > Discourse 2.2.0.beta6 added a new feature to Discourse: Remove full quotes of direct replies. We’ve received quite a few questions about how it works, so I wanted to provide all the details here. How does this feature work? The new feature is... by disabling the `remove full quote` site setting. FYI @engineer_comp_geek ---
**Author:** ![wolfpup](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/wolfpup/32/10618_2.png) [@wolfpup](https://boards.straightdope.com/u/wolfpup)\ **Post date:** [August 11, 2024, 4:21pm UTC](https://boards.straightdope.com/t/could-we-implement-this-option/1005532/11 "2024-08-11T16:21:23Z")
Nice find! Meanwhile I’ve been working around the full quote removal by adding the hidden string ` ` to the end of the quote. ---
**Author:** ![LSLGuy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/lslguy/32/5813_2.png) [@LSLGuy](https://boards.straightdope.com/u/LSLGuy)\ **Post date:** [August 12, 2024, 5:55pm UTC](https://boards.straightdope.com/t/could-we-implement-this-option/1005532/12 "2024-08-12T17:55:29Z")
IMO the audience playing at home does not need to see an entire post repeated to understand somebody is talking to/about the post / poster just above them. That way is pure clutter and confusion. Do _not_ disable the “no full quote of preceding post” feature. In fact, go the other way and make workarounds like @wolfpup just described a rule violation. Quoting a relevant excerpt is fine. But any gaming the system to quote substantially the entirety of the preceding post is something we should be vigorously squashing, not encouraging. Instead TPTB should tweak the reply-to-post button so a reply to the immediately preceding post is clearly labeled as a reply to the immediately preceding post. Just like it is when it’s a reply to another post farther up. Since this also appears to be an existing settable option in Discourse, doing this right ~~is~~ ought to be easy. ---
**Author:** ![wolfpup](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/wolfpup/32/10618_2.png) [@wolfpup](https://boards.straightdope.com/u/wolfpup)\ **Post date:** [August 12, 2024, 6:37pm UTC](https://boards.straightdope.com/t/could-we-implement-this-option/1005532/13 "2024-08-12T18:37:49Z")
> [@LSLGuy](#): > > Do _not_ disable the “no full quote of preceding post” feature. In fact, go the other way and make workarounds like @wolfpup just described a rule violation. Wow, that’s a militant side of you I haven’t seen before! 😉 I must admit that one of the reasons I do the full quote workaround is because of the ambiguity about who you’re actually responding to – the previous poster, or the OP. If there was a clear indication who the response was directed to I might feel less inclined to do that. But still, if you have an OP that says “I’m a very strong believer in _x_” and you’re replying to a preceding post that says “_x_ is bullshit” and your post is “I disagree”, it’s kinda handy to make it super clear who you’re responding to! ---
**Author:** ![Dewey\_Finn](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/dewey_finn/32/4222_2.png) [@Dewey\_Finn](https://boards.straightdope.com/u/Dewey_Finn)\ **Post date:** [August 12, 2024, 6:40pm UTC](https://boards.straightdope.com/t/could-we-implement-this-option/1005532/14 "2024-08-12T18:40:49Z")
I agree with @LSLGuy that people should not quote the entire previous post, or even most of it. ---
**Author:** ![LSLGuy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/lslguy/32/5813_2.png) [@LSLGuy](https://boards.straightdope.com/u/LSLGuy)\ **Post date:** [August 12, 2024, 6:41pm UTC](https://boards.straightdope.com/t/could-we-implement-this-option/1005532/15 "2024-08-12T18:41:26Z")
@Wolfpup two above … You (every you) should absolutely positively always make it clear who you’re responding to: the OP person/post specifically, the entire thread to date, or the poster/post immediately preceding your own. As I just did by @-ing you. But in the latter case quoting their entire 17 paragraph post is a _really_ disruptive way to do that. Quoting even a short post entire is also disruptive. That disruption is what I’m objecting to. And I wasn’t trying to single you out; I’ve made the same point several times already in this thread and the dozen-ish other threads we’ve had on this topic in the last 5 years. Quoting the whole thing with a diddle to fool a useful Discourse feature is vandalism, not outsmarting. ---
**Author:** ![Chronos](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/chronos/32/134_2.png) [@Chronos](https://boards.straightdope.com/u/Chronos)\ **Post date:** [August 12, 2024, 6:46pm UTC](https://boards.straightdope.com/t/could-we-implement-this-option/1005532/16 "2024-08-12T18:46:50Z")
The people who are taking the trouble to prevent Discourse from deleting the quote are not the people who are quoting an entire 17-paragraph post. Quoting an entire 17-paragraph post is almost never appropriate, and it’s reasonable for the software to remove that. But it can sometimes be appropriate to quote a one-line post in its entirety. ---
**Author:** ![wolfpup](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/wolfpup/32/10618_2.png) [@wolfpup](https://boards.straightdope.com/u/wolfpup)\ **Post date:** [August 12, 2024, 7:16pm UTC](https://boards.straightdope.com/t/could-we-implement-this-option/1005532/17 "2024-08-12T19:16:04Z")
In response to both @LSLGuy and @Chronos, I have occasionally seen posts that quote an enormous prior post in full, and I agree that this is disruptive and bad practice. I mean, what is the poster thinking – that you’re supposed to re-read the 17 paragraphs you’ve just read before reading the poster’s illustrious response? But Discourse doesn’t prevent that (nor do I think it should; some things shouldn’t be automated and should be a matter of sensible posting etiquette). What it **does** prevent is what is often useful in disambiguating who you’re responding to, and having such a “feature” as the default is just bad design. I’d never quote the previous post in full if it was more than a few lines. But if it’s short, and helps clarify who you’re responding to, I don’t see it as being in any way disruptive or, as the Discourse designers like to say, “clutter”. These were the folks who were so obsessed with eliminating “clutter” that for a time we had date formats on posts that were very easily misinterpreted (April '08 vs April 08) because it was considered “elegant” to have only the minimal necessary information to unambiguously resolve the date. The problem being that the users of these boards are human beings and not computers. ---
**Author:** ![TriPolar](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/tripolar/32/3008_2.png) [@TriPolar](https://boards.straightdope.com/u/TriPolar)\ **Post date:** [August 12, 2024, 7:19pm UTC](https://boards.straightdope.com/t/could-we-implement-this-option/1005532/18 "2024-08-12T19:19:45Z")
This is about a reply to the previous post. It requires very little for that to be automatic with as little as symbol, or some minimal text. At least identify the post in case of cross posting. ---
**Author:** ![Yookeroo](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/yookeroo/32/323_2.png) [@Yookeroo](https://boards.straightdope.com/u/Yookeroo)\ **Post date:** [August 12, 2024, 7:25pm UTC](https://boards.straightdope.com/t/could-we-implement-this-option/1005532/19 "2024-08-12T19:25:14Z")
> [@wolfpup](#): > > This is a great idea. The ambiguity of whether a post is replying to the OP or to the immediately preceding post is a real nuisance. And worse, if you quote the immediately preceding post in full, Discourse “helpfully” removes the quote! I hate this so much. ---
**Author:** ![pjd](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/pjd/32/3009_2.png) [@pjd](https://boards.straightdope.com/u/pjd)\ **Post date:** [August 25, 2024, 4:49pm UTC](https://boards.straightdope.com/t/could-we-implement-this-option/1005532/20 "2024-08-25T16:49:45Z")
> [@engineer\_comp\_geek](#): > > And I will see if we can get this turned on. Any news on this ? [Next page](https://boards.straightdope.com/t/could-we-implement-this-option/1005532.md?page=2)