th3l3mons

GitHub is already expected to comply with DMCA takedowns just like they have to comply with counter notifications. That's how they maintain a safe harbor, though the latter is a bit harder to truly enforce (see the recent Twitch kerfuffle).

Apple has used US Customs to seize parts intended for repairs, including parts from donor boards. Apple sued (and last I knew was trying to appeal) a Norway repair shop for repairing iPhones using "counterfeit" components. iirc, some parts, including the display, must match appropriately or the OS won't boot as a form of parts validation, effectively preventing display swaps when repairing.

I don't think the previous comment was licensing the design. Apple has been very aggressive with donor parts and data recovery.

To piggy back, this also goes down the dependency chain. Leftpad wasn't bad because it was being used directly. Projects imported other libraries which either directly pulled leftpad or, more likely, pulled another library which may be the calling party or not.

It's been a few years but the libraries needed for different OSs changes. The source and imports needed between Linux and Windows differs. Also comes with some other baggage, like I don't recall if Windows offers a Unix socket implementation.

The other side I would pose is: do you want anyone to alter your responses? I'm currently trying to find the RFC, but I recall an ISP defining an RFC for tampering with HTTP responses in-transit. In addition, I also recall seeing Comcast (I believe) injecting JS to users that they are approaching their plan limits.

Obviously, not the end of the world. But do you want any third party to easily alter the response from your server to the client(s)?