Hey all, following up on this proposal: #Helpdesk channel on Slack (proposal to close the channel) and a thread here: I’ve heard a number of people say Julia is not mainstream because it doesn’t have many stackoverflow questions answered but they don’t know about discourse , I decided to work activel…

[image] kevbonham: but that’s gonna get old fast I have an issue open for this and am looking into it: Formatting issue when the message from Slack includes special characters · Issue #8 · JuliaCommunity/SlackBridge · GitHub

So there’s a rather long winded discussion thread currently on Slack about this bridgebot, and I’d like to just copy over a couple points I made there to here for posterity. I think that the Bridge-Bot is creating a flood of noisy, unhelpful, low quality posts on this Discourse that have a very low…

One possible solution that might fix a few problems: Instead of replying to a post in a thread, the bot can Direct Message the author with a more verbose message. The key point of this will ask them to potentially edit this original message with more details so folks on discourse can help easier, e…

I think the bot’s visibility is not the real problem - if a user posts a clear, carefully-crafted question and is immediately answered by a bot who implies that their post might lack detail, that’s bad whether it happens in public or in DMs. Look at MS Word’s Clippy or impenetrable call center keypa…

Instead of replying to a post in a thread, the bot can Direct Message the author with a more verbose message. The key point of this will ask them to potentially edit this original message with more details so folks on discourse can help easier, etc. Thank you @logankilpatrick for doing the heavy …

[image] logankilpatrick: One possible solution that might fix a few problems: With respect, and appreciation of all the work that went into implementing this bridge, I would propose that it is just discontinued. It was an interesting experiment with good intentions, but I don’t think it is wo…

I agree with Tamas, it’s better to discontinue this experiment. There is nothing wrong in negative outcome, in the end of the day that’s what experiments are for. But sunk cost fallacy better to be avoided.

The ideal situation seems to be the following: A user writes a nice descriptive question (that has the possibility of a good answer) in #helpdesk in Slack. The user gets the answer on Slack, typically over a set of chat messages. After getting an answer on Slack, the user summarizes the answer nic…

I agree with Tamas and Kristoffer . I also feel like the only thing the bot achieves at the moment is extra noise on both Slack and Discord. [image] Tamas_Papp: FWIW, I decreased my involvement on Discourse because the noise just got to be too much. Discourse lets you mute categories complet…

Back when there was discussion about closing the #helpdesk channels, I made a point about trying to encourage users to post their questions to Discourse first. I still find occasionally that answers to basic questions that have likely (though not definitely) been asked on Slack/Zulip are not present…

Bridging Slack's #Helpdesk and Discourse (Proposal, feedback welcome!)

Community

logankilpatrick March 20, 2021, 3:56am 44

Update, bridge has been shut down indefinitely.

Low rate of opt-in for the Discourse Bridge on the Slack Help Desk

New BridgeBot, are answers bridged back?

Topic		Replies	Views
#Helpdesk channel on Slack (proposal to close the channel) Community announcement	61	4641	January 18, 2021
New BridgeBot, are answers bridged back? Meta Discussion	19	1219	March 23, 2021
Why a 10,000 message limit promotes better communication for large communities Community	17	2434	May 5, 2020
Link to Julia questions on StackOverflow Meta Discussion	30	5303	June 16, 2017
Slack and the value of community heritage Community	37	3165	May 11, 2021

Bridging Slack's #Helpdesk and Discourse (Proposal, feedback welcome!)

Related topics