Optionally threading posts to parent topic in slack integration

@riking A bit, but with some differences.

The announce wouldn’t quite look like that; it would be posted by the watch side of the integration. It wouldn’t say that it was moved. Here’s an example of the current (unthreaded) interface, from the slack integration as I implemented for makerforums:

In the threaded model, the first of those posts would start a slack thread, and Nedman’s comment would instead be in a threaded slack response. When post thread :thread_url is used, the :thread_url would be stored with the new topic and the watch side of the chat integration would post the initial topic post and all further comments to that slack thread, but the content would be the same.

The watch thread integration sends you to discourse where you have to write the title and have the opportunity to edit the new topic post before posting it. So the announcement that is posted to slack already credits the person running post thread as the author, then has a line with the topic title as the link text which links to discourse, and then has a pull quote from the beginning of the post. The change I propose here is that with a non-default and per-channel configuration (so a watch option, not site-wide chat integration plugin configuration), it would post that content to the thread rather than to the channel. (Not “also send to channel” — which would defeat the purpose of the change for us.) Further comments on that new topic in discourse would also go into that same slack thread.

And, since you ask for guesses, 2017, the year that slack rolled out threads?

2 Likes