You can use whatever license you want. You can even go ahead and write your own license from scratch.
You'd only have to worry about enforcing the license, especially when you include such unorthodox terms and conditions.
this post was submitted on 18 Jun 2024
23 points (72.5% liked)
Asklemmy
43746 readers
1361 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
I've added a "Everyone except Bob Smith can use this software" a la "fuck Anish Kapoor" clauses for paint colors before.
Though honestly it would be hard to enforce.
In reality, no one worth extorting is going to use a non OSI approved license (or license and exception).
That said, the JSON license says JSON must not be used for evil. Is it any coincidence Google made protobuf as a JSON alternative??
You can write any term you want for your software. There have been instances of people adding terms to their licensing like "You hereby accept to forfeit your soul's ownership to the creator of this software."
Enforcing it is a different problem.
What if the Devil just automatically does the transfer and some prankster gets to hell and is friggin rich with like 20k souls to his name?
Then you get the executive suite.
You can write any conditions you want into a license.
That's what actually differentiates proprietary licenses from open-source licenses.
Open-source licenses follow certain rules, and you usually select an existing license, so therefore they can be reasoned about, collectively. People often implicitly mean "OSI-approved license", when they talk of "open-source licenses".
Proprietary licenses, on the other hand, can contain whatever bullcrap you want.
Having said that, I'm not a lawyer, but I imagine, if you also called your license "GNU General Public License", then a case could probably be made in court, that your license is deliberately confusing.
They can't just contain "any bullcrap you want".
Contracts need to follow the set of rules in your country that dictate what can and can't be enforced. It's an entire branch of law.
If you try and pull something like OP is suggesting, the worst case scenario is that it may render the contract an unlawful document and therefore void.
I imagine in most places things like what OP is suggesting would get laughed out of court.
You can have some fun though. I heard of one guy who, as a recruitment bonus, insisted that it be included in his contract that he receive an office desk made entirely of Lego.
You can write almost any bull crap you want, as long as it obviously doesn't go up against some law and has the main contract elements.
An unenforceable aspect of a contract, won't void the entire contract if it goes to court, unless it's the main aspect of the contract.
Well that depends on the laws where you live but if you actually want the contract to be enforceable then yes, it needs to follow certain rules, and no, you can't just "write any bullcrap".
But you can write whatever crap you want, it can't just be the basis of the entire contract.
Let's say I write a contract for you to supply me bricks for 10 years at a firm fixed price cost of $1 a brick, with an order limit of 100 million bricks. I could then add in elsewhere "if more than 5% of the bricks are damaged, you must supply me with one living unicorn."
That whole contract doesn't become void because unicorns do not exist. In fact, if it went to court a lawyer might even argue with a straight face that the supplier must provide something of equal value to a unicorn.
This one would be like a "GNU General Pubic License."
Oracle Java uses a license called "GPL with Classpath Exception", so it's definitely possible to create derivatives of the GPL and name them appropriately.
Wow, I've definitely seen that before, but I never realized how wild that is. So many companies will start drooling like a dumbass when anything contains the GPL.
So, it's not like they can't ever use GPL software, most do use Linux knowingly or unknowingly. But if you use GPL software in a way the legal department hasn't seen before, they'll always feel uneasy about it.
Frankly, I'm surprised that Java gained any traction in the corporate world at all, then.
The original version of Java was proprietary. Sun later open-sourced large parts of it but they kept selling a version of Java with a proprietary license. There were also random kerfuffles over the years with IBM and Red Hat who wanted to sell open-source Java into large organizations without giving a cut to Sun/Oracle.
So you're telling me there's a chance
The GPL states that its text must not be modified. I take this to mean (though I'm no lawboy), that if you wanted to have a license with the same terms plus some changes (the butthole rule), you would have to rewrite the whole thing. It would not nearly be a "GPL license".
This is very important nitpicking I'm doing here, okay?
Nah, there is the class path exception which is like an amendment to the license sort of. It doesn't change the text of the license, it's just added at the end. Also, nothing is stopping you from dual licensing. In the same way many companies provide a version of their software under GPL but provide a version under an exclusive license if you pay them, you could give people the code under an exclusive license if they send a butt pic.
Creative works are better served by Creative Commons licenses instead of software licenses.
I just like to interject for a moment. What you're referring to as butthole is in fact GNU/butthole, or as I've recently taken to calling it, GNU+butthole.
Fun fact: Buttholes are unique in the same way that fingerprints are. So resubmitting with a new picture can be used as proof of identification and thereby licensing.
Why do I know this, you wonder? Eons ago I stumbled across this anus recognition software source base. The idea was that it could one day be used for identification instead of retina scanning.
OP, make sure that since you'd be collecting personally identifying information, you can comply with GDPR requests.
I'll need some way to verify the software was deleted if the butthole was revoked.
*GDPArse