@John_Lehmann we just implemented exactly this in a plugin
@Hooksmith it may be useful for you, although the plugin does allow the OP to reply to their own topic (e.g. to respond to follow-up questions)
6 个赞
@david this is great, much appreciated. The remaining aspect that would make this perfect, is the ability of the mods to ADD others to the conversation. In our case, the OP would be posting a rating or dispute about a two-way transaction. We’d want to make the other party be aware and able to chime in. Is there any way for this to be done?
The only way you could do this at the moment would be to add those people to a group which doesn’t have replies restricted. Inviting additional people on a per-topic basis would require some extensions to the plugin.
4 个赞
@david thanks for the clarification.
Can you say, what is the level of difficulty of extending this plugin so ad hoc users could be added per thread? It sounds kind of complicated, but I’m not really in a position to judge.
And is there any chance that someone would work on this? Thanks!
Extreme difficulty. Very unlikely to happen. Discourse does not offer per-topic permissions and will never offer it. If you need that, build a group PM.
2 个赞
Thanks for the reply. Sorry for my ignorance, can someone explain what build a group PM would mean? Are you talking about building a different kind of plugin, or are you saying go and use a different software than Discourse?
If you need per topic permissions, write a personal message and include the recipients.
You might describe your use case for some other ideas. If you really want per topic permissions and using direct/personal messages doesn’t suit you, then discourse probably isn’t for you.
EDIT:
Oh! Sounds like I’m a little bit wrong.
2 个赞
If you want to follow the same pattern as the plugin, and simply modify the reply permissions, then it’s relatively simple. Maybe 1-2 days work for someone familiar with Discourse programming. I can see how this would be useful for a Q&A style site.
As Jeff said, trying to modify view permissions per-topic is very difficult, and is unlikely to ever happen. That’s because it would require extensive changes across the whole application including topic lists, suggested topics, notifications, etc. If you need to modify view permissions on a per-topic basis, then use PMs.
3 个赞
Another option rather than adding individuals is to select a Group and send a personal message to only that Group of users. Just be careful that you don’t accidentally spam a whole group:
-
Go to the hamburger menu - the default position is at top right of screen.
-
Select Groups to display all groups.
-
Select the Group you want to send a group PM to.
-
If you have the correct permissions (e.g. PM’s enabled for the forum) then a Message button will be visible
-
Select the Message button to draft a group PM
-
…
2 个赞
Hi guys, thanks for the info. For context, I have a healthy discourse site running now for probably 6 months which is a companion site to my marketplace website. Looks like we are roughly half as active as this meta site so far. Very happy with discourse, working fine, no intention of changing.
However, we’d like to add a special Category where we do public arbitration of disputes. E.g., buyer unhappy with how things went down, as OP they bring a complaint, and then trusted TLX users can reply to gather more info and moderate.
The detail I forgot to mention above is the one thing still missing after this plugin – that we’d also need to easily grant the counter party Reply permission for that topic they are involved in.
- Create: Everyone
- Reply: OP, Group X, Counter Party (added by a moderator?)
- See: Everyone
The value of having these discussions publicly is that the mature community can draw out the reality of what happened in these complex situations and who’s at fault. The history of these threads is high beneficial for building positive and negative reputations. We actually have a ratings system on our site, but it does not get into the details like these 2±way conversations can.
As you can imagine, this kind of “Category” is very messy. However, if we had this setup, I believe we could provide this need for our community better than any previous attempt. They have been many, and the most recent decent one just got deleted off Facebook, years of history wiped out. But that none of these other formats have ever been ideal because of the mess of ignorant 3rd party opinions that they allow.
I would be willing to fund a few days development to create the plugin.
2 个赞
High likelihood that I will be sponsoring the extension of this plugin to support the functionality I just mentioned. In case anyone has suggestions, here’s the proposed approach:
In order to allow additional users to given “ad hoc” Reply permissions on the Topic, the plugin will scan the OP for all mentioned users. This way they can be mentioned at the outset, or moderators could go and edit them into that post.
We feel this is a good approach in terms of a natural workflow, and also sounds easier in terms of implementation (e.g., no UI).
4 个赞
How about you just use the “must approve” settings for the category? It would slow things down since a moderator would need to approve each post but that is probably good in a contentious topic.
3 个赞
我想为原始帖子中指定的“创建”权限提供最新的支持。我们将 Discourse 用作课程论坛，作为 Piazza 的（更）优越的替代品。我们提出了两个使用场景，需要允许用户（学生）在特定类别中创建帖子但无法查看帖子：
- 当学生需要实际在问题中发布代码以寻求帮助时。在这种情况下，我们不希望学生看到其他学生发布的部分解决方案。
- 维护一个学期长的工作日志，记录他们在较长编程项目上的进展。同样，我们希望这些日志包含代码，但学生无法窥探彼此的工作日志。
在这两种情况下，提供类似类别的功能以及对课程工作人员的访问权限都至关重要。
请注意，我们自 2018 年秋季以来，在三个学期中一直尝试使用消息系统来处理上述第一个使用场景。老实说，效果非常不理想。我的班级有数百名学生（秋季 800 人，春季 600 人），还有数百名课程工作人员。至少对我来说，数百条请求作业帮助的消息造成的消息垃圾邮件淹没了来自工作人员和学生的更重要的直接消息，使得整个私信功能变得不那么有用。
因此，我打算建议本学期使用 Google Docs 来实现上述第二个使用场景——遗憾的是，Discourse 本应是更好的选择。但我实在无法忍受由此产生的额外消息流量和混乱。
我不确定上面描述的插件能在多大程度上实现这一功能，但如果能够实现，我们或许可以协助开发。请注意，在我们的情况下，控制主题可见性而不仅仅是回复能力至关重要。
不过，群聊功能可以解决垃圾信息问题。你可以通过仅关注群组来选择“温和”的通知，或者通过静音或将群组设置为普通模式来完全关闭通知。
当你提到使用消息系统时，你指的是否是群聊？（例如，你可以建立一个名为 computing101-staff 的群组，让相关人员在该群组中发送消息，然后该群组的成员可以根据自己的需求选择通知的响亮程度）
2 个赞
我刚才正在编辑我的帖子，想指出我们实际上还没有真正尝试过这种方法，或者尝试得不够深入。有没有一种方式可以实现类似常规话题的处理模式，即我可以不接收某个分类下的所有通知，但可以接收我参与过的消息的回复通知？
除此之外，我大概只能抱怨这些互动被隔离到了论坛的另一个部分，而我更希望它们能与其他话题一起出现在某个分类中。不过，我想这只是一个较小的问题——也许完全可以通过用户界面来解决？我能否让某个消息群组以某种方式显示在分类列表中？
那这样如何？
（以及在最新帖子视图中。）
1 个赞
这是不可能的，这是一个非常不同的类别。尽管如此，在你尝试之前，请不要完全否定它。请尝试一下，并在尝试几个月后反馈结果。
请记住，我们已经尝试消息方法超过一年了。我认为调整音量会有所帮助，但我担心这可能会导致消息被忽略的频率更高。不过，我会提醒我的员工关于可以调整消息组的音量设置。感谢你的提醒。
归根结底，在我们的案例中，确实没有很好的理由在用户界面层面上将学生寻求帮助但不包含代码的话题与包含代码的话题分开。（实际上，如果能按话题级别调整外部可见性，以便我们可以轻松重新分类包含代码但仍需回应的话题，那就太好了。）我们的经验表明，强制通过这些消息系统会使消息功能变得不那么有用，嗯，就是消息功能本身 。无论如何，我理解我们在这里属于更小众的使用场景，但我们已经开始尝试说服更多人将 Discourse 用作课程工具，我认为更无缝地支持这种功能将有助于加强这一论点。
我担心的是，如果我们开始在这里将油和水混合，那么为什么在用户体验中还要将“消息”单独放在一个部分？不如将所有消息和主题都放在首页的一个大列表中，供所有人查看？
我可以创建内容，但只能看到某个类别的子集，这本质上就是针对特定用户的私信。
3 个赞