Live data from Hacker News

How did IRC ping timeouts end up in a lawsuit?

mjg59.dreamwidth.org

11–20 of 34 posts

Re: How did IRC ping timeouts end up in a lawsuit?

#14
post #12

A 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

The internet is a "federated" network though, so their point still applies.

Re: How did IRC ping timeouts end up in a lawsuit?

#15
This vaguely reminds me of years ago when a friend got hit at an intersection and went to court to fight that he wasn't at fault. I ran the numbers a bit and found that whoever hit him would've been moving at a very high though not outlandish (think maybe 60mph in a 30mph or something) speed. But they never showed up and he won by default

Re: How did IRC ping timeouts end up in a lawsuit?

#17

A 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

...and back in my day (yeah I am becoming an old fart), it was dead simple to cause a netsplit on most networks.

Re: How did IRC ping timeouts end up in a lawsuit?

#18
post #17

Earlier 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.

I'll admit to sending a couple of the messages that made Linksys routers restart. I also set up automatic k-lines on Snoonet for these very strings, years ago
Post reply on HN