zlacker

[return to "Open source liability is coming"]
1. sevagh+F6[view] [source] 2023-12-29 18:40:30
>>daniel+(OP)
I find this article and the reactions here confusing. This seems to me like unequivocally a good thing for open-source devs.

Making commercial vendors who rely on open source software liable for bugs is fantastic news, that's how it always should have been. You can't have a commercial company throw their hands up and say "well github.com/cutefuzzypuppy is at fault for writing an open-source npm package we used so harm to our customers is not our fault!"

◧◩
2. grumps+cA[view] [source] 2023-12-29 21:28:57
>>sevagh+F6
How in the world is this good for devs? It's terrible. Do you really think that "big corp" will not figure out how to pass the liability directly to the author?

What will happen the opensource world once you're held liable for some moron who uses some software I wrote for myself? or incorrectly uses it?

do you really believe the curl should be held liable because some POST failed and a user lost something over it?

what about my old backup scripts? I need to remove them from my repos?

◧◩◪
3. moses-+GJ[view] [source] 2023-12-29 22:28:20
>>grumps+cA
I read the article twice, because the link title made me think that I as an open source contributor and publisher liable for complaints.

My reading of the text is that the one actually selling the software product is the one having to abide by this law. Am I incorrect?

How could this be negative? I presume that most publishers of open source software would prefer that some Silicon Valley Unicorn did _not_ half-heartedly integrate their library, causing security issues and tainting their library name?

◧◩◪◨
4. grumps+i81[view] [source] 2023-12-30 03:01:30
>>moses-+GJ
Because lawyers and courts become involved. They don't understand software or anything related to it.
[go to top]