Opt-In Conference Scheme

AI-generated summary

The Opt-In Conference Scheme proposes a category-based system for large communities, allowing users to opt-in to specific work groups or special interest sections. This scheme aims to reduce overwhelming notifications and topics by focusing on categories rather than individual topics.

hellekin suggests implementing this as a plugin, leveraging existing functionality to adapt the UI. A similar scheme has been successfully used in other online forums, such as Brainstorms.

To set up a similar scheme on Discourse, hellekin provides a step-by-step protocol, including enabling specific settings, creating groups for each category, and using category descriptions as group descriptions. However, this approach has limitations, and hellekin proposes an alternative: using the associated category description topic as the group page.

Let’s call conference a Category associated with a Group.

A conference has a home page, presenting the conference purpose and possibly inviting users to join, according to the group’s credentials, as in the group’s page. Technically, this home page could be the group’s home page, without the members list.

The conference scheme enables large communities to maintain opt-in work groups or special interest sections, or different language sections without overwhelming all users with notifications and a large number of topics.

This can be implemented as a plugin which I’m interested in programming. I’m proposing this to the community to see if there is traction, and if other people would like to participate. I suppose most of the functionality is already present, and it’s a matter of fixing the pipes to adapt the UI. This “category opt-in” scheme mostly moves the focus from topics to categories.

This scheme has been used in other online forums, e.g., Howard Rheingold’s Brainstorms, where hundreds of users exchange daily, rendering the contents quite overwhelming when you try to follow everything – hint: you can’t. As thousands of posts accumulate in your reading list, you’re very happy to be able to focus on some parts of the community rather than playing catch-up or muting the avalanche of new categories and topics.

1개의 좋아요

Discourse 3.1.0.beta6에서 다음 프로토콜을 사용하여 유사한 구성을 설정했습니다:

  1. mute_all_categories_by_default 활성화
  2. allow_uncategorized_topics 활성화
  3. suppress_uncategorized_badge 비활성화
  4. "미분류 카테고리"에 대해 default_categories_watching_first_post 활성화
  5. default_navigation_menu_categories를 메인(공개) 카테고리로 설정
  6. 각 카테고리에 대해 해당 카테고리를 track하는 특정 그룹을 생성합니다 (예: foo라는 이름의 카테고리에 대해 c-foo 그룹 생성…). 그룹의 목적에 따라 자유롭게 가입/탈퇴하거나, 가입 요청/자유 탈퇴 방식을 적용합니다.
  7. 각 카테고리에 대해 카테고리 설명을 그룹 설명으로 사용하여, 해당 그룹이 어떤 카테고리(들)에 대해 어떤 알림 수준을 제공하는지 명시합니다.

이 마지막 부분이 더 나은 방법이 있을 수 있다고 생각하게 만드는 부분입니다. 실제로, 해당 카테고리의 설명 토픽을 그룹 페이지로 사용할 수 있는 기능이 있으면 좋겠습니다.