Compare And Contrast: How GPL Enforces Violations vs. How RIAA/MPAA/BSA Enforce Violations
from the it's-a-bit-different dept
While we've discussed how extreme views in the open source community can, at times, rival the way the entertainment industry acts towards those who violate licenses, reader Nick Coghlan writes in to point to an article that highlights how different they are in many cases, with Bradley Kuhn, the technical director of the Software Freedom Law Center (SFLC), putting forth new guidelines that encourage people not to jump to conclusions when they see potential violations, and to give the benefit of the doubt to anyone they suspect of violating the license. Compare that to the tens of thousands of threat letters sent out by the RIAA, at times with little real evidence.
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Filed Under: copyright, enforcement, gpl, licenses, violations
Companies: riaa, sflc
Reader Comments
Subscribe: RSS
View by: Time | Thread
Re: Re: Re: Freeloaders: Software vs Art
"The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights."
It's amazing that people could misinterpret the GPL's purpose when it's stated so clearly.
Add Your Comment