Unlisted topics: Making them more useful

This follows on some previous discussion on unlisted topics. My use case is that Discourse is our company message board for most internal communications, i.e. just among the employees of a company.

We’re quite an open company, but we have 30+ people who can read our staff message board. Most of the time, we want everyone to see everything, as soon as its posted. But sometimes we want to use Discourse to talk about something among a small group before making the discussion accessible. For that, Unlisted topics are perfect (and that matches @sam’s stated use case Invisible topics are not invisible - #7 by sam).

Unfortunately that doesn’t work at the moment because not everyone can create an unlisted topic (as per previous discussion above). You have to create the topic, THEN unlist it, but that option is only offered after the notifications have gone round. So that only works if you are a member of a privileged group - i.e. you create the topic in the privileged group, then unlist it, then move it. That’s also a lot of clicking for something that I’d like to be routine.

It’s :thumbsup: that unlisted topics don’t appear in the site search. I appreciate that unlisted topics are not especially secured, but the defaults support the use case of “you can’t find them unless you dig”. In the same way e.g. our company email is on a shared server, and some people have root/admin rights to that server, I already trust those people not to dig around, and I’d trust the relatively light security defaults of an unlisted topic.

To make this useful to our company, the feature would look like this, whenever I create a new Topic:

So this screenshot implies at least three changes:

  1. that you’re able to create an unlisted thread at all;
  2. that the Create Topic pop-up puts the visibility of each thread up-front, all the time.
  3. [bonus feature] that you’re able to tell Discourse to make an unlisted thread listed after a certain period of time (see below);

Clearly 1 doesn’t imply any data changes, but extra UI.

2 - is a big deal, because it makes the UI more complicated by default. It’s probably something that needs enabling as a new board setting, and defaults to Off, because it seems like too much of an imposition on lots of people that don’t understand / care for it.

3 - is another new feature, automatically listing unlisted topics after a certain amount of time (e.g. 7 days after last post?) Almost all the discussion I want to have on our staff forum - i.e. in a corporate context, anything truly private doesn’t belong there, and is already better served by email. But most of the time, I do want all our discussions to be public eventually. Making that process automatic makes sense, otherwise we run the risk of losing an interesting older discussion from searches.

But I can see that it changes a potentially compact two-way UI option into a longer-winded bumper box. e.g. without that feature, you might have a toggle switch or a checkbox or something smaller.

Alternatively you could ensure that unlisted & open discussions retain priority in the thread listing for the users that see them, e.g. listed after pinned topics, so as to remind people to either close or list them.

I imagine that “ability to create unlisted topics” is a privilege, or a board-wide feature, since not everyone would want the clutter (and then there’s another setting). So I hope I can see the costs of this feature reasonably. But I’ve tried to think about what the minimum number of changes would be, and I’m certain that implementing above would result in less email and more Discourse discussion at Bytemark.

If any developers had bandwidth to think about this, had any questions about our use case, I’m happy to elaborate on anything at all. We love Discourse, and just want to use it more :heart_eyes:

8개의 좋아요

Couldn’t you use PMs for this? Message the private group, talk about it, and then move/convert it to a Public Topic (new feature that came out a few weeks ago)

8개의 좋아요

Thank you, that is brand new information :slight_smile: I’ve asked for an upgrade, and will see if it solves my use case.

2개의 좋아요

We could easily add it to the gear icon, we already do this for whispers which are conceptually almost identical. Can you take a look at adding this @tgxworld it seems maybe easy?

4개의 좋아요

OK we upgraded and the PM → public topic admin function does operate exactly how I want, thank you @cpradio.

10개의 좋아요

Ability to toggle a topic unlisted has been added to the gear icon and is only available when creating a new topic.

15개의 좋아요

Thanks! Looking forward to trying it out in a release, though the private thread → public also fits my use case.

4개의 좋아요

Doesn’t Shared Drafts cover this use case more precisely? Do we still need this post-as-unlisted hack?

1개의 좋아요

Thanks for the prompting me about this new feature which I’ve just tried out.

It doesn’t cover our use case because the groups of people who might want to collaborate on a thread might be different. e.g. for one post it might be just me & the company directors, for another it might be with marketing and NOT the other directors. Both drafts would eventually become public, but I’d want different (often gradually expanding) groups of people to be able to see them.

So e.g. here’s a typical workflow:

  • make a PM with an initial discussion list
  • gradually increase the number of people included on the topic
  • discuss & edit a single post in the thread, add discussion to the bottom
  • split the thread to cut off early discussion from a final draft
  • make the whole / partial thread public later.
5개의 좋아요

I see, so this covers the “let random people see it” use case. That’s fair.

2개의 좋아요

이 기능이 여전히 사용 가능한가요? 가능하다면 어떻게 활성화하나요?

2개의 좋아요

여전히 사용 가능하며, 활성화할 필요가 없습니다. 스태프(관리자/모더레이터)는 작성기에서 톱니바퀴 아이콘을 통해 새 주제를 생성할 때 ‘비공개’ 상태를 전환할 수 있습니다.

8개의 좋아요

아, 그렇군요. TPM에서 그룹 DM에 멤버를 추가하는 기능이 작동하지 않고, 해당 기능을 개발 중인 TPM 담당자가 꽤 오랫동안 자리를 비울 예정이라서, 우리 일반 사용자들에게도 옵션이 될 수 있을지 궁금했거든요…

2개의 좋아요

이 부분에 대해, 특정 신뢰 등급의 사용자가 비공개 주제를 생성할 수 있도록 하는 설정이 있나요?

1개의 좋아요

아니요, 그런 기능은 없습니다. 그리고 그런 기능을 추가할 계획도 없다고 생각합니다. 목록에서 제거(Unlisting)는 직원(및 TL4) 전용 기능입니다.

7개의 좋아요

신뢰 수준 4에 도달해야 합니다(수동 승인만 가능하므로, 사용 중인 Discourse 인스턴스에서 스태프와 대화하세요). 그러면 가능합니다.

6개의 좋아요

감사합니다. TL2에서도 이 기능을 사용할 수 있도록 하되, 관리자 승인을 요구하는 방식이 유용할 것 같습니다…

그리고 사소한 건이지만, 이들을 사용자의 북마크에 포함시키는 것이 유용할 것 같습니다. "비공개(unlisted)"라는 속성이 북마크에도 적용되는 것 같아서요…

3개의 좋아요