# Testing Nested Replies on Meta
**URL:** https://meta.discourse.org/t/testing-nested-replies-on-meta/398759
**Category:** Nested Replies Testing
**Created:** [March 18, 2026, 8:56pm UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759 "2026-03-18T20:56:48Z")
**Posts on this page:** 20
**Page:** 6
### Author:  [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [April 21, 2026, 7:08pm UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/102 "2026-04-21T19:08:51Z")
I suppose on nested views, you’re not supposed to “read it all” as opposite to a flat view. You’re meant to direct your attention to branches instead.
Is that how it’s supposed to be used?
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [April 21, 2026, 7:54pm UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/103 "2026-04-21T19:54:36Z")
That’s exactly it, you nailed it.
---
### Author:  [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [April 22, 2026, 6:21am UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/104 "2026-04-22T06:21:24Z")
And then there is the unsolved issue: how does a user know what branch has info/opinions interesting enough 🤷♂️
That would be a nightmare’ish for moderation. But as said several times — if the nested thingy will be reality at some point, there is no force to start using it, unless community (meaning quite often what an admin desires 😜) wants or likes it.
---
### Author:  [@Orioni](https://meta.discourse.org/u/Orioni)
#### Post date: [April 22, 2026, 9:51am UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/105 "2026-04-22T09:51:34Z")
Here’s one reply to your comment to test the nesting.
---
### Author:  [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [April 22, 2026, 10:18am UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/106 "2026-04-22T10:18:53Z")
> [@Jagster](#):
>
> And then there is the unsolved issue: how does a user know what branch has info/opinions interesting enough 🤷♂️
On Reddit, I tend to consider each top-level comment as “mini topics”. I find one interesting, and then I read as much as I can from it, which is limited by the usability of this interface. Which means I’m probably missing interesting comments because they were too deep, or inside a sub-branch I didn’t expand.
The difference between Reddit and Discourse is that whatever they are called, I rarely consider Reddit replies in higher esteem than mere “comments”. Rarely interesting, rarely more than a single sentence, rarely high-effort or value adding, and, of course, often dispensable (and riddled with trolls and bots).
On Discourse, or at least on meta (even if Discourse emphasizes this by philosophy), replies are much more substantial and deserve to be read.
Which makes the nested view, at least on meta, particularly unfit, if not incompatible.
---
### Author:  [@markvanlan](https://meta.discourse.org/u/markvanlan)
#### Post date: [April 22, 2026, 1:48pm UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/107 "2026-04-22T13:48:29Z")
> [@Jagster](#):
>
> if the nested thingy will be reality at some point, there is no force to start using it, unless community (meaning quite often what an admin desires 😜) wants or likes it.
Yes, you’re absolute right about this. It’s not something we would recommend for the vast majority of communities. I think it’ll only make sense for quite large communities like game forums. I used to watch professional League of Legends and the subreddit would have post-game discussions with thousands of people discussing. That would be a perfect use case, where you can’t read everything. You don’t want to read everything.
---
### Author:  [@markvanlan](https://meta.discourse.org/u/markvanlan)
#### Post date: [May 8, 2026, 4:10pm UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/108 "2026-05-08T16:10:35Z")
How does this notification work, is it good?
---
### Author:  [@markvanlan](https://meta.discourse.org/u/markvanlan)
#### Post date: [May 8, 2026, 4:10pm UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/109 "2026-05-08T16:10:42Z")
What about this notification?
---
### Author:  [@markvanlan](https://meta.discourse.org/u/markvanlan)
#### Post date: [May 8, 2026, 4:10pm UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/110 "2026-05-08T16:10:50Z")
And then it’ll consolidate.
---
### Author:  [@markvanlan](https://meta.discourse.org/u/markvanlan)
#### Post date: [May 8, 2026, 4:11pm UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/111 "2026-05-08T16:11:04Z")
Just testing notifications, don’t mind me 🙂
---
### Author:  [@piffy](https://meta.discourse.org/u/piffy)
#### Post date: [May 9, 2026, 1:48am UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/112 "2026-05-09T01:48:49Z")
A few tweaks and could be a nice replacement for the [Journal Plugin](https://meta.discourse.org/t/journal-plugin/317785) !
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [May 18, 2026, 6:39pm UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/113 "2026-05-18T18:39:02Z")
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [May 18, 2026, 6:39pm UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/114 "2026-05-18T18:39:20Z")
---
### Author:  [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [May 21, 2026, 11:28am UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/115 "2026-05-21T11:28:30Z")
testing an unread reply 1
---
### Author:  [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [May 21, 2026, 11:28am UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/116 "2026-05-21T11:28:55Z")
testing an unread reply 2
---
### Author:  [@sk-or-v1-contents](https://meta.discourse.org/u/sk-or-v1-contents)
#### Post date: [May 24, 2026, 3:36am UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/117 "2026-05-24T03:36:22Z")
Anyone know how to disable machine translation? I can’t find the 文A button normally next to the post count button in flat topics. You can find a machine translated one posted on Apr 7 - I won’t link it because I don’t feel like it
---
### Author:  [@sk-or-v1-contents](https://meta.discourse.org/u/sk-or-v1-contents)
#### Post date: [May 24, 2026, 3:57am UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/118 "2026-05-24T03:57:22Z")
Is there a way to “catch everyone’s attention” with nested replies? For example you asked a question, people answered, and then you thought you aren’t getting the information you need and want to let people answer in a particular direction.
---
### Author:  [@markvanlan](https://meta.discourse.org/u/markvanlan)
#### Post date: [May 28, 2026, 2:00pm UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/119 "2026-05-28T14:00:34Z")
By the way, a version of this was implemented. Thanks for the great idea! test edit
---
### Author:  [@Ahmed26](https://meta.discourse.org/u/Ahmed26)
#### Post date: [May 31, 2026, 1:05pm UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/120 "2026-05-31T13:05:02Z")
Does this really need to be like Reddit? Something simpler would do the job just fine. I think something like the image would be enough.
It would be enough if the reply section were a pop-up window; that way, Discourse’s original reply thread would be preserved. The tree structure seems to make things far too complicated.
They did the same thing in the XenForo forum system
---
### Author:  [@isaac](https://meta.discourse.org/u/isaac)
#### Post date: [June 15, 2026, 3:36pm UTC](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759/121 "2026-06-15T15:36:18Z")
I am testing a reply for Mark 🙂
[Previous page](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759.md?page=5)
[Next page](https://meta.discourse.org/t/testing-nested-replies-on-meta/398759.md?page=7)