aspragg
Bradley M. Kühn@richardfontana wrote…
> “[Linus'] reading of initial attempts to address what at the time was described as ‘Tivoization'…”
…properly nuanced, nevertheless FUD continues re: so-called #TiVoization.
TLDR:
* TiVo's #GPL violation didn't relate to lockdown.
* To comply w/ v2, #TiVo allowed modified #Linux install (just proprietary TiVo app wouldn't work after).
* #GPLv2 & LGPLv2.1 *require* right to installation.
* #GPLv3's both looser & stricter—mainly,it's just different.
https://sfconservancy.org/blog/2021/jul/23/tivoization-and-the-gpl-right-to-install/
“Tivoization” & Your Right to Install Under Copyleft & GPL
Two schools of thought about the purpose of copyleft have been at odds for some time. Simply put, the question is: are copyleft licenses designed primarily to protect the rights of large companies that produce electronics and software products, or is copyleft designed primarily to protect individual users' rights to improve, modify, repair, and reinstall their software?
Misinformation & FUD continues re: so-called #TiVoization. *Many people* still misunderstand issues re: #GPLv2 vs. #GPLv3 on installation & device lock-down.
TL;DR:
* TiVo's #GPL violation didn't relate to lockdown.
* To comply w/ GPLv2, #TiVo *allowed* installation of modified Linux, but proprietary TiVo app stopped working if you did.
* GPLv2 & LGPLv2.1 *require* right to installation.
* GPLv3 is sorta looser & sorta stricter— mainly, it's just different.
https://sfconservancy.org/blog/2021/jul/23/tivoization-and-the-gpl-right-to-install/
#copyleft
“Tivoization” & Your Right to Install Under Copyleft & GPL
Two schools of thought about the purpose of copyleft have been at odds for some time. Simply put, the question is: are copyleft licenses designed primarily to protect the rights of large companies that produce electronics and software products, or is copyleft designed primarily to protect individual users' rights to improve, modify, repair, and reinstall their software?
brozu ▪️Do you know what “#Tivoization” means?
#RichardStallman coined this term to criticize a practice that restricts user freedom: even with free and opensource software, some devices block the execution of modified versions.
Yes, but why this name?
It simply takes the name of the first product (Tivo) this terrible practice was applied.
Did you know? 😬
Todd A. Jacobs | Pragmatic CybersecurityHave the open source and open data communities, including organizations like the @eff, @creativecommons, or the @fsf, given any thought yet to updating various #FOSS and other licenses to address the current #SaaS problem of code or data that isn't necessarily being "redistributed," allowing these companies to dodge the obligation to contribute changes back upstream? How about the privatization and unauthorized commercialization of material licensed under the #GPLv3 and #FDL, #CreativeCommons licenses, and other open-license content that is often scooped up regardless of licensing into #AI #datasets that are then put behind #paywalls?
To me, this seems very similar to the #Tivoization problem that led to the evolution of #GPLv2 to #GPLv3. It seems wrong that #OpenAI or #GitHub_Copilot can profit by putting licensed code, writing, or other data into a walled garden where even the original contributors that they rely on are charged for access.
I'm not anti-business. If these companies were at least making the data sets freely available, there's nothing intrinsically wrong with making value-added profit off of properly-licensed data, although examples like CC-BY-NC 4.0 are a notable exception that should also be considered. Companies like Canonical, Red Hat, IBM, and others have been making money legally off of open source software for decades.
Just because the label "AI" is slapped on something doesn't mean that companies should be allowed to ignore copyrights or licensing terms. If they want to do that, and licensing or requiring free access to open-content data can't prevent this land-grab, perhaps its time we collectively revisit the whole framework around #intellectualproperty that currently allows corporations like #Disney and uncountable #PatentTrolls to create ever-expanding assertions of property rights that prevent almost any material from entering the public domain within a single human lifetime.
Todd A. Jacobs | Rubyist@fsf Has there been any thought given to updating the #GPL or FDL to address the #SaaS problem where code isn't necessarily being "redistributed," or the privatization and unauthorized commercialization of material licensed under the GPL, FDL, or similar open licenses in #AI #datasets?
It seems very similar to the #Tivoization problem that led to #GPLv3. It seems wrong that #OpenAI or #GitHub_Copilot can profit by putting our GPL-licensed data behind a #paywall.
LisPi@rq #Tivoization is anathema.
@PeterCxy @Fairphone @miklo @rysiek #Tivoization is a horrible sin.
It needs to be banned entirely.
@chjara @lanodan So long as it's #GPLv3 (that is, with the anti #tivoization additions) that's fine.
#DRM you can remove is the only type I'll accept existing. It's also completely futile and pointless, but that's fine by me.
Trolli Schmittlauch 🦥Dear #freesoftware #legal community: I need some help finding comments on #GPLv3 #tivoization clause and whther the term "user product" covers the case of your company handing out devices to you as a work tool.
I need to convice someone that they don't have to give their employees root access on in-house devices (mobile phones).