3 ms·
What a horrible plan! I mean, I support the basic idea of not wanting your work to be used by, say, the Westboro group. But how could you possibly define "commu
by kstrauser 15y ago
What a horrible plan! I mean, I support the basic idea of not wanting your work to be used by, say, the Westboro group. But how could you possibly define "communication that disparages or discriminates" in any meaningful way? Some cases are obvious (see the above example), but what about someone who's disparaging a repressive government? Last year's Arab Spring protestors wouldn't think that they're being discriminatory or hate-driven, but the local authorities had a different view of the matter. For a (possibly) closer-to-home example, consider the opposing sides of the pro-life/pro-choice debate. Either group would be very likely to accuse the other of disparaging or discriminating against their own "religion, or other characteristic".
Furthermore, some overly-sensitive people interpret anything that doesn't actively support them as opposing them. Who gets/has to decide whether a particular instance of communication "disparages or discriminates": the speaker, the listener, or you?
Also, remember that a license is actually a legal document. Do you really want to have to defend these vague terms in court?
The GNU folks considered such things when crafting the GPL. According to their rationale at http://www.gnu.org/philosophy/free-sw.html http://www.gnu.org/philosophy/free-sw.html , the very first requirement of a free software licence (freedom 0) is:
The freedom to run the program means the freedom for any kind of person or
organization to use it on any kind of computer system, for any kind of overall
job and purpose, without being required to communicate about it with the developer
or any other specific entity. In this freedom, it is the user's purpose that
matters, not the developer's purpose; you as a user are free to run the program for
your purposes, and if you distribute it to someone else, she is then free to run it
for her purposes, but you are not entitled to impose your purposes on her.
While many people disagree with the GNU authors on many finer points, this is a pretty fundamental freedom that many or most free software authors support.
Basically, while I sympathize with the motivation, this just can't work in reality. Nor should it! It sets a very bad example of attempting to impose behaviors on end users and that never ends well.
- GuiA 15y agoThanks for the politely written, well argued criticism! My goal in writing+submitting this was more to ignite interesting conversations like yours rather than to provide a legal document ready to use. That being said, I have to say that in the light of what you said, I would tend to agree with everything that you said. But it still bothers me that it is possible to use free software for "hate" driven causes. If a homophobic/xenophobic/etc. group used my work to efficiently promote their ideals, it would bother me on a deep level. I don't think there's a straight solution to that, but I still feel like it's a problem at some level- despite the fact that yes, attempting to impose behaviors on end users is a very slippery slope.
- deleted 15y ago[deleted]
- kstrauser 15y agoThanks for taking it in the friendly spirit I intended it. Parts may have come across a little more harshly than I planned, but I meant well. :) Again, I totally understand the motivation. I'd hate to think that someone was taking the software that I poured so much hard work into and using it to mistreat others! I think that's just something we have to learn to accept. You can use a rifle to shoot a wild animal or assassinate a political opponent. A knife can open a box or hijack an airplane. Virus manipulation can end a disease or end a country. The best you can do is make sure your own motives are good and hope for the best from others.
- HerraBRE 15y agoA solution may be to provide a template, where developers can list explicitly the activities they do not support. You'd still be imposing your morals and beliefs on others, but at least it could be less ambiguous. This would not be a "free software license" due to the nature of the restrictions, so it would never make it into a distro like Debian for example, but maybe you don't care about that. EDIT: For this to really work you'd probably have to encourage users of the license to be very explicit and give some examples which don't suffer from the slippery-slope problem.