Hacker News, Reddit, Stack Overflow Stats
No public GitHub repository stats available
What is Slack?
Imagine all your team communication in one place, instantly searchable, available wherever you go. That’s Slack. All your messages. All your files. And everything from Twitter, Dropbox, Google Docs, Asana, Trello, GitHub and dozens of other services. All together.
What is RocketChat?
What is Friends?
Friends is like Slack except P2P, offline friendly and open source. We transmit data over secure channels and authenticate messages. It's made by a group of open source developers who are motivated to make a public chat platform that is easy to use but isn't centrally controlled, and where data is owned by its users.
Pros about this tool
Cons about this tool
3955 Companies Using Slack
23 Companies Using RocketChat
1 Companies Using Friends
What are some alternatives to Slack, RocketChat, and Friends?
Great product, great company
April 14, 2014 12:51
Slack filled a very complicated role and did it elegantly.
Its very well designed and easy to use. Adding integrations can be complicated but their documentation with images makes it very easy.
Also I contacted support and get a relevant answer quickly!
All this on the free plan, you better bet we will be upgrading soon.
Simple to use but user accounts could be handled better.
November 14, 2014 18:14
Slack is gorgeous and runs on multiple platforms - that's benefit #1. You can easily talk on your iMac then switch to your Android device on the fly.
The one thing I don't really like about it is how it handles multiple organization accounts.
I am a software consultant so I typically work with multiple teams over the months and it's odd to 'log into the right account'. It's not intuitive at all.
I would like there to be a way for users to easily pick a 'Persona' and not accidentally post to the wrong company.
This is insane: Slack could never crash again
July 05, 2018 09:08
Today the impossible happened, our beloved Slack crashed sending chaos into offices around the globe. “Wow, how am I now going to vote for the flavour of our new office candy???”, I thought. But even though it might not have felt like it, everything else around us was still working: the world was still spinning, South Korea was winning over Germany at the World Cup, and today’s quotas and goals had to be met. In these situations, people most often turn towards traditional messaging tools like messenger, WhatsApp or email and hope for the best — that Slack will be back up soon. However, these temporary remedies are not without their complications: undelivered messages that you thought were read, lost documents, mental breakdowns, wasted time, etc.… In general, for us it creates a problematic gap in our office chat history.
But what if I told you that these crashes could potentially never occur again?
Yes, this is real life, and it’s exactly what mesh technology is about so we are going to explain it. In this scenario, if Slack ran with mesh networks, its users would not have been affected by its current technology’s single point of failure, which in this case was the crash of the server.
Lol okay, how is this possible bc this is real life???
Mesh networks might not sound familiar to everyone so let’s compare it with other well-known networking topologies. Consider a Local Area Network (LAN), where devices are connected to a central access point (imagine it like a star with the central access point in the middle and the devices located at the ends). Be it LAN or wifi, the idea is the same, so when I send a message on Slack, it first arrives at the Slack server (the central access point) and from there it is sent to the recipient.
In mesh networks, devices are directly connected to each other. They form a local network using existing connectivity technologies such as Bluetooth or Wi-Fi as “connectors”. Devices can act as “routers” and forward messages and files to others, enabling the content to hop between them until it reaches a destination. This eliminates the need for a central entity.
Let’s apply this concept to today’s crisis. If slack ran on top of mesh networks, their consumers would still be able to communicate and send files even though they were not connected to the crashed server. Once it was up and running again, all their group conversations which would have taken place during the outrage would be uploaded back to Slack’s server once they were back online.
Honestly, it’s that simple. To Slack, it would not only be convenient for its customers in situations like these (because we would never have Slack crashes), it would also considerably reduce their own infrastructure costs and prevent them from having moments that they might find embarrassing.
So slack, if you see that mesh networks could potentially help you, come talk to us.
March 18, 2018 13:02
Internal Communications made easy
Packet uses Slack
Slack is our hub, we live there to help bring our virtual team members into the fold.
Clever uses Slack
We switched from Slack to Hipchat and have been very happy - we no longer have issues when connecting and disconnecting from our VPN, and robust editing of previous messages is a useful feature.
StackShare uses Slack
I first heard about Slack from my friend Matt (shout out to Final!). He was helping me out with some Rails issues so we started using Slack and I liked it. Specifically, the chat interaction. But also all the integrations. I wasn’t thinking of it as a tool to end all tools at first, just a chat tool with some cool integrations. Then I created a Slack account for StackShare, and that’s when things got real.
Sentry got easier to stay on top of, Heroku was easier to see activity from, discussions were more fluid, and the mobile app was killer. Most of the tools I use either don’t have a mobile app or have shitty ones. Slack is like a replacement for all the mobile apps my tools should have.
I don’t find Slack particularly useful for focused discussions, so I doubt it will replace email anytime soon for us. Things like product discussions/debates are best via email. It forces you to think before you type and have a clear back and forth with someone.
Small gripe: I wish Slack would disable email notifications by default, I still haven’t figured out how to turn those off.
cjsaylor uses Slack
All build, CI, and github notifications go to our dev channel. This also is where we discuss and share documents.
SmartLogic uses Slack
Our team is partly distributed, but we would still use Slack even if it weren't. Keeping conversations asynchronous ensures nobody will be kicked out of "flow" during their most productive hours.
chrisDeFouRire uses Slack
Internally and with our clients, we communicate mostly through slack. We're a remote team, so Slack is our communication backbone
Refractal uses Slack
Slack is a lifesaver, not only for our day to day team communications and it's direct links into our other tools, but for Beta testing as well, with our custom Slack bot in our beta group being an invaluable asset to avoid giving our testers direct JIRA access.
OnlineCity uses Slack
Almost all company communication happens in slack, it's the beating heart of OnlineCity.
megmorsie uses Slack
I have used Slack to communicate with other developers during and after conferences and to replace email notifications from some of the sites I work on at KHM Travel Group.
itzMe uses Slack
For team members not based in the head office and for working with external contractors Slack provides a great tool to communicate, stay in touch and share ideas.
Lumanu uses Slack
As a remote company we rely on Slack for most of our communication. Ease of sharing links, creating private conversations, and developing bots makes it a solid communication tool.
Giant Swarm uses Slack
Slack is our internal communication tool of choice. We also use Slack to provide support to customers and integrate some administrative tools.
Udacity uses Slack
Team coordination, and centralized reporting of deployments, code commits, code review comments, and exceptions in our live stack.
andreikun uses Slack
Group Chat, Error notifications from API, Build Process Notifications and Continous Integration Notifications. Jira Notifications about task changes.
aharrisonwatt uses Slack
A vital communication tool used primary coordinate with my PM. Just a important office communication tool in general.
ralic uses Slack
Algorithm practice and prepare for interview and follow software project discussion.
softwareantelope uses Slack
Stay in touch and record comments, chat about progress and record information that comes to light in the development and support of your project.
nerogit uses Slack
하루 계획 & 회고,
개발 관련 webhook,
trello web hook,
marketing 채널 운영
thibmaek uses Slack
Get notified of build status, deployment status, github changes and internal communication for the team.
Oomba uses Slack
Slack is our primary communication tool both within a single team and company as a whole.
rqtaylor uses Slack
Great for communicating at work. Also have a family Slack to keep in better contact with my brothers and parents.
Sud Web uses Slack
We use Slack for day to day exchanges, confcalls and notification center from external services.
SaberEsPoder uses Slack
Slack is our go-to communication tool and it's slowly replacing emails across all departments of the company. We built our own Slack Bot to help us with simple DevOps stuff; Honeybadger notifies us in real time of errors happening on production in our monitoring channel; CircleCI reports builds status and deployment info as well.
papaver uses Slack
irc for the masses. currently use it with all my clients. great for communication and notes. was introduced a couple of years ago, but originally started using irc 15 years ago.
kfancy uses Slack
Slack is hands down the best business and developer collaboration tool out there. I use it regularly.
kycfeel uses Slack
요즘은 조금 시들하지만 한때 찬란했던 업무용 메신저. 탄탄한 기본 기능에 정말 다양한 플러그인을 만들고 배포할 수도 있어 팀 활동에 사용중. 개인 관리 서버의 모니터링 도구와 Slack을 연결해 푸시 알림도 받고 있다.
Ataccama uses Slack
Slack is used as a company-wide communication tool. In addition, we've got a few channels set up to notify developers about build failures, thrown exceptions on production servers and stuff like that.
HomeUnion uses Slack
Using Slack for all internal product and Engineering team communication, application Alerts & Notifications
Fluxti uses Slack
We use slack as the collaborative platform for our teams linking our core and support repos and our trello cards aswell
andrewgatenby uses Slack
Team comms is essential. The R&D team is distributed over two offices, as well as the chance that people are working from home. Slack provides lots of options of keeping individuals and groups up to date. We also use it to integrate into services such as Github and Sentry.
shridhardalavi uses Slack
Slack is an instant messaging and collaboration system It unifies your entire team communications, making your workflow, well, flow a lot better. It is a cloud-based set of proprietary team collaboration tools and services. Slack teams allow communities, groups, or teams to join through a specific URL or invitation sent by a team admin or owner.
dflynn1024 uses Slack
We use this to collaborate with the DLX team. Our deployment pipeline (Octopus Deploy) sends release notifications to the team on Slack.