# A more social Discourse layout

**URL:** <https://meta.discourse.org/t/a-more-social-discourse-layout/89759>\
**Category:** UX\
**Created:** [13 ביוני,‏ 2018,‏ 11:00am UTC](https://meta.discourse.org/t/a-more-social-discourse-layout/89759 "2018-06-13T11:00:41Z")\
**Posts on this page:** 1\
**Showing post:** 42

<div class="post-metadata">

**Author:** ![jtbayly](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jtbayly/32/119510_2.png) [@jtbayly](https://meta.discourse.org/u/jtbayly)\
**Post date:** [16 ביוני,‏ 2018,‏ 12:26am UTC](https://meta.discourse.org/t/a-more-social-discourse-layout/89759/42 "2018-06-16T00:26:28Z")

</div>

> [@angus](#):
>
> I think it’s important to keep a healthy skepticism about ‘Discourse as social media’. Just because images increase click through rates, it doesn’t follow that it’s a good thing for healthy discussions.

This.

In particular, I’ve found the following to kill true discourse on FB:

1. Having a non-linear display of comments.
2. Having multiple levels of comments under a single post.
3. Having a “read more” button displayed inside a comment (or even 2, 3 or more “more” buttons in a single comment)
4. Not even loading all comments that are part of a single discussion (as in they aren’t found in the DB or something). I can’t guarantee 100% that FB does this occasionally, but I’m virtually certain that I’ve run into it multiple times.
5. Upon clicking through, only loading the comments under a single top-level comment, thus completely removing from display all other top level comments and their responses.

(I think I’ve got more for this list, but can’t think of them. I’ll update if I come up with them.)

What these things cause is people missing parts of the discussion without realizing it. I’ve personally carefully read every word of every comment in some discussions prior to responding, only to find out that I still accidentally missed substantial portions of the conversation. The “more” links within a single comment are particularly insidious, especially when you’ve already clicked one or more of them in the comment and you come to the end of a paragraph that seems like a conclusion.

These UX decisions are especially damaging in discussion where emotions are running high for whatever reason. When the comment with the apology doesn’t get displayed, or when it is accidentally left as a top-level comment instead of a response, thus dropping it out of view either by pushing it down the page or, even worse, not loading it at all because of issue #5 above.

The number of clicks required to see everything just goes up and up and up, and I’m sure it drives up the amount of “interaction,” but it also destroys discourse. I will say that some of these things—like the way that top level comments get their own thread—definitely have arguments that can be made for them for certain usability use cases. However, if you want to have serious discussion it is an outright nightmare.

I would urge the Discourse team to be very careful about what kinds of changes they make in the search for “social” features or “familiar” features (from social) or simply increased “interaction.”

I love Discourse precisely because it doesn’t have these things.

---

_[View the full topic](https://meta.discourse.org/t/a-more-social-discourse-layout/89759)._
