How to seperate the "drive by" topics from the "deeper" discussions?

Community Building
21

I agree there’s plenty that could be automated to solve this and that this is an important aspect of what large social media companies do. But there are “manual” signals as well on social media, like who you choose who to friend/follow.

Within our organization, people opt in to some subset of a couple thousand Slack channels. That’s a pattern they are used to. (I’ll choose which topics/groups/categories I want to stay on top of).

I think there are important differences in Discourse, and one of the goals we have is to encourage cross-pollination, so I don’t really want to go down a road where people have to opt in to the things they want to see. And similarly, I don’t want to force people to mute things they don’t want to see.

I’d really like to keep the Latest page as the default “firehose” for those that want to see the full activity on the forum, while providing a simple and intuitive UX for people to build one custom stream of their favorite topics that they can focus on. I’d like this to work in a way that reduces noise, rather than boosting signal, which is why I’m not super keen on recommending that they just watch or track those categories.

I don’t object to exploring automated approaches, but I think there may be lower hanging fruit that is easier to reason about which could be tackled first.

This is definitely something that has also come up in our research so far as well.

6개의 좋아요
22

hm. You’re both more experienced in managing communities than I am, but we’re talking here about a matter of degree, rather than a categorical distinction. I’m sure it’s true that relationships still matter in a forum, however my hypothesis would be that, the connection that ‘regulars’ have with a forum (and each other) is significantly more ‘topic-centric’ than it is on social media. I’m willing to be proved wrong, but I’d need some solid evidence.

Take meta for example. I could think there were cool and interesting people here (and I do :slight_smile: ). But if suddenly meta was re-purposed as a forum to talk about our favorite cars, then I probably wouldn’t come here that often.

There’s an analogy here with ‘work friends’. Work friends are people you know because you are pursuing the same goal. You naturally get to know them better in pursuit of that goal. You feel a sense of connection with them. However, when you change jobs your relationship with your work friends may last for a bit, but it often fizzles out. Maybe that’s just me.

I guess what I’m saying is that I definitely accept that relationships become more important over time, however the center of gravity is still going to be about specific subject matter. Conversely, on social media you care more about who it is that is saying or sharing something. Yes, what they are saying is still important of course, but who they are and what you think of them as an individual plays a greater role. You exist on social media as an ‘individual’ or a ‘personality’ (reflected in the ‘integrated’ experience @tophee mentions). You exist on a forum in a more targeted, focused way.

In some ways, allowing a user to manually curate their list is harder to do than ‘automatically’ making lists more user-centric. The ‘automated’ approach here would be to edit the algos in TopicQuery to preference topics similar to those a user has previously engaged on. You wouldn’t need to change much in the UI. The ‘automated’ approach also allows you to be more responsive to how people actually end up using your list. The problem with ‘manual’ approaches is that there is often a difference between what we think we’re interested in and what we’re actually interested in.

I think I will attempt the ‘automated’ approach to topic list curation based on proxies for user interest in a plugin at some point.

8개의 좋아요
23

I think that’s a totally fair comment and I agree with you (although there are plenty of Facebook groups which fall outside the normal ‘social media’ formula).

What I’m trying (perhaps badly) to say is that I think that different types of forum audiences are motivated by different things – and by extension, different types of communities rely on different types of behavioural norms for their survival.

Agreed. The counter-argument is that if there was another community about the same topic which was filled with people that you have a lot more in common with, you’d be more likely to visit that one.

FWIW I’m really enjoying this topic and I’m not attempting to win any points – just picking your brains. I’m interested in your thoughts.

3개의 좋아요
24

Since the vast majority of drive bys will be trust level 0 users, perhaps you could require trust level 1 to create a thread in any category other than tech support. When people get denied based on their trust level, you can remind them that anyone can post in the tech support category.

4개의 좋아요
25

That definitely addresses the separation/getting lost in the noise issue but it will exacerbate the ‘we’re getting lots of crap and very few interesting discussions’ issue by raising the barrier to entry.

26

Addressing the good conversations getting lost in the noise should indirectly help bolster more discussion. Less frustrated users leads to less attrition which leaves you with more people to have interesting discussions.

I’m not sure the separation of wheat/chaff posts and the lack of interesting discussions are problems that can be fixed together with a single solution. Getting people to talk about interesting stuff on a forum is a much bigger problem than can be solved by tweaking category structure or user permissions.

3개의 좋아요
27

Yes I agree. I think what cuts across that somewhat though, and what I see as the important connection between the UX of forums and social media, is the psychological aspect of product development; aka captology.

When Facebook is designing their news feed they don’t start from the assumption that their users are rational agents with definite preferences. They start from the assumption that their users have certain biological structures and responses that can be stimulated and even shaped over time. The UX decisions about the news feed are essentially based on neurobiology, not on higher level concepts of ‘interesting’ or ‘deep’. I’m sure that when they are making product decisions about their ‘groups’ features, they are taking similar things into account.

The ‘dark’ slant of this is thought that tech products are being designed to be addictive in the same way that drugs or slot machines are. The academic paper underlying that comparison is here if anyone is interested. A side note here is that that paper (and similar work) is often mis-reported. If you actually read the thing, they quite clearly say (a number of times):

technology “addictions” may not present the exact same brain etiology and possibly pathogenesis that drives substance and gambling addictions.

The more neutral reading of this direction is that of course neurobiology should play a role in UX and content curation. Taking into account the neurobiological responses of your users is simply acknowledging that they are human. The idea that there is some separation between a mental rational ‘self’ and our biology is a remnant of the dualist theme in Western thought going all the way back to Plato’s Forms. The question is not whether or not it is ethical to take a neurobiological approach to UX - all approaches have neurobiological consequences whether you realize it or not - the question is what are the ethics of the neurobiological approach you are taking.

This is partly what I meant when I said we need to think of the UX of social media as a product strategy, rather than a ‘practice intertwined with social and ideological narratives’. This is the context to why I think there has to be a role for things like automated user-specific curation in the discovery topic lists, rather than relying entirely either on user choice or user curation (i.e. moderation / community management). Automated user-specific curation is much better at incorporating learnings from advances in neurobiology / psychology, e.g. that there often isn’t a one-to-one relationship between our perceived and our enacted preferences; that we invariably seek the path of least resistance (we’re naturally lazy); that our ‘interests’ are not so much ‘chosen’, as they shaped over time by our environment; etc.

It doesn’t follow from this that Discourse should adopt practices like preferencing videos and images over text (like Facebook does). It flows from it’s topic-centricity that forum content, and engagement with that content, is different from social media.

It does follow from this that UX / product thinking about content discovery and curation on a forum needs to move more toward an explicit discussion of user psychology and away from approaches based the assumption that users are atomic rational agents with definite preferences, or that engagement on different types of communities is inherently different. People are behaviorally much more similar than they think. That behavioral similarity is how Facebook manages to ‘addict’ an academic at Yale as easily as a factory worker in Dhaka.

Finally, I would reiterate that I am not saying “Let’s think about how we can get users addicted to our forums”. I am saying that the real context to this discussion about content curation and UX is our neurobiological response to stimuli. ‘Addiction’ is a description of a state on a neurobiological spectrum. A spectrum which we all exist on, 100% of the time.

@HAWK none of that is directed against you per se. As you say, I think we’re broadly on the same page.

4개의 좋아요
28

All good. I actually used to teach a captology/persuasive technology workshop (and how it relates to community platforms). I’m 100% on board with ^^

1개의 좋아요
29

And if try to make a plugin that adds a new page: feed
Which can be added to select pages (categories and latest + feed)

What to show on the feed?

1. bookmark
2. all the themes from categories, tags are not muted

The idea is that would make a Central page it is like the tape in social networks. This will allow to solve a lot of problems.

I just suggest if it make sense?

What I’m not signed, I won’t see. In social networks I do not unsubscribe from the content, and subscribe. Perhaps this approach is more General users. They see only what they want?

Although there is a “rule” of 3 clicks. In fact, each click is very important. For example. Now categories can be seen if you click on the tab. It’s one click. Transferring a list of categories in a bar we remove this with a click and do everything visually convenient. For example, I don’t like what I see, I suppose not satisfied with the topics from a specific category. I should go to this category and unsubscribe, that would not see the content on the main page of the forum. This extra action. Let originally that I like I will choose myself. As is done in all social networks. It certainly has a place when there are a huge number of people who post material on the forum.

2개의 좋아요
30

Sorry but I disagree. Following your example, docs are docs because their calling is helping other. They are there because patients exist. Building a community where there are “ship classes” is not inclusive, something like “keep out the kids!”
I understand that docs should have a place where they can discuss “high level medical topics” but keeping the people out is not the right choice. Keep in mind that one of those “random people” (if you are kind to them) can become a doc himself, or even a chief.

1개의 좋아요
31

The avenue I would pursue is ranking content on a user by user basis by comparing content classifications - categories, tags and authorship (i.e. who made the content) - with user-interest proxies - likes, views, reading time, replies (and others) - of the individual user. Use that ranking to create a user-specific topic list.

Maybe you know how to already, but if you don’t, the way I would do it (and the way it’s done in @joebuhlig’s Hot Topics plugin) is:

  1. Add your list to the top menu options and the filter options is easy. Just add these lines to your plugin.rb e.g.

    Discourse.top_menu_items.push(:agenda)
Discourse.anonymous_top_menu_items.push(:agenda)
Discourse.filters.push(:agenda)
Discourse.anonymous_filters.push(:agenda)

  2. Add your list logic to TopicQuery. e.g.

    require_dependency 'topic_query'
class ::TopicQuery
  SORTABLE_MAPPING["agenda"] = "custom_fields.event_start"

  def list_agenda
    @options[:order] = "agenda"
    topics = create_list(:agenda, ascending: "true")
  end
end

I suggest you make both the content classifications and user interest proxies the subject of site settings so that different mixtures can be applied according to the initial hypothesis and experience of each forum.

4개의 좋아요
Reddit new algorithm
32

Thanks, I tried to do:
https://github.com/Toxu-ru/discourse-feed-topics

The only thing that stops working on this page is sorting: Replies, Views, Activity
I think this approach can be useful.

1개의 좋아요
33

What we do in our community: we create topics a bit wider than the narrow scope of individual support questions, and then join the latter into the former.

Example “support” questions in the cheese home-making category:

  • My blue cheese turned out to be too hard, how do I soften it?
  • Blue cheese spoiled in my fridge. What are fridge requirements for blue cheese?
  • The ferment produced by XXX for blue cheese never worked for me, anyone tried it? What may I be doing wrong?

– all joined into a topic titled e.g. “Issues with blue cheese production”.

Then we have similar topics for soft cheese, hard cheese, cottage cheese and so on.

It has been working well so far. Just don’t make the combined topics’ scope too wide.

We also noticed that readers love such topics because they can read about many issues and read about experience of many people all in one thread – at least for cheese making it turned out to be useful to group discussions like these.

I’m not sure why it works. Maybe because when you cook something it is useful to read all the issues you can experience in one go in one place. Also, once an issue is solved (usually within <10 posts), the topic is over. If you leave it as is, the topic will get lost and never get any more activity unless it is specifically searched for).

3개의 좋아요
34

최근 누군가 이 주제에서 내 게시글에 '좋아요’를 눌러서, 다시 한번 읽어보게 되었습니다.

7년 전의 토론을 다시 읽는 것은 잊고 있었던 내 발언들과 시간이 흐르면서 생긴 변화(예를 들어, 2017년에 HAWK와 Dave가 Discourse에서 일하고 있었는지 확신은 없지만, 지금은 각각 공동 CEO와 프로덕트 매니저로 재직 중입니다. 또한 내가 Pavilion에 합류하기 전이기도 했습니다)를 볼 수 있어 기이하면서도 재미있는 경험입니다. 포럼이 제공하는 '토론 고고학’의 기회는 포럼의 강점 중 하나라고 할 수 있겠습니다.

관련하여, 최근 추가된 ‘핫(hot)’ 주제 목록(이 커밋에서 추가됨)을 살펴볼 생각은 하고 있었는데, 위 내용을 다시 읽으면서 동기가 생겼습니다. 코드 내의 주석은 핫 알고리즘에 유용한 수식을 제공합니다:

(총 좋아요 수 - 1) / (시간 단위 경과 시간 + 2) ^ 중력(gravity)

이 기능에 대한 논의는 해당 기능을 알리는 주제에서도 이루어졌습니다.

핫 주제 목록에 대한 제 의견을 덧붙이기 전에, 이는 본질적으로 '생각의 방울(thought bubbles)'이며, Lindsey가 핫 목록(또는 다른 주제 목록)의 제품 유틸리티가 어떻게 결정되어야 하는지에 대한 개요에 동의한다는 점을 밝히고 싶습니다:

그럼에도 불구하고, 이 오래된 토론과 새로운 핫 주제 목록이 교차하는 지점에서 떠오르는 몇 가지 사항들을 정리해 보았습니다:

  • '분류(taxonomies)'를 선택적으로 사용하여 핫 알고리즘의 가중치를 조절할 수 있을지 궁금합니다. 즉, 특정 카테고리나 태그가 많은 활동(예: 좋아요)을 받더라도, 포럼 관리자로서 이를 다른 카테고리나 태그의 활동보다 ‘얕거나’ 어떤 면에서 덜 바람직하다고 판단할 수 있습니다. 다시 말해, 사이트 특성에 맞는 발견(discovery) 큐레이션(선별)을 더하는 것입니다.

  • 사용자 변수(예: 신뢰 수준, 해당 사용자의 이전 주제 조회 기록)에 맞춰 컨텍스트화 된 주제 목록이 어떤 모습일지/어떻게 작동할지 궁금합니다. 다시 말해, 사용자 특성에 맞는 자동화/알고리즘 기반 큐레이션을 더하는 것입니다.

요약하자면:

4개의 좋아요
35

저는 2017년 7월에 CDCK에 합류했으므로, 이 주제에 처음 기여했을 당시에는 막 합류한 상태였습니다. 자신의 오래된 게시물을 다시 읽을 때 얼마나 낯설게 느껴질 수 있는지에 대한 의견에 전적으로 동의합니다.

이러한 일반적인 아이디어를 좋아하며, _핫_을 일정 수준까지 큐레이션할 수 있는 것이 유용할 수 있는 상황을 여러 가지로 떠올릴 수 있습니다.

3개의 좋아요