21–30 of 48 posts
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.
Wait, is this a joke or was there really a great email collapse in 2006?
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 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.
>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?
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?
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 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 popular it will be destroyed by spam and other abuse. (Effectively a sybil attack.) Self-policing protocols (without costly proof of work) are an "AI-hard" problem since your adversary is the human intelligence of the protocol's exploiters.
Niche federated protocols avoid this fate by never becoming popular. The other way to avoid this fate is to impose a severe work function like Bitcoin and other block chains, but this is too expensive (figuratively and literally) for most applications. Could you imagine a forum software that requires a minimum of several hundred watts of power to participate in the network?
All others fall to the tragedy of the commons.
I don't see that type of unprofessional behavior among the users I collaborate with. I guess that's the drawback to working with Millennials. Lazy and time-wasting and always think they are new or funny.
I stopped using Slack. It is a productivity drain.
Using MS Teams at the office and I couldn't agree more. It's useful about 30% of the time. The other 70% is sharing giphies and news links.
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.
Having said that, Google certainly run many many mail servers, as such an outage that impacts delivery for one group of people does not necessarily impact everyone. This is the difference between robust systems and those with critical lynch pins that create system wide outages.
I stopped using Slack. It is a productivity drain.