Re: "We agree with the district court’s reasoning"
Trollface
>>Re: "We agree with the district court’s reasoning"
>>But really, the judge is perfectly right. Attacking Cloudflare for hosting infringing sites is like attacking >>those who make roads for facilitating a criminal's getaway.
>The problem with your analogy about road makers is that it is fundamentally the same argument as >"guns don't kill people, people kill people", or that social media sites like Facebook, and even so->called bulletproof website operators, should not be held in any way responsible for the content that >they serve. Perhaps you hold both of these beliefs too, which would be fair enough, but they don't >really cut much ice with many people.
>I haven't read the full judgment, but the judge's reasoning described in the article is quite different - >"The plaintiffs have not presented evidence from which a jury could conclude that Cloudflare’s >performance-improvement services materially contribute to copyright infringement". i.e. As far as it >can be imperfectly applied to your analogy, Cloudflare's road improvements did not help facilitate a >criminal's getaway.
With your logic, it would make sense then that Cloudfare can now be the conductor, engineer, and run all the major Fortune 1000 railroad systems combined.
What happens when the conductor decides to turn the content arbitrarily in the direction of rail way that goes off a cliff? Or better yet, a day to day internet user who isn't a bot, but gets his content redirected to an arbitrary locale, at the time the conductor desires.
All is highly switchable to "third" man in the loop, while the internet is great for keeping "stateful" connections - those are called "secured". Transparency means, you have so many hops, and time to live, not setting a user up as a hostage to an non-engineered, non-credentialed or non-regulated set of cables, switches, or disaster prone region of the world.
And for that matter what if I want to "upload" data to my service - the speeds are 1990's dial up modem speeds, why? Download is great, but how do you keep a stateful and secure connection without know where the IPV4 or IPV6 connection gets tunneled without a MAC instead a Lexical search.
I see missing from Cloudfare almost identical regulatory standards any railroad company is mandated with. And it's only short time before it catches up. Much is confusing to any legal officer, but once you look at it from a railroad Conductor or Engineer perspective, you will see the same exact issues, which in essence would you want Cloudfare directing your train down some unknown path???
Biting the hand that feeds IT
