31–40 of 48 posts
I stopped using Slack. It is a productivity drain.
It's harder (but not impossible) to have complete service lossage like this in a federated protocol. That's why you didn't hear about the great email collapse of 2006.
Of course, if my email goes down, it does not help me that other's is still up. In fact, if total downtime is constint, I would prefer they overlap.
So the people who are supposed to do work for you also can't work?
It's harder (but not impossible) to have complete service lossage like this in a federated protocol. That's why you didn't hear about the great email collapse of 2006.
The great e-mail collapse occurred in the late 1990s and early 2000s when spam made it prohibitively difficult for most users to actually run federated e-mail endpoints. At this point it's an amazing pain to the point that very few attempt it. The rest is moot. That's the problem with federated protocols. Without someone who owns the system and who has the resources and central authority to police it, if it becomes p…
It's harder (but not impossible) to have complete service lossage like this in a federated protocol. That's why you didn't hear about the great email collapse of 2006.
>That's why you didn't hear about the great email collapse of 2006. Wait, is this a joke or was there really a great email collapse in 2006?
The top-level routing is held together with duct tape and lots of carefully trained eyes looking for problems with it.
Slack is down, productivity goes up... after using it for a while I find it does communications within a team well but does almost nothing to increase collaboration, so I guess slack is in area which apps like Discord will disrupt.
I don't disagree with you, but in what way do you think Discord will "disrupt" Slack with regards to collaboration?
Earlier quoted context omitted.
Of course, if my email goes down, it does not help me that other's is still up. In fact, if total downtime is constint, I would prefer they overlap.
> In fact, if total downtime is constint, I would prefer they overlap. So the people who are supposed to do work for you also can't work?
It's harder (but not impossible) to have complete service lossage like this in a federated protocol. That's why you didn't hear about the great email collapse of 2006.
>That's why you didn't hear about the great email collapse of 2006. Wait, is this a joke or was there really a great email collapse in 2006?
There have been other Gmail outages in the past though. My two favorites are:
1. The multi-hour outage in 2009 http://www.cnn.com/2009/TECH/09/01/gmail.outage/index.html?e.... 2. And one where they had to restore data from magnetic tape backups https://gmail.googleblog.com/2011/02/gmail-back-soon-for-eve....
Of course, there are other email providers too and their own outages. But I like Gmail and that's what I follow.
Earlier quoted context omitted.
Of course, if my email goes down, it does not help me that other's is still up. In fact, if total downtime is constint, I would prefer they overlap.
> In fact, if total downtime is constint, I would prefer they overlap. So the people who are supposed to do work for you also can't work?
But if everyone's email is down, they won't be able to send those messages, so they won't think we received them to ignore them.
(Then again, email is kind of uniquely bad here, because of the way SMTP works as a store-and-forward protocol. In most protocols, if my server went down, your client wouldn't be able to connect to it, so it'd be pretty clear something is wrong. With SMTP, your client can just "put a message on the Internet" for my server to receive, and won't know for 48 hours or more that my server isn't there any more.)
It's harder (but not impossible) to have complete service lossage like this in a federated protocol. That's why you didn't hear about the great email collapse of 2006.
Of course, if my email goes down, it does not help me that other's is still up. In fact, if total downtime is constint, I would prefer they overlap.
Fortunately, you can have more than one mailbox. Things change with time, so one has to have backup channels anyway.
> In fact, if total downtime is constint, I would prefer they overlap.
To me it sounds like "I'd prefer if everyone would be getting sick at once": not a good scenario at all.
I stopped using Slack. It is a productivity drain.
I've been tempted to stop using it, but instead just shut off notifications. I really like being able to pull it up quickly to see when code has been pushed up, pull requests created / merged, or whatever automated CI action is going on for a particular project. The chatter can burn a lot of time though. You're absolutely right there.