News for hackers. Stuff that matters.
Re:The Unlicense is an inferior license wrapped in an atroci... by hannob on Friday March 04, 2022 @08:59AM (#30554776)
I wish people would get together to agree upon a public domain alike software license that everyone finds acceptable.

That'd mean:

* OSI approves it

* FSF approves it

* Google and other companies with large stakes in FOSS find it acceptable

* Github + Gitlab support it in their templates

Can we have that?

Re:The Unlicense is an inferior license wrapped in an atroci... by jhardy54 on Friday March 04, 2022 @09:28AM (#30555225)
That’s the 0BSD. I called it the Free Public License when submitting to OSI, but we changed it to 0BSD because Landley had apparently come up with the same license a few years before me.
Re:The Unlicense is an inferior license wrapped in an atroci... by dmulholl on Friday March 04, 2022 @02:26PM (#30559228)
Thanks for this. 0BSD has been my default license since I discovered it. My only issue with the MIT license was the requirement for attribution, which always seemed like an unnecessary pain. 0BSD fixes that.
Re:The Unlicense is an inferior license wrapped in an atroci... by freemint on Friday March 04, 2022 @09:57AM (#30555699)
Can you post the FPL text? I am wondering whether it was literally the same license.
Re:The Unlicense is an inferior license wrapped in an atroci... by jhardy54 on Friday March 04, 2022 @11:36AM (#30556986)
It’s the same text, which is just the ISC license sans the “ provided that the above copyright notice and this permission notice appear in all copies” clause.

The only differences:

- I didn’t use the “Copyright Boaty McBoatface 2022” line, but that’s not a big enough change to justify having two licenses.

- The license was approved as the FPL-1.0.0, which I believe was the first OSI-approved license that user semantic versioning. This isn’t necessary, but I was mildly excited about it.

- The 0BSD doesn’t actually inherit from any other BSD license, the “BSD” bit is more of a spiritual nod that I found more confusing than helpful.

Re:The Unlicense is an inferior license wrapped in an atroci... by freemint on Friday March 04, 2022 @03:19PM (#30559920)
> The 0BSD doesn’t actually inherit from any other BSD license, the “BSD” bit is more of a spiritual nod that I found more confusing than helpful.

Don't tell Rob Landley that (the creator of the license). He is quite adamant that he used a BSD license as the basis.

Re:The Unlicense is an inferior license wrapped in an atroci... by alexwennerberg on Friday March 04, 2022 @09:14AM (#30555004)
Re:The Unlicense is an inferior license wrapped in an atroci... by rdpintqogeogsaa on Friday March 04, 2022 @11:22AM (#30556806)
0BSD is actually incompatible with a desired pure CC0. Unlike CC0, 0BSD keeps copyright intact. It's just a license with no conditions except the usual disclaimer; CC0 attempts to cause a public domain dedication wherever possible. Consider the following:

1. Let there be a file F. F is released to the public under 0BSD.

2. Let there be a project P. P includes code from F. The license notice of F is scrubbed as part of the inclusion process.

3. P is released as CC0.

The author of P cannot release the project as CC0 because the author has no right dedicate another person's code (F) to the public domain. Because 0BSD doesn't cause a public domain dedication in jurisdictions that accept doing so, F would have to continue being separate and explicitly exempt from the effects of CC0 to be an accurate of its usage terms. Effectively, this makes 0BSD be a de-facto attribution license in a CC0 project. In practice, it makes no difference, but it's legally deeply inelegant.

Re:The Unlicense is an inferior license wrapped in an atroci... by hannob on Friday March 04, 2022 @10:01AM (#30555763)
Fails on criterion 4, and I think that's a real issue.

Github is the de-facto default sourcecode plattform. If it isn't a standard option on Github then it doesn't feel like a standard license.

Re:The Unlicense is an inferior license wrapped in an atroci... by ahelwer on Friday March 04, 2022 @09:27AM (#30555202)
Not an alike license.
Re:The Unlicense is an inferior license wrapped in an atroci... by marcinzm on Friday March 04, 2022 @09:44AM (#30555482)
...isn't that literally the opposite of public domain? You can't have it both be public domain with no copyright and ALSO use copyright to enforce what people do with their copies of it.
Re:The Unlicense is an inferior license wrapped in an atroci... by freemint on Friday March 04, 2022 @09:42AM (#30555454)
What do you mean? CC0 and 0BSD are both public domain equivalent.
Re:The Unlicense is an inferior license wrapped in an atroci... by ghaff on Friday March 04, 2022 @10:26AM (#30556070)
CC0 isn't an OSI-approved license. (It was withdrawn from consideration around patent language concerns.) MIT-0 (or probably 0BSD now as well) is probably the closest you get to a public domain license to the degree that putting something in the public domain is recognized in a given jurisdiction.
Re:The Unlicense is an inferior license wrapped in an atroci... by donatj on Friday March 04, 2022 @10:29AM (#30556108)
MIT-0 is pretty close as well.

https://opensource.org/licenses/MIT-0

Re:The Unlicense is an inferior license wrapped in an atroci... by smasher164 on Friday March 04, 2022 @10:47AM (#30556347)
It lacks OSI approval, though -- which is a big one. I suppose someone could jump on the OSI mailing lists to get it through the approval process, but it hasn't been done yet.
Re:The Unlicense is an inferior license wrapped in an atroci... by ghaff on Friday March 04, 2022 @10:50AM (#30556389)
It is. https://opensource.org/licenses/MIT-0 (Relatively recently.)
Re:The Unlicense is an inferior license wrapped in an atroci... by smasher164 on Friday March 04, 2022 @11:14AM (#30556712)
I stand corrected.
Re:The Unlicense is an inferior license wrapped in an atroci... by indymike on Friday March 04, 2022 @10:36AM (#30556210)
> Google and other companies with large stakes in FOSS find it acceptable

There are really a lot of times that this is not important, or may be detrimental to your projects success.

Re:The Unlicense is an inferior license wrapped in an atroci... by kemitchell on Friday March 04, 2022 @12:17PM (#30557499)
Blue Oak Council, a gaggle of savvy open licensing lawyers, published a model permissive software license: https://blueoakcouncil.org/license/1.0.0

There's a brief write-up here: https://blueoakcouncil.org/2019/03/06/model

All of us have direct experience with both OSI and FSF license processes. We have no desire to deal with them again. Even for a thoroughly noncontroversial permissive license.

I'm executive director of Blue Oak Council.

Re:The Unlicense is an inferior license wrapped in an atroci... by mattarm on Friday March 04, 2022 @01:05PM (#30558164)
> All of us have direct experience with both OSI and FSF license processes. We have no desire to deal with them again.

As a more casual person looking to use a license, this is basically the opposite of what I want to read.

As a non-lawyer, I have little chance of vetting a license myself. As a person with life experience, I have full appreciation for the delicacy of these kinds of licenses and legal issues.

If a license has consensus from OSI, FSF, Debian, maybe a FANG company or two, etc., then I have some trust that a kind of validation and peer review has occurred. I fear that using a license for which this has not occurred puts the users of my software at risk, or at least shifts the burden of future validation on to them.

TLDR: everybody knows what MIT, BSD, Apache, and the various GPL licenses imply. I think other bespoke licenses have a pretty high bar to clear before they become truly useful.

Re:The Unlicense is an inferior license wrapped in an atroci... by kemitchell on Friday March 04, 2022 @01:16PM (#30558303)
I've written a bit on my experiences with OSI review in particular, and also the list of licenses it has approved. See, e.g., https://writing.kemitchell.com/2019/05/05/Rely-on-OSI.html. In a nutshell: people think there's a team of lawyers back there, counting angels on the heads of fine legal pins. But it's actually a highly politicized mailman list where activist-types do most of the talking.

I put energy into cofounding Blue Oak Council to publish rigorous resources, like our permissive license list, https://blueoakcouncil.org/list, in large part out of disappointment and dread, pulling back the curtain on the institutional processes for license review. As lawyers, we need functional resources like that license list, to incorporate by reference into contracts and policies. Fundamentally political artifacts, like OSI or FSF or Debian whitelists, are type errors in those contexts.

> everybody knows what MIT, BSD, Apache, and the various GPL licenses imply

I'm afraid that's not true. I would say there is broad agreement on many of the core aspects. And in many situations, practically, the specific license terms don't matter nearly as much as widely help expectations. But key concepts affecting fairly common situations remain unclear, and those details come out when there's money or strategic leverage on the line. See, e.g. the list Heather Meeker keeps at https://heathermeeker.com/open-source-faq/what-are-the-most-... See also the whole debate on permissive licenses and standards-essential patents: https://writing.kemitchell.com/2019/10/03/Open-Standards.htm....

Re:The Unlicense is an inferior license wrapped in an atroci... by chrismorgan on Friday March 04, 2022 @11:39PM (#30564306)
Thanks for chipping in on this thread, you’re expressing things nice and clearly, now I have a few more links for describing this unhappy situation in open-source licensing.

Any chance you could change the slug on that first link from Rely-on-OSI to Dont-Rely-on-OSI-Approval or similar? The current URL suggests the opposite of the article’s content. Hopefully adding a redirect isn’t too onerous.

Re:The Unlicense is an inferior license wrapped in an atroci... by kemitchell on Saturday March 05, 2022 @12:18PM (#30569477)
Point taken on page URL. Alas, it's been up a while and I don't have a ready redirect mechanism in place.
Re:The Unlicense is an inferior license wrapped in an atroci... by jobigoud on Friday March 04, 2022 @01:21PM (#30558385)
From the license text:

> You must ensure that everyone who gets a copy of any part of this software from you, with or without changes, also gets the text of this license or a link to https://blueoakcouncil.org/license/1.0.0.

To me this sounds like a viral public domain, so in a sense less permissive than MIT & co. If I modify the work but still have to put the text of this license when publishing it, the modified/derivative will be licensed under this license as well. Is this a fair assessment or am I missing something? I don't see how someone could take the work and use it in a proprietary software for example.

Re:The Unlicense is an inferior license wrapped in an atroci... by kemitchell on Friday March 04, 2022 @01:49PM (#30558745)
> If I modify the work but still have to put the text of this license when publishing it, the modified/derivative will be licensed under this license as well.

How does that follow? Compare:

MIT:

> The above copyright notice and this permission notice (including the next paragraph) shall be included in all copies or substantial portions of the Software.

BSD: > 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. > > 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

Re:The Unlicense is an inferior license wrapped in an atroci... by kibwen on Friday March 04, 2022 @01:51PM (#30558779)
I'm not sure the reason for bringing up that clause, when the same clause exists in the MIT license:

"Permission is hereby granted [to do so-and-so] subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software."

If you're shipping MIT-licensed software (or anything derived from MIT-licensed software) without also shipping a copy of the license, then you're not in compliance with the license.

Re:The Unlicense is an inferior license wrapped in an atroci... by _ZeD_ on Friday March 04, 2022 @09:17AM (#30555059)
isn't it cc0?
Re:The Unlicense is an inferior license wrapped in an atroci... by hsn915 on Friday March 04, 2022 @10:23AM (#30556049)
The problem with CC0 is it's very wordy and very legaleeze, which means I don't want to bother trying to understand it, and potential users won't either.

A one-line sentence should be more than enough to clarify my intent.

Re:The Unlicense is an inferior license wrapped in an atroci... by zarzavat on Friday March 04, 2022 @10:41AM (#30556263)
Public domain. Concise. Effective. Choose any two.

The issue is that donating to the “public domain” isn’t a thing in many jurisdictions, so if you want a license that is effective everywhere then it needs to be wordy. If you are happy to retain copyright and other rights and simply want to grant other people a license to use you work then just use MIT.

Re:The Unlicense is an inferior license wrapped in an atroci... by mokus on Friday March 04, 2022 @11:48AM (#30557148)
I hear this a lot, but what jurisdictions and why? On the face of it, it seems batshit insane to me that there would be a place where I can’t waive my property rights on something.
Re:The Unlicense is an inferior license wrapped in an atroci... by agency on Friday March 04, 2022 @12:27PM (#30557634)
Germany, for one: (PDF warning) https://rd-alliance.org/sites/default/files/cc0-analysis-kre...

> With regard to the transferability and the waiving of the copyright the German copyright law can be considered as one of the strictest systems in the world. Main reason is the strict monistic approach the German copyright law bases on. Key feature of this approach is the concept that, in principle, the copyright/author’s right itself can neither be transferred to another person nor waived by the author herself. The German author’s right consists of two parts, the moral rights and the exploitation rights. The moral rights are – as a rule – personal rights that are bound to the person of the creator (or, after her death, her legal heirs), i.e. they can neither be transferred nor waived. Since moral and exploitation rights are considered as inseparable parts of the author’s right as a whole (monistic approach) the exploitation rights cannot – in principle – transferred or waived by contract as well. However it is naturally possible to license the use of the work i.e. to transfer rights to use a protected work even on a large scale. Such licenses can practically lead (nearly) to the same result as an assignment or waiver of rights.

Re:The Unlicense is an inferior license wrapped in an atroci... by wongarsu on Friday March 04, 2022 @12:27PM (#30557639)
Germany would be one example. Public Domain exists, but only as the state something enters after copyright expired naturally 70 years after the death of the author. You can't release things into public domain.

As for why: nobody considered that case when writing our copyright laws, and nobody bothered to change it. Copyright as designed can't be transferred (except through inheritance), to avoid exploitation of the original creator. As a consequence you can't really get rid of it, you can only grant licenses.

It's hardly the only right you can't get rid of, and CC0 tries to deal with some of them, like the right to one's one image which in the shortest possible form says that you can't create or publish a picture of a person without their consent (but as you can imagine is way more complicated than that). You could say that the German legal framework isn't about maximizing freedom, it's about maximizing happiness, and sometimes being able to give away a right or freedom will on balance cause more harm than good.

Re:The Unlicense is an inferior license wrapped in an atroci... by rectang on Friday March 04, 2022 @12:49PM (#30557943)
> Public domain. Concise. Effective. Choose any two.

A workaround to the "concise" problem would be a commonly understood convention for indicating that a file is CC0 with a single line comment. The officially recommended boilerplate for CC0 is painfully cumbersome:

https://wiki.creativecommons.org/wiki/CC0_FAQ#May_I_apply_CC...

Something like this:

  // Available under http://creativecommons.org/publicdomain/zero/1.0
Come to think of it, it sure would be nice if "Available under [URL]" came to be a convention for FOSS licensing in general. I'm choosing "available" rather than "licensed" because it seems as though it would be generalizable to both copyright licenses and public domain dedications. (Caveat: though I'm fairly familiar with FOSS licensing for a layperson, I'm not a lawyer and so this would need to be reviewed by a lawyer to ensure for drafting soundness.)
Re:The Unlicense is an inferior license wrapped in an atroci... by ksec on Saturday March 05, 2022 @12:57AM (#30564737)
>isn’t a thing in many jurisdictions

I try to look this up and there isn't a concrete answer. There are countries with no or unclear Copyright terms, but I cant find countries with no public domain.

Re:The Unlicense is an inferior license wrapped in an atroci... by iudqnolq on Saturday March 05, 2022 @01:59AM (#30565082)
One example is in Germany you can't give up all your rights (the sticky rights are often called "moral rights"). In that case you want to fallback to a permissive license.
Re:The Unlicense is an inferior license wrapped in an atroci... by rwmj on Friday March 04, 2022 @11:00AM (#30556524)
Trouble is no such sentence exists.

There are countries (eg. France) where moral rights are inalienable.

There are countries where you cannot put something into the public domain (Germany). Even countries where there isn't such a thing as the public domain.

You end up needing to write something which is clearly a license, yet acts like the work is in the public domain, and make it watertight (nearly) worldwide. So you end up with CC0.

Luckily you don't need to write anything very wordy to use CC0. It's actually pretty simple and short at your end. Creative Commons have already done the hard bit.

Re:The Unlicense is an inferior license wrapped in an atroci... by hsn915 on Friday March 04, 2022 @11:35AM (#30556971)
> no such sentence exists

What's wrong with 0BSD?

https://opensource.org/licenses/0BSD

"Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted."

Re:The Unlicense is an inferior license wrapped in an atroci... by rwmj on Friday March 04, 2022 @04:40PM (#30560976)
Well you missed out the second paragraph is the first problem.

Not being a lawyer I can only speculate on other problems. It doesn't get around the problem of moral rights, so probably doesn't work in France.

Re:The Unlicense is an inferior license wrapped in an atroci... by hsn915 on Friday March 04, 2022 @06:41PM (#30562122)
The second paragraph is so common that you can safely skim/skip it without loss.
Re:The Unlicense is an inferior license wrapped in an atroci... by hannob on Friday March 04, 2022 @10:01AM (#30555768)
Not OSI approved.
Re:The Unlicense is an inferior license wrapped in an atroci... by floatboth on Friday March 04, 2022 @09:11AM (#30554952)
Re:The Unlicense is an inferior license wrapped in an atroci... by thomascgalvin on Friday March 04, 2022 @09:35AM (#30555334)
Is `This work is public domain.` insufficient?
Re:The Unlicense is an inferior license wrapped in an atroci... by zinekeller on Friday March 04, 2022 @09:43AM (#30555463)
No, no, no, no. Nope. That's enough in US but never enough (like, legally impossible) in Europe or parts of Asia (that's why CC0 has a fallback permissive license).
Re:The Unlicense is an inferior license wrapped in an atroci... by ravenstine on Friday March 04, 2022 @09:48AM (#30555549)
I'm curious... if Creative Commons can't even create a public domain license that applies to both US and Europe, then what would it actually take to do so? Seems insane that any system can't accept "this is public domain" as all you need.
Re:The Unlicense is an inferior license wrapped in an atroci... by zinekeller on Friday March 04, 2022 @09:55AM (#30555661)
> Seems insane that any system can't accept "this is public domain" as all you need.

Except that's exactly (legally, anyways) sane in Europe (not EU, it predates EU). Read about moral rights, and you will learn the complexities of what the US squishes into a single copyright regime.

Note: moral rights was translated from French legal term droits moraux, there's no religious meaning in moral here.

Re:The Unlicense is an inferior license wrapped in an atroci... by hutzlibu on Friday March 04, 2022 @10:07AM (#30555839)
"Except that's exactly sane in Europe"

This is up to debate. I am a european resident and I think it is insane, that the reason I am not free to donate my work into the public domain is supposed to be "moral rights".

Re:The Unlicense is an inferior license wrapped in an atroci... by michaelmrose on Friday March 04, 2022 @02:59PM (#30559613)
It's not that anyone is denying you your right. You aren't "free" to donate your work to flutbark bargleboff either not because its forbidden but because its undefined.

Contract your lawmaker and have them define it legally. Its undefined because there isn't money to be gained by giving stuff away and for practical purposes current solutions seem to be work good enough for practical purposes for those who want to do so robs any such movement of much momentum thus far.

Re:The Unlicense is an inferior license wrapped in an atroci... by hutzlibu on Friday March 04, 2022 @05:36PM (#30561547)
"It's not that anyone is denying you your right"

Of course they are. I am not free do do with my IP as I want. (gifting it to everyone). I have to keep ownership. (even though I reject the concept of IP alltogether)

But you are right with your explanation why it is like this. There is no money in it to change it for good and current solutions work "good enough" for practical purposes (giving everyone the right to use my IP).

So I will likely also just go on use the existing solutions, instead of running against walls and trying to change the laws.

Re:The Unlicense is an inferior license wrapped in an atroci... by zinekeller on Friday March 04, 2022 @10:09AM (#30555866)
Fair, I should put "legally sane", I lost the nuance there.
Re:The Unlicense is an inferior license wrapped in an atroci... by Taywee on Friday March 04, 2022 @09:53AM (#30555627)
Some places, like Germany, don't recognize a public domain at all.
Re:The Unlicense is an inferior license wrapped in an atroci... by hutzlibu on Friday March 04, 2022 @10:08AM (#30555859)
In a way we do, called Gemeinfrei. But the only way to transfer something to it, is dying and waiting 70 years.
Re:The Unlicense is an inferior license wrapped in an atroci... by Brian_K_White on Friday March 04, 2022 @11:07AM (#30556608)
What is the status of work that no one knows where it came from?

A recipe for a cake is written on a paper and left on a bulletin board in town. It has no name and no one witnessed it being posted.

Everyone sees it and now knows how to make this cake.

The author may or may not be dead for 70 years.

Is it illegal to even document this cake recipe? You couldn't legally recount it in a news article or history text book without being able say who the author was and prove that they either granted a copy right or are known to be dead for 70 years?

Or worse, you are not only incentivised but essentially obligated to claim the authorship yourself just so you have someone to assign it to?

The thing undeniably exists regardless that the legal structure provides no place for it.

It's patently ridiculous. (guilty, terrible pun intended).

Re:The Unlicense is an inferior license wrapped in an atroci... by wongarsu on Friday March 04, 2022 @12:38PM (#30557778)
That's called an orphan work. You can apply §61 UrhG, which in this case would mean donating it to an archive, museum, library or university, who can then search for the author and after turning up empty are allowed to publish it. From there you can probably quote it, citing them as your source.
Re:The Unlicense is an inferior license wrapped in an atroci... by zinekeller on Friday March 04, 2022 @11:19AM (#30556754)
> A recipe for a cake

And there we come to the nuance of copyrights, at least in the US: you can't copy the text of the recipe, but the recipe itself don't have protection itself. Specifically, the text of the recipe is literature (which is protected), the recipe itself are instructions (which is not protected). This is the whole justification into clean-room design and reverse-engineering in software.

Also psuedonymous or even anonymous publications do have copyright (insert a legalheap of asterisks here). This actually sadly results into something called "orphan works", where they don't knew (or if they knew cannot find the next-of-kin/successor company/maybe even the government where the company was incorporated) where they can ask for permission.

Re:The Unlicense is an inferior license wrapped in an atroci... by marcosdumay on Friday March 04, 2022 @10:42AM (#30556284)
Well, I imagine they recognize a license saying "you can do anything with this". It probably just has different legal status than public domain.
Re:The Unlicense is an inferior license wrapped in an atroci... by davidjytang on Saturday March 05, 2022 @12:00PM (#30569235)
I only imagine something like "but you give up the right to sue me if any harm comes from whatever you do with this" would need to be appended to "you can do anything with this".
Re:The Unlicense is an inferior license wrapped in an atroci... by germanier on Friday March 04, 2022 @11:18AM (#30556746)
No. There are certain rights to a work you cannot waive, no matter how much you want to. Even less without actually specifying what "anything" entails.
Re:The Unlicense is an inferior license wrapped in an atroci... by 3np on Friday March 04, 2022 @08:10PM (#30562881)
While you can not waive certain rights, you absolutely can proclaim "you can do anything with this". You can choose to not exercise your legal right to attribution, for example. So what you’re saying is not in conflict with the person you’re replying to.

(You can argue that there’s some legal risk at hand here; for example, if someone writes a book with the above and you start selling copies of it claiming you wrote it, the author can still come back and demand that you credit them as author and have that right enforced in court)

I think this is great. Case in point: blanket EULA for an image sharing site can not remove your right to be attributed, should your photo end up in an ad campaign or a newspaper. This means that many European newspapers actually make sure to not misattribute photographs, which has the side-effect of improving transparency in news reporting. So grabbing a photo online and wrongfully claiming it’s from the wrong time, place and source is not something that tends to happen in practice. And if it does, there’s a clear path to recourse that doesn’t require "lawyering up", you just file a claim with evidence.

Re:The Unlicense is an inferior license wrapped in an atroci... by Jach on Friday March 04, 2022 @01:56PM (#30558837)
Nevertheless I suspect sqlite is used in Europe or parts of Asia without trouble.
Re:The Unlicense is an inferior license wrapped in an atroci... by zinekeller on Friday March 04, 2022 @08:57PM (#30563281)
1) Hipp, Wyrick & Company, Inc. (Hwaci, the legal owner of the code) does not actively enforce its rights available. This does not mean it will not affect operations in certain countries, while computer code is not (yet) affected, music definitely is (see GEMA in Germany). Additionally, in an adverse purchase of a company Hwaci could be bought by a scrupulous corporation (à la patent trolls of today) and enforce the copyright in countries where Hwaci has residual rights. If somehow that did not happen but Hwaci faces bankruptcy and wound up in favour to the State of North Carolina (the default option), we will have a similar problem as a particular Canadian company that unfortunately currently escapes my mind. This is what worries large companies: a permissive license which is recognised internationally cannot be annulled (unless they breached the very simple requirement), sure for new users it would suck (even GPL doesn't close the hole), but the new company cannot sue companies with existing licences because they have a very permissive license.

2) Actually, SQLite has this: https://www.sqlite.org/purchase/license

Re:The Unlicense is an inferior license wrapped in an atroci... by Jach on Saturday March 05, 2022 @09:22AM (#30567817)
I've long been aware of their $6k warranty of title. Only someone from Hwaci could give an accurate count of purchasers (they only say "Most people use SQLite without any kind of license or support"), but I would bet that not even half of the developer-users and distributors of sqlite directly (let alone those of sqlite indirectly through other products or libraries that bring it in or embed it, which they are under no obligation to disclose) in countries like Germany have actually purchased one. I doubt it's even a significant money-maker for them given their range of available things for purchase (https://www.sqlite.org/prosupport.html). It's not a problem in practice, it's exceedingly unlikely to ever become a problem, but sure, a lawyer can find a vulnerability in everything, even with GPL (which is part of why some US companies have a blanket "no GPL" policy).

I'm glad they offer the warranty of title and take money from companies with edgy lawyers, though. $6k is small as legal fees go. It's in general a lazy monetization strategy I broadly agree with and I've been hoping GitHub under MS's stewardship would help spearhead a simple way for people/companies to buy secondary-licensed copies of software without having to contact the author about it. (I think I got the idea from Zed Shaw around the time MS bought GH.) Like, a lot of software out there isn't a mess of contributors like the linux kernel each holding their own copyright, and thus much of it can be relicensed or dual-licensed without fuss. When people license something under the AGPL or even public domain if they're copying sqlite, sometimes they include something in the readme about being open to selling an alternatively licensed version/warranty of title to companies who have some issue. But even if they don't explicitly mention it, companies can still fruitfully contact such authors and make a deal. This happens all the time on twitter of all places, with journalists asking some user (who may not even be legally identifiable from just their handle) to re-use their apparently original photo or video. Sometimes the user just gives permission, sometimes they demand "pay me", sometimes a payment is actually made. Douglas Crockford has given permission (not sure if he got any money out of it) at least to IBM to use his software for evil, again showing his infamous clause is only a problem for people who decide to make it one.

Basically, I'd rather not tell people how they can license (or not license, as per public domain declarations) their code, and while it's fine to be aware of usability tradeoffs and it's fine to know that some edgy companies or users in other countries might write you off for your choice, it's important not to overstate the actual risks involved relative to the base rate risks already out there (like patent trolls) and it's important to recognize that solving the problems in ways even the edgiest of lawyers can be mostly happy with is often possible. Having blanket policies instead of pursuing those solutions is also a choice people are free to make.

(Writing this comment led me to https://web.archive.org/web/20120510151444/http://methodlogi... which is interesting in that it could suggest how further knowledge of tradeoffs and future pushback in the beginning may have led sqlite to be put under a license, however I don't suppose anything legally stops the authors agreeing to relicense in a new version since they retain a clean title, it's just there's no compelling practical reason like seeking more contributors.)

Re:The Unlicense is an inferior license wrapped in an atroci... by jimmaswell on Friday March 04, 2022 @11:02AM (#30556546)
So FOSS contributions are impossible in Europe, or they just take some legal work?
Re:The Unlicense is an inferior license wrapped in an atroci... by 3np on Friday March 04, 2022 @11:19AM (#30556769)
Neither, really, it’s just that "public domain" is a US-specific legal term that doesn’t have equivalents in most countries.

For one example, in Sweden you can never fully sign away the right to have creative work attributed to your name (until 50/70 years after creation/creator death, depending on nature of the work) as a creator. You can make a pinky promise to not claim that right, but you can’t fully waive it so you could always have a change of heart and demand to be credited by name later. IIRC this came from a notion of protecting artists and photographers from predatory contracts from the print industry or something similar.

Commercial rights etc can all be fully transferred, of course.

Re:The Unlicense is an inferior license wrapped in an atroci... by Scarblac on Friday March 04, 2022 @11:13AM (#30556703)
FOSS contributions don't need something to be added to the public domain to be possible.
Re:The Unlicense is an inferior license wrapped in an atroci... by freemint on Friday March 04, 2022 @09:46AM (#30555516)
Yes. At least if you want people who have to talk to lawyers to use the code. Lawyers don't like that. For some anecdotes see this talk https://youtube.com/watch?v=MkJkyMuBm3g (worth the hour, althoug Rob Landley write the same thing on his website too but to lazy to Google that.
Re:The Unlicense is an inferior license wrapped in an atroci... by ketzu on Friday March 04, 2022 @09:41AM (#30555434)
Yes, because in some jurisdictions it is not possible to discard your rights.
Re:The Unlicense is an inferior license wrapped in an atroci... by pjfin123 on Friday March 04, 2022 @01:33PM (#30558549)
Not ideal but I've used dual licensing under MIT and CCO.
Re:The Unlicense is an inferior license wrapped in an atroci... by netr0ute on Friday March 04, 2022 @09:08AM (#30554906)
What about LGPL? It seems to tick all of the 4 boxes you have.
Re:The Unlicense is an inferior license wrapped in an atroci... by zokier on Friday March 04, 2022 @09:09AM (#30554920)
LGPL is not public domain alike
Re:The Unlicense is an inferior license wrapped in an atroci... by michaelmrose on Friday March 04, 2022 @03:01PM (#30559633)
It's undesired by people who want to exploit other people's work commercially or fantasize that they somehow they might want to do so in the future. Kind of like poor people who don't want to tax the rich because they fantasize that they may someday be rich.
Re:The Unlicense is an inferior license wrapped in an atroci... by ahelwer on Friday March 04, 2022 @09:21AM (#30555112)
Google et. al (and OSI for that matter) will find no such alike-license acceptable until a platform using that license becomes too valuable to ignore, like Linux with GPLv2. So the calculus has to tilt such that giving their work away for free is worth it because they get so, so much work for free. And even then they will try to work around it like with Fuschia.

Plus since everything is served over the internet these days unless a license includes AGPL-type clauses the alike requirement will not attach.

Re:The Unlicense is an inferior license wrapped in an atroci... by faho on Friday March 04, 2022 @09:40AM (#30555429)
The parent was asking for a license "akin to Public Domain", not a "share-alike" license.