Hacker News new | ask | show | jobs
by tangotaylor 31 days ago
This is a potential loophole. Companies could have an "open source" OS but restrict installations like Tivo did in the 2000s (i.e. "Tivoization"). Or they could allow installation of modified software but restrict functionality like the way the Google Play Integrity API can nerf apps running on custom builds of Android.

Or, they can have a license like the Business Source License where you can copy, redistribute, and modify the software but you can't use it commercially. This goes against OSI's open source definition.

We emailed this amendment to Buffy Wicks's staff:

§1798.504(f) This title does not apply to[...]:

(4) An operating system or application that meets both of the following conditions:

(A) The operating system or application is distributed under license terms that permit a recipient to copy, redistribute, and modify the software, including for commercial purposes and without payment of a royalty or fee.

(B) The operating system provider or developer does not, by technical or contractual means, prevent the recipient from installing modified versions of the software on a device on which the unmodified version operates, and does not restrict the functionality or interoperability of modified versions.

1 comments

That's great, thank you.

> copy, redistribute, and modify the software

Shouldn't that specify the code not or not only the software? For example, the corporate Windows license allows the corporation to copy, redistribute (internally), and modify (via group policy, APIs, or development on the Windows platform) the software. The big difference between that and Linux is licensees can't access the code. FOSS requires free access to, use of, modification of, and redistribution of the code.

Honestly you're probably right, code is a better term. I copied that language from Colorado's SB26-051 bill which also has a FOSS exemption and they use the word "software". I'm not a lawyer but I'm hoping that a court's interpretation of one state's language will apply to other states.

That and lots of FOSS licenses use some variant of those words "copy, redistribute, and modify" so it's probably a term-of-art that courts recognize.

This is what Colorado's law says. It prevents Tivoization but not feature nerfing like the Play Integrity API.

§ 6-30-105 (3)

(e) AN OPERATING SYSTEM PROVIDER OR DEVELOPER THAT DISTRIBUTES AN OPERATING SYSTEM OR APPLICATION UNDER LICENSE TERMS THAT PERMIT A RECIPIENT TO COPY, REDISTRIBUTE, AND MODIFY THE SOFTWARE WITHOUT ANY PLATFORM-IMPOSED TECHNICAL OR CONTRACTUAL RESTRICTIONS IMPOSED BY THE PROVIDER OR DEVELOPER ON INSTALLING ALL MODIFIED VERSIONS.

I suppose using the broader term, software, doesn't hurt FOSS. It just might extend the law to others.