The facts were never argued, the other party failed to follow procedure.
How did IRC ping timeouts end up in a lawsuit?
11–20 of 34 posts
Re: How did IRC ping timeouts end up in a lawsuit?
#12A whole other part of this argument that could be made is about the inherent assumption that a ping timeout is caused by an event that only affects one machine.
Re: How did IRC ping timeouts end up in a lawsuit?
#13Re: How did IRC ping timeouts end up in a lawsuit?
#14A whole other part of this argument that could be made is about the inherent assumption that a ping timeout is caused by an event that only affects one machine.
Ergo isn't a federated server, it's meant to scale vertically
Re: How did IRC ping timeouts end up in a lawsuit?
#15Re: How did IRC ping timeouts end up in a lawsuit?
#16A whole other part of this argument that could be made is about the inherent assumption that a ping timeout is caused by an event that only affects one machine.
Re: How did IRC ping timeouts end up in a lawsuit?
#17A whole other part of this argument that could be made is about the inherent assumption that a ping timeout is caused by an event that only affects one machine.
Imagine them trying to sue every person on one side of a netsplit
Re: How did IRC ping timeouts end up in a lawsuit?
#18Earlier quoted context omitted.
Imagine them trying to sue every person on one side of a netsplit
...and back in my day (yeah I am becoming an old fart), it was dead simple to cause a netsplit on most networks.