A more social Discourse layout


(Jon Stokes) #27

I think there are probably a few discussions here that are jumbled together, and that is probably my fault because I kinda tried to hijack the thread with this stuff about how it shouldn’t just look like a feed, which is what the OP is after, but there should be a way for a user to actually manually curate a real feed.

So for my part, am not talking solely or even primarily about any sort information density issue. Sure, there are ways I’d like a feed to look, but I’m speaking more specifically to organization and ease of curation and to the existence of a curated feed itself. I want to be able to curate a feed and have people follow it. That’s different than saying “I want the topics list to look this other way… more like a social site” which is where this thread started. I want to curate a feed, and I also want that feed to look more information-dense (like most social feeds) than the current topics list, and this latter point is where my interest intersect with the OP’s.

Note that I’m of the clearly opinion that Discourse should move in a more social- or feed-centric direction, but of course I just got here and started using it and am not really a part of the dev community yet so I offer it more as an outsider’s take that seems to jive with some demand that I’ve seen here on and off via Googling for plugins. Regardless of what happens with Discourse itself, though, it’s extensible enough that any of us who want to see it do more feed-like things can just make it do that.

As for the distinction @angus raised between author-centric and discussion-centric… maybe, but I’m not entirely sure I follow because I don’t know that that’s a real dichotomy that I’d sign on to, or what the two terms would mean here.


(Adrianbblk) #28

And how you get that design with topic list peview? It doesn’t work on mobile and/or for the homepage.


(Angus McLeod) #29

The topic list social site or category setting. Happy to work through your use case, but please try it first. If you have further questions or requests, post in Topic List Previews and I’ll follow up there.

This is what I meant by ‘author-centric’, content curated by reference to an author, as opposed to ‘discussion-centric’, which would be content curated by attributes of the discussion: when it was posted, how popular it is etc.

You alluded to the same distinction above, i.e. many to many v one to many.

Are you advocating for Discourse to handle both cases?


(Adrianbblk) #30

I’ve tried already and I don’t like it. I was trying to say that it is not the same the topic owner says.


(Mittineague) #31

The way I would say it is

On a “social” platform I am interested in what particular people are saying regardless of what is being said. On a “discussion” platform I am interested in what is being said regardless of who is saying it.

There is often some overlap so that there isn’t a clean division but that’s what “centric” means.

I can understand that some forum users might have interest in what another member is posting. But because forums typically have a hierarchy of categories it seems to me that discussions would be expected to be primary over the social. Not that member feeds are a bad idea, just that it feels more like a forum “nice to have”


(Jeff Atwood) #32

:+1: This is also why “I want to follow users X, Y, and Z” is a huge red :triangular_flag_on_post: flag.


(Dražen Lučanin) #33

Awesome @awesomerobot! Really nice to see you’re already playing with some layouts :slight_smile:

I guess some sort of combination of last updated and popularity-based sorting would be good. As a regular reader, I find the recent/unread topics marked in a different colour useful to catch up. As a first time / occasional visitor I would like to see more engaging content on the front page (to motivate me to continue exploring).

Yes, your layout mockup looks great – if every topic in the topic list had a few algorithmically selected replies underneath it and maybe images from these posts as well (because images can often be much more engaging than text alone) that would be great!

Once you open an actual topic to see all the posts, I think it can stay the way it is – where you can read the whole exchange. I think Discourse is already doing a good job there.


(Sebastian) #34

just bringing up the feed that BuddyPress uses once again. no algorithms, no shenanigans, just a user-friendly feed of what’s happening in the community…


(Jon Stokes) #35

A red flag for what, though? You have a blog, and people who want to know what you have to say follow it. So you’re doing exactly the “author feed + comments” paradigm that I’m expressing a preference for, yourself, but for whatever reasons you’ve decided not to host the feed (i.e. blog) on Discourse, and to only host the comments.

In fact, there is such a demand for some kind of “feed + comment” solution based on Discourse that an increasing number of sites are going to the trouble of wiring up a Ghost or WP blog to Discourse so that they can at least do the comments half, here. And of course every now and then somebody posts the obvious question in this forum, i.e. “Discourse is a great authoring and publishing solution, so what’s with making me wire it up to an external blog so that I can blog with it? Why doesn’t it have out-of-the-box support for just blogging directly on it?”

So I don’t have to defend the idea that “follow my feed and comment/like/share” would be a popular way to use Discourse, because to the extent that such a thing possible it’s already happening, and people are jumping through hoops to make it happen by mating Discourse to something you can actually host a feed with.

I think it’s not at all a stretch for it to handle both cases. As for if I’m advocating for that, I guess I was, but at this point it’s clear to me that (absent a dedicated social plug-in) it’s not going to happen in any other form than it’s currently happening, i.e. somebody else (Ghost or WP) hosts the feed, and Discourse hosts the comments.

The team here seems dedicated to keeping Discourse squarely in the realm of a Google Groups and/or Disqus replacement, which is still awesome because both those things suck and should definitely be replaced by FOSS.

My take-home from this thread is that anyone who wants to see Discourse host a followable feed directly should focus their efforts on a plugin, so that’s what I plan to do. Right now, I’ve started hacking at my own, but I’m more than happy to ditch that and contribute to a more mature plugin that’s headed in that direction.


(MAR) #36

Creatives would be more engaged by something like this where images are used to engage as well. Food for thought


(Jeff Atwood) #37

That’s right, I think some communities can be way more visual than others, which is why this depends heavily on the specific community.


(Angus McLeod) #38

Happy to help you with anything you get stuck on with your plugin. Just pm me.


(Jon Stokes) #39

Thanks! I will definitely abuse… er, take advantage of that :slight_smile: I have a long weekend or two ahead of me of going through the code for your existing plugins before I’m even ready to start pestering you, though.


(MAR) #40

Any wayvto have the option?


(Angus McLeod) #41

If you mean any way to have the option of pm’ing me about help with a plugin you’re building, sure happy to help.


#42

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.


(Jeff Atwood) #43

I am with you :100:% on this.

I see and understand the need to be “more visual” for certain communities that are already highly visual by nature, but as a central tenet of what we stand for? It would literally break us.


#44

Yeah, awful! One advantage of having a smaller scale community where I’d argue such behaviour is unnecessary.


(Sebastian) #45

I see the thin line Discourse has to walk here. And I do agree this has to be carefully weighed and probably be the job of a plugin. However, I think there is another, more overarching challenge that Discourse should consider and weigh in as well. It’s that of an overall shift in the web that happened over the last many years, away from websites, blogs and message boards on to Facebook and other proprietary platforms, which have come to shape and form users’ expectations as to functionality and usability. These platforms have become the home for people, their view of the web and unfortunately more often than not a golden cage. I do not think that Discourse should ever try to copy that or become kind of an open source Facebook clone, don’t get me wrong. However, and that’s why I brought up Buddypress’ timeline view as an example, I don’t see anything wrong in offering an optional view to Discourse users (in addition to top, latest, unread, categories…), that depicts, without any algorithm and whatnot, a linear, reverse chronological, feed timeline of what is happening in that particular discourse community, and a more “familiar” entry point for some and also a useful indicator to visitors of the activity that is going on. Such a feed would not only list things like “XY posted in topic Z” or “Topic X was moved to category Z”, but also “X, Y and Z joined the forum today” or “A was rewarded Badge soundso for his excellent post in topic D” etc. So much activity types that such a feed could display that would trigger a lot of interaction and help build a community… I think for those of us struggling to get people back into message boards like Discourse, this would be a huge step up.


(Jeff Atwood) #46

This feature has been available for years in vBulletin 5 and people hated it.