#0bsd — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #0bsd, aggregated by home.social.
-
@hexaheximal case in point:
#Copyleft doesn't work in terms of getting #contributions or actual improvements.One can not really force people to do intellectual labour nor get them to share it!
But don't take my word for it, because @landley has been there and done that as the fmr. maintainer of #BusyBox and nowadays maintains a competing project (#toybox) licensed under #0BSD...
---
TBH I'm not against the #GPL, not even #GPLv3 because when you want to commit #AssetDenial it does that fine and I use it for that...But sadly #FLOSS doesn't exist in a vacuum and as much as I wished #CCSS to never have existed in the first place, it sadly does and worse people often depend on that shite...
---
So I do aim to #DoBetter instead... -
Another reason why "#PublicDomain" is a problem but #0BSD isn't is because not every juristiction acknowledges or accepts Public Domain.
For example in #Germany, where the head maintainer resides. there is no such thing as "Public Domain" but only "Lapsed Copyrights*".
Otherwise it would be impossible to prosecute authors of obvious #hatespeech, cuz not every place agrees with the U.S. principle of what is essentially "#ConsequenceFreeSpeech", not "#FreeSpeech"...
Again:
We don't make the rules, we've to follow them whether we like them or not!https://www.youtube.com/watch?v=MkJkyMuBm3g&t=2107s video via @linuxfoundation feat. @landley
* which hasn't lapsed yet for #SteamboatWillie there because as per bilateral agreements, Copyrights don't lapse till 70 years past the death of the authors and that applies for U.S. works to - in return German Residents don't need to file for Copyright because that's inherently granted at creation and thus also applies in the USA!
-
Another reason why "#PublicDomain" is a problem but #0BSD isn't is because not every juristiction acknowledges or accepts Public Domain.
For example in #Germany, where the head maintainer resides. there is no such thing as "Public Domain" but only "Lapsed Copyrights*".
Otherwise it would be impossible to prosecute authors of obvious #hatespeech, cuz not every place agrees with the U.S. principle of what is essentially "#ConsequenceFreeSpeech", not "#FreeSpeech"...
Again:
We don't make the rules, we've to follow them whether we like them or not!https://www.youtube.com/watch?v=MkJkyMuBm3g&t=2107s video via @linuxfoundation feat. @landley
* which hasn't lapsed yet for #SteamboatWillie there because as per bilateral agreements, Copyrights don't lapse till 70 years past the death of the authors and that applies for U.S. works to - in return German Residents don't need to file for Copyright because that's inherently granted at creation and thus also applies in the USA!
-
Another reason why "#PublicDomain" is a problem but #0BSD isn't is because not every juristiction acknowledges or accepts Public Domain.
For example in #Germany, where the head maintainer resides. there is no such thing as "Public Domain" but only "Lapsed Copyrights*".
Otherwise it would be impossible to prosecute authors of obvious #hatespeech, cuz not every place agrees with the U.S. principle of what is essentially "#ConsequenceFreeSpeech", not "#FreeSpeech"...
Again:
We don't make the rules, we've to follow them whether we like them or not!https://www.youtube.com/watch?v=MkJkyMuBm3g&t=2107s video via @linuxfoundation feat. @landley
* which hasn't lapsed yet for #SteamboatWillie there because as per bilateral agreements, Copyrights don't lapse till 70 years past the death of the authors and that applies for U.S. works to - in return German Residents don't need to file for Copyright because that's inherently granted at creation and thus also applies in the USA!
-
Another reason why "#PublicDomain" is a problem but #0BSD isn't is because not every juristiction acknowledges or accepts Public Domain.
For example in #Germany, where the head maintainer resides. there is no such thing as "Public Domain" but only "Lapsed Copyrights*".
Otherwise it would be impossible to prosecute authors of obvious #hatespeech, cuz not every place agrees with the U.S. principle of what is essentially "#ConsequenceFreeSpeech", not "#FreeSpeech"...
Again:
We don't make the rules, we've to follow them whether we like them or not!https://www.youtube.com/watch?v=MkJkyMuBm3g&t=2107s video via @linuxfoundation feat. @landley
* which hasn't lapsed yet for #SteamboatWillie there because as per bilateral agreements, Copyrights don't lapse till 70 years past the death of the authors and that applies for U.S. works to - in return German Residents don't need to file for Copyright because that's inherently granted at creation and thus also applies in the USA!
-
Someone asked "Why don't you use BusyBox?
Let me answer this simply...
1. #BusyBox's #Licensing page kinda makes them look #toxic...
https://busybox.net/license.htmlAnd @landley went into great detail on why the whole "enforcement" backfired very hard:
https://www.youtube.com/watch?v=MkJkyMuBm3g&t=301s2. #toybox on the other hand is very much a drop-in replacement and it's #0BSD licensed, so much less headaches...
http://landley.net/toybox/license.htmlSo it was chosen for OS/1337:
https://github.com/OS-1337/OS1337/blob/main/LICENSE.md3. We use unmodified source code as of today and thus can just link to the original sources and attribute them properly:
https://github.com/OS-1337/OS1337/blob/main/docu/LICENSES.md#NotLegalAdvice but AFAICS this is sufficient for compliance.
I
-
@landley The sad part is that you are in fact correct.
The only thing #Copyleft like #GPLv3, #AGPLv3 and espechally #AssholeLicensing of the #SSPL, #RHEL and #grsecurity kind can do is commit #AssetDenial and even that is flaky as one can only put actual #code under a license and not an implementation of something like a #Codec...
...But those are usually covered by #patents and other legalese trolling efforts, like the way #MELP / #MELPe is licensed so everyone who doesn't want to exclusively make a radio for NATO / U.S. DoD has to arrange a licensing deal woth half a dozen tech giants, so #Codec2 had to be made...
https://en.wikipedia.org/wiki/Mixed-excitation_linear_prediction
https://en.wikipedia.org/wiki/Codec_2As of now I am considering to relicense my content under #0BSD and sinve very few of my projects have any external contributions, this should be trivial to do so.
-
@geraldew @RTP @linux @torvalds
Being a "universal donor license" would be a reason.
But don't take my word for it, ask @landley on why he left #BusyBox and started #toybox under #0BSD.
TLDW: #Copyleft backfired and made BusyBox notoriously hostile to vendors as well as kinda hurt everyone.
https://www.youtube.com/watch?v=MkJkyMuBm3g&t=25m27sThe reason why no "applianced" Console runs #Linux is the #GPL, because #PlayStation since the #PS2 and #Nintendo since the #WiiU run #FreeBSD as #Copyleft would be incompatible with their #DRM and subsequent #NDA's as well as contractual secrecy per their vendors & subcontractors...
#Valve and the #SteamDeck aren't compareable to i.e. the #NintendoSwitch because they see it as a tool to increase revenue per #Steam User, not as a means to increase their market share from de-facto to de-jure #monopoly whilst facing stiff competition like #XboxGamePass on the #PC and #Chromebooks as well as #ChromeOS flex running #Android #Games!
-
Open source licences are one of those cans of worms I mostly try to avoid. Except it really annoys me when I want to borrow some code and I can't work out what the licence is.
If you're writing sample code or something small, you should include a #licence. However which to use? One of the *BSD or MIT licences is usually a good choice (but be careful which version!), they place minimal requirements on you. However the requirement to include a copyright notice is just annoying for everyone involved (when the code is small). Android Toybox (https://en.wikipedia.org/wiki/Toybox) solved this with the Zero-clause BSD licence (aka #0BSD); it is a modification of the ISC license, not a BSD one, but the name doesn't matter really.
My attempt to make this easier to use is now available at http://©.st (think copyright street? © can be obtained with Option+G on a Mac, Ctrl+Atl+C on Windows, Compose o c on X11 or use the emoji selector). It's really just a way to make it easier to apply 0BSD, as it gives you some very short copy pastable comment lines. Consider 0BSD next time you write some small piece of code.
Also you can use it to test your #IDN support.
While 0BSD may not be perfect, I believe it (or MIT-0, which is nearly identical) achieves the best balance of all the "do what you want" licences. I'm mainly talking about "small" pieces of code here; for larger projects it's understandable the licence choice is more nuanced and you may want Apache, #GPL, etc. This is not legal advice. Talk to a lawyer if in doubt.
-
Open source licences are one of those cans of worms I mostly try to avoid. Except it really annoys me when I want to borrow some code and I can't work out what the licence is.
If you're writing sample code or something small, you should include a #licence. However which to use? One of the *BSD or MIT licences is usually a good choice (but be careful which version!), they place minimal requirements on you. However the requirement to include a copyright notice is just annoying for everyone involved (when the code is small). Android Toybox (https://en.wikipedia.org/wiki/Toybox) solved this with the Zero-clause BSD licence (aka #0BSD); it is a modification of the ISC license, not a BSD one, but the name doesn't matter really.
My attempt to make this easier to use is now available at http://©.st (think copyright street? © can be obtained with Option+G on a Mac, Ctrl+Atl+C on Windows, Compose o c on X11 or use the emoji selector). It's really just a way to make it easier to apply 0BSD, as it gives you some very short copy pastable comment lines. Consider 0BSD next time you write some small piece of code.
Also you can use it to test your #IDN support.
While 0BSD may not be perfect, I believe it (or MIT-0, which is nearly identical) achieves the best balance of all the "do what you want" licences. I'm mainly talking about "small" pieces of code here; for larger projects it's understandable the licence choice is more nuanced and you may want Apache, #GPL, etc. This is not legal advice. Talk to a lawyer if in doubt.
-
Open source licences are one of those cans of worms I mostly try to avoid. Except it really annoys me when I want to borrow some code and I can't work out what the licence is.
If you're writing sample code or something small, you should include a #licence. However which to use? One of the *BSD or MIT licences is usually a good choice (but be careful which version!), they place minimal requirements on you. However the requirement to include a copyright notice is just annoying for everyone involved (when the code is small). Android Toybox (https://en.wikipedia.org/wiki/Toybox) solved this with the Zero-clause BSD licence (aka #0BSD); it is a modification of the ISC license, not a BSD one, but the name doesn't matter really.
My attempt to make this easier to use is now available at http://©.st (think copyright street? © can be obtained with Option+G on a Mac, Ctrl+Atl+C on Windows, Compose o c on X11 or use the emoji selector). It's really just a way to make it easier to apply 0BSD, as it gives you some very short copy pastable comment lines. Consider 0BSD next time you write some small piece of code.
Also you can use it to test your #IDN support.
While 0BSD may not be perfect, I believe it (or MIT-0, which is nearly identical) achieves the best balance of all the "do what you want" licences. I'm mainly talking about "small" pieces of code here; for larger projects it's understandable the licence choice is more nuanced and you may want Apache, #GPL, etc. This is not legal advice. Talk to a lawyer if in doubt.