What is Discord?
Who uses Discord?
Why developers like Discord?
Here are some stack decisions, common use cases and reviews by companies and developers who chose Discord in their tech stack.
Shortly after I joined Algolia as a developer advocate, I knew I wanted to establish a place for the community to congregate and share their projects, questions and advice. There are a ton of platforms out there that can be used to host communities, and they tend to fall into two categories - real-time sync (like chat) and async (like forums). Because the community was already large, I felt that a chat platform like Discord or Gitter might be overwhelming and opted for a forum-like solution instead (which would also create content that's searchable from Google).
I looked at paid, closed-source options like AnswerHub and ForumBee and old-school solutions like phpBB and vBulletin, but none seemed to offer the power, flexibility and developer-friendliness of Discourse. Discourse is open source, written in Rails with Ember.js on the front-end. That made me confident I could modify it to meet our exact needs. Discourse's own forum is very active which made me confident I could get help if I needed it.
It took about a month to get Discourse up-and-running and make authentication tied to algolia.com via the SSO plugin. Adding additional plugins for moderation or look-and-feel customization was fairly straightforward, and I even created a plugin to make the forum content searchable with Algolia. To stay on top of answering questions and moderation, we used the Discourse API to publish new messages into our Slack. All-in-all I would say we were happy with Discourse - the only caveat would be that it's very helpful to have technical knowledge as well as Rails knowledge in order to get the most out of it.
From a StackShare Community member: “We’re about to start a chat group for our open source project (over 5K stars on GitHub) so we can let our community collaborate more closely. The obvious choice would be Slack (k8s and a ton of major projects use it), but we’ve seen Gitter (webpack uses it) for a lot of open source projects, Discord (Vue.js moved to them), and as of late I’m seeing Spectrum more and more often. Does anyone have experience with these or other alternatives? Is it even worth assessing all these options, or should we just go with Slack? Some things that are important to us: free, all the regular integrations (GitHub, Heroku, etc), mobile & desktop apps, and open source is of course a plus."
We use Discord to tracking some action and errors (logs / alerting / assertion). it's free and simple to use with mobile application et notifications
Discord has become a regular part of life. Since I belong to a lot of gaming groups, there's no better alternative than Discord at this moment to discuss with team. It has a facility of custom bots to automate a lot of stuff or simply play your favorite music during the gameplay. Trying out its new game streaming feature to see how it can possibly replace Twitch at some point in time.
Our Discord Server is our n°1 community stop; we gather feedback from our users from here, discuss about new features, announce new releases, and so on.
We even use it for internal meetings and calls !
Discord is used for all the discussions with our community, and discussions between our entire staff (including Community Managers, Chat Moderators and BATs). We also use a Discord bot we developed to deploy new code to the server. Discord