4 ms·
You'll get more downtime hosting your own chat server. But you can also fix it immediately when something breaks.
by anderspitman 6y ago
You'll get more downtime hosting your own chat server. But you can also fix it immediately when something breaks.
- paxys 6y ago> But you can also fix it immediately when something breaks. Assuming that a random company will pay to have engineering/ops staff on-call 24x7 who all have enough knowledge about their internal chat system.
- anderspitman 6y agoI don't think there are many companies that don't already have at least a couple things that must stay up 24/7. Who fixes those? Or pay a company to host your chat system, but use an open source server and just have them manage your instance. If something goes wrong, you email them and they can quickly fix the issue. Because it's a simple system and they know the problem exists on your node. Besides, I don't need it 24/7. There's always email for that. I need chat during working hours. Slack is currently not fulfilling that need, and even if I could get ahold of someone there, that person wouldn't be able to fix my problem. Their system is too complex.
- tyre 6y agoif this slack outage lasts 6 hours, it's far less time then someone would spend futzing around with their own chat server that includes deployments, updates, security audits, etc.
- anderspitman 6y agoHonestly I don't even care if I had to spend 10x more time fiddling with hosting my own. The advantage is choice. If it breaks on a Friday afternoon, maybe we don't care and just call it for the weekend. But if it breaks in the middle of coordinating a deployment (like today), it can become priority #1 on the team until it's resolved. With slack I have no control.