3 ms·
> "Hey guys, remember when _all of IRC_ went down?" I certainly remember downtimes, and netsplits bad enough that it would have made team collaboration impossi
by pavel_lishin 5y ago
> "Hey guys, remember when _all of IRC_ went down?"
I certainly remember downtimes, and netsplits bad enough that it would have made team collaboration impossible depending on who was connected to what.
I think the lesson here isn't "run and maintain your own version of X", but "make sure you have other ways to communicate besides X".
- dijit 5y agoI think that's a fair conclusion honestly, though the cynic in me does want to point out that people do integrate their work against slack and that is difficult to maintain in parallel. Netsplits are mostly a solved problem these days, both with increased reliability of the internet and with network failure proxies like RobustIRC (for the linking protocol); and I remember fondly the times where we had a single IRC instance for all of our company (which had people working across: Thailand, USA and N.Europe) without issue. But, yeah, I think what you said is completely fair.
- pavel_lishin 5y ago> though the cynic in me does want to point out that people do integrate their work against slack and that is difficult to maintain in parallel. Tell me about it! Two minutes after I posted that comment, I realized that our deploy system relies heavily on Slack.
- Hamuko 5y ago>I realized that our deploy system relies heavily on Slack. How? The only deployment integration we have for Slack is that we get a message when a deployment start and when a deployment ends.
- Spivak 5y ago@deploybot do_release v2.3.45 I mean I've seen weirder. For Slack specifically I had a fight with a dev team because their deploy tool failed if it couldn't push a message to Slack.
- u801e 5y agoI can't think of a time where the internal IRC server where I work went down. Netsplits shouldn't be an issue for that particular use case.
- outworlder 5y ago> I certainly remember downtimes, and netsplits bad enough that it would have made team collaboration impossible depending on who was connected to what. But it certainly wasn't all the entire IRC network(s). Which is the parent's point. Slack is centralized. It was a common practice back then to have one "server". You would be hard-pressed to find mentions of "high availability" as servers were a very scarce resource. Small networks sometimes repurposed existing machines that were serving other workloads and added the IRC daemon.
- stickfigure 5y agoWhy does it matter to me if all of slack goes down at once? I only interact with "my" slack. There is no material difference to my team's experience if "all of slack" goes down vs "our standalone chat server" goes down. The only relevant issue is whether or not Slack's team creates a more reliable service than my poorly maintained homegrown solution.
- andrepew 5y agoFrom my perspective as a business, I don't see a difference between my server being down and all of IRC being down. Either way my comms are down. All I care about as a business is about frequency and duration of those outages. If Slack outdoes whatever my in house solution is, Slack wins in reliability. You can make arguments about the net impact on society of everything being down, but from my perspective as an individual business, having everything down is a win was well. If I explain to client that we have a delay because our in house service is down -- fault falls on our business. If I explain to a client it is because Slack is down, odds are they'll blame Slack, not us. This is especially true if they're impacted by the Slack outage as well or the outage makes news outlets. Outages from services likes Slack, AWS, etc. that are wide spread are almost treated like acts of god. Clients seem to be far more forgiving for those sorts of issues in my experience.
- _jal 5y ago> If I explain to client that we have a delay because our in house service is down -- fault falls on our business. This is an under-appreciated competitive advantage "cloud" services offer - outsourcing blame. Somewhat similar to using staffing agencies as lawsuit shields.