Wow until about half way through the article I read Discourse as Discord, and it didn't make any sense to me. Now that I understand, this seems like a pretty cool solution. I have been really loving both slack and discord for personal use. Unfortunately, my work use Skype for business. I have been pushing for a switch to slack.
I read exactly the same thing - I was wondering if he was going to start touting how amazing it is to be able to just start talking with people in "Engineering Rooms" or something.
> Discourse has become such an integral part of our company that we abandoned making decisions in meetings entirely.
That's really impressive and cool.
Being an old Usenet fart, I have some problems with Discoure's linear discussion threads (I don't have that problem with twitter's similar structure though).
But I guess if you can keep people on topic and open up new threads for discussions that get side-tracked, it can be a really cool tool.
Have the Discourse developers ever commented on whether they deliberately didn't support visualization of the thread structure? The software appears to know the thread structure (because there's a specific UI to reply to, and quote, a particular message), but it doesn't do much to show it to a reader -- or provide other thread features that you might find in a news reader, like marking a subthread as read or hiding it.
Do we know if this is something Discourse might support in a future version?
Of all sites, I have found all the disparate sbnation sites to have the best live, threaded discussion model. They do it threaded like reddit or HN, but new updates show live and unread and there are various shortcuts to jump to next unread, mark all as read, etc. The key to live, threaded discussion is unread message support.
Sounds like it's working for you. Why people don't turn notifications off is beyond me though. Still, curating/making asynchronous is the biggest issue with slack so thumbs up.
I recently had to deal with some Discourse users trying to hijack my community's discussions to a Discourse chatroom. Absolutely awful experience and terrible client support.
Almost certainly referring to Discord, as Discourse doesn't have chat. Not that people haven't asked us to build it, but I think a good Slack integration is a far better choice, plus Slack is free (in terms of hosting costs, and ease of starting with just 2 or 3 people) in a way that is highly complimentary to what Discourse does.
I like to think of Discourse as the "long term memories" in Pixar's Inside Out. You ship stuff there as you need to. A mixture of mostly short term and sometimes long term memories is a sane and manageable arrangement for most humans.
Could you provide more details on what happened? It sounds like you have a mix of human issues, "users thing to hijack" and something with the product "terrible client support".
I'd be interested to understand what you ran into in more detail.
Instead of going through contortions trying to break bad Slack habits and worrying about the API getting shut off, maybe it's worth checking out something made for the purpose.
In the original post from the AgileBits team quoted at the top, that team tried Basecamp, which to me seems to do a good job of separating thoughtful/long-form discussion from chat, along with the weekend-pause feature.
Very excited about this! We're on the same path of Slack+ Discourse. We tried switching chat to other tools that would be more fit for purpose but just couldn't drive engagement. Slack is too sticky.
I'm planning to take this bot for a spin today. Aside from that, it's just great to hear there are other companies feeling the same pains as we are.
The main reason for not turning off notifications is the fear of missing out, decisions being made without you. And it's a very valid fear.
One team member going away from Slack is bad for the member and for the team. If everyone else participates and you're on the sideline, then you're an oddball and not a team player.
For it to be effective, the whole team has to willingly move away from it.
Not too familiar with Discourse, and I'm curious about the difference to trello comments on a card (in this context of taking discussions offline from slack.)
Could anyone who uses both trello and discourse care to comment about the difference in experience?
We at Dgraph use Trello as well. TBH, the commenting on Trello is primitive compared to Discourse. We still comment on Trello when we're talking about specific cards -- but if it needs thorough discussion, we always go to Discourse.
In fact, it's pretty common for us to create Trello cards out of discussion at discuss.dgraph.io.
Also note that we keep our Slack only for general chit chat. As soon as something becomes more "structured", we switch it to Discourse. We also actively encourage people to just create topics there instead of bringing it on Slack in the first place.
Huh, I can only assume slack is going to remove this api very soon after this, nothing makes companies clamp down on openess sooner then syphoning off users.
I was going to say that's unlikely since the API is part of what makes Slack Slack, but I would have said the same thing about Twitter 6 years ago...
That said, Twitter and Slack are very different beasts. There is not nearly the same network effect to keep teams from switching to a competitor... except to the extent that 3rd party products integrate with Slack's API...
Right on, I approve of this. I wish people would give up on slack already - it's a proprietary hype machine that's made it's way to the core of too many complex systems.
[+] [-] Kratisto|9 years ago|reply
[+] [-] seangrogg|9 years ago|reply
[+] [-] codinghorror|9 years ago|reply
[+] [-] bhaak|9 years ago|reply
That's really impressive and cool.
Being an old Usenet fart, I have some problems with Discoure's linear discussion threads (I don't have that problem with twitter's similar structure though).
But I guess if you can keep people on topic and open up new threads for discussions that get side-tracked, it can be a really cool tool.
[+] [-] schoen|9 years ago|reply
Do we know if this is something Discourse might support in a future version?
[+] [-] kodablah|9 years ago|reply
[+] [-] johanneskanybal|9 years ago|reply
[+] [-] mrjn|9 years ago|reply
[+] [-] tokenizerrr|9 years ago|reply
[+] [-] codinghorror|9 years ago|reply
I like to think of Discourse as the "long term memories" in Pixar's Inside Out. You ship stuff there as you need to. A mixture of mostly short term and sometimes long term memories is a sane and manageable arrangement for most humans.
[+] [-] jSully24|9 years ago|reply
I'd be interested to understand what you ran into in more detail.
[+] [-] JeremyBanks|9 years ago|reply
[+] [-] robbfitzsimmons|9 years ago|reply
In the original post from the AgileBits team quoted at the top, that team tried Basecamp, which to me seems to do a good job of separating thoughtful/long-form discussion from chat, along with the weekend-pause feature.
[+] [-] davidbanham|9 years ago|reply
I'm planning to take this bot for a spin today. Aside from that, it's just great to hear there are other companies feeling the same pains as we are.
[+] [-] mrjn|9 years ago|reply
With Wisemonk keeping us accountable, we're now able to tackle the negatives of Slack; so eager to learn your experiences.
[+] [-] indspenceable|9 years ago|reply
[+] [-] mrjn|9 years ago|reply
One team member going away from Slack is bad for the member and for the team. If everyone else participates and you're on the sideline, then you're an oddball and not a team player.
For it to be effective, the whole team has to willingly move away from it.
[+] [-] pavel_lishin|9 years ago|reply
[+] [-] gingerlime|9 years ago|reply
Could anyone who uses both trello and discourse care to comment about the difference in experience?
[+] [-] mrjn|9 years ago|reply
In fact, it's pretty common for us to create Trello cards out of discussion at discuss.dgraph.io.
Also note that we keep our Slack only for general chit chat. As soon as something becomes more "structured", we switch it to Discourse. We also actively encourage people to just create topics there instead of bringing it on Slack in the first place.
[+] [-] Illniyar|9 years ago|reply
[+] [-] tlrobinson|9 years ago|reply
That said, Twitter and Slack are very different beasts. There is not nearly the same network effect to keep teams from switching to a competitor... except to the extent that 3rd party products integrate with Slack's API...
[+] [-] yoz-y|9 years ago|reply
[+] [-] kefka|9 years ago|reply
Their potential killing of the APIs won't affect if I use Sikuli to automate it.
[+] [-] smaili|9 years ago|reply
[+] [-] yoz-y|9 years ago|reply
[deleted]
[+] [-] mrmondo|9 years ago|reply
[+] [-] Kiro|9 years ago|reply