@jacob yes, and #OpenWashing is a real issue not just with #AssholeLicensing as seen with #Redis & others using #SSPL as a literal #AssholeLicense which are just "#SourceAvailable" instead of #OpenSource, but actual #donations.and #contributions.
#AssholeLicensing
@kotaro gramted, all of tuhe #Forks that are #BSD-licensed had way more #effort put into them.
- I just think that #AssholeLicensing is as bad as #Tivolization in terms of #OpenSource and #useability.
#SSPL is still worse than #AGPLv3, but #AGPL & #GPLv3 are just completely disregarding the legal reality of #IP and #Licensing.
- If they don't want to accept #competition, they could've chosen @creativecommons #CCBYNCSA instead, but they did not!
Needless to say if I were a #developer of it and had contributed under #BSD license I'd expect to either get my code removed entirely or the license to be kept the same.
- And now you know why I'll refuse to sign any "#ContributorLicenseAgreement" (#CLA) UNLESS I get a paid, non - term-limited position as an enployee in return…
@Nicholasr_ITSulu @nixCraft nodds in agreement and since there are so many stakeholders with opposing interests and a #copyleft license, #GAFAMs can't #enshittify or #tivolize it!
- And due to #GPLv2only eben a move to #AssholeLicensing like #AGPLv3 or #SSPL is not possible!
@xerxespersrex nodds in agreement...
- Shit like #SSPL & #RSAL is IMHO even worse than #SourceAvailable as it's literally "#AssholeLicensing"...
At least most source available products like #Tarsnap are honest that they are not #OpenSource!
@anderseknert Everyone who uses #AssholeLicensing like #SSPL or tries to infringe upon users' #FLOSS #Rights like #grsecurity & #RedHad do should be banned from any professional developments and supply chains as part of the #RiskAssessment and #RiskAvoidance in #DueDiligence.
- Anything else in criminal neglect at this point...
One can really see this is an older video, as it misses not only #0BSD between #PublicDomain and #MIT but also #SSPL right of #AGPLv3 in a tab that's right of it called "#AssetDenial" or "#Monopolistic" or just "#AssholeLicensing" and a tab right of that for "#SourceAvailable" licensing, but I get ahead of myself...
#Sarcasm #OpenSource #Licensing #Copyleft #Cipyright #Copywrong #rant #vent #venting
@carlwgeorge @vermaden @samurro @tara @vkc @BrodieOnLinux TBH, being just marginally better than #Oracle and #Microsoft is the only reason I'd use #RHEL over #Solaris or god forbid #Windows, tho I'm glad #Linux isn't controlled entirely by #RedHat and that I can use #OpenSUSE and #UbuntuLTS and their parent companies didn't gave me or my (fmr.) clients/employers the finger...
But hey, go keep lying to yourself with the corporate propaganda of open source sustainability because if you think that #FLOSS needs to be #profitable you haven't understood why people choose #Copyleft licenses like the #GPLv2 and espechally #GPLv3 and how Red Hat is providing arguments to push for "#AssholeLicensing" a la #AGPLv3.
Your dismissals of criticism are childish and your way to flood my notifications with bs replies just to then flee the discussion like a coward is a really bad way to pull rank.
- This behaviour reminds me of "channers" that refexively reply "You have an anime pfp, your opinion doesn't matter!" as if that's a way to engage with potential clients!
Just because I'm not a CxO doesn't mean I know how to (dis-)recommend suppliers and underpin that with past experiences, as clients/employers trust in my judgement.
@marcan @fuchsiii Either way, like @landley I did the #copyleft experiment and those projects didn't see even remotely as much resonance or contribution as when I embraced #0BSD as a #PermissiveLicense (cuz #PublicDomain legally doesn't exist in #Germany: One cannot renounce #Authorship for legal reasons, otherwise #HateSpeech would be unprosecute-able, so only #Copyright lapses 70 years post-mortem of the Authors)...
- I think "#AssholeLicensing" like #SSPL is inherently unfree and #AGPLv3 is just an act of committing #AssetDenial which doesn't work.
TBH, the only way to preven #GAFAMs like Amazon from leeching #FLOSS is to either make #CCSS or offer the superior [#SaaS] solution by ticking boxes #aws can't ( i.e. due to #CloudAct, like #GDPR compliance) or inherently won't hecause it's antithetical to their business ( i.e. [airgapped] #SelfHosting & Support/Management Options for self-hosted systems)...
- #healthcare-IT based startups in the #EU pay Companies like #Telekom to host their medical data because unlike #Amazon they can and will evidently enshure their U.S. division can't leak that data to U.S. govt. agencies and if one butters them with enough money, they'll likely sign the hardest NDAs one can throw at them...
@ohanamatsumae ain't #MongoDB those #SaaS-only guys that basically use #AssholeLicensing as per #SSPL?
https://en.wikipedia.org/wiki/MongoDB
https://en.wikipedia.org/wiki/Server_Side_Public_License#Licensed_software
To me that disqualifies them for any serious useage!
@Elucidating that's still #AssholeLicensing.
Compared to @ubuntu which when I asked them via eMail [years ago] about #preinstalling #UbuntuLTS went like:
'Shure you can do that and sell the systems and provide commercial support as an MSP. Just make shure you don't claim to be affiliated or endorsed by us and follow our trademark guidelines.'
And I'm shure if I were in the business of offering managed #Zulip Servers for customers, I'm shure @zulip wouldn't mind that as long as either stick to the #FLOSS'd version or appropriately license that for customers and not claim to be endorsed or affiliated with Zulip....
@Elucidating the fact that you use the words steal ad starve unsarcastically speaks volumes in regards of how little you seem to understand what #OpenSource is and what the idea behind is.
Sorry to break it to you, but maybe then #FLOSS isn't what you want tho, because that "risk" is inherently part of #FOSS / #OSS...
You can try to beat #GAFAMs into working with you, or you can incentivize contributions...
OFC for-profit companies will always churn the numbers and choose what's cheapest for them...
What gets my blood boiling here is that #Redis, #MongoDB & #Elastic chose to switch to #AssholeLicensing as a form of #CollectivePunishment because they failed to attract #donations, #contributions and / or #customers, which means either their #products & #services were bad or they didn't bring anything to the table worth spending money for.
Again: You can't force people and companies to actually invest personnel hours and/or money into it - either you attract contributors or not.
@Yuki I sincerely hope everyone's gonna fork #Redis before they changed to #AssholeLicensing with the #SSPL which is a #NonFree #AssholeLicense.
This is worse than #Copyleft but just blatant Asset Denial because *"We WaNt AmAzOn To PaY uS!" kinda bs...
If you want to make money with #FLOSS, provide some good product and make it attractive to #donate and/or #buy some support.
As a matter of fact, @landley did try to crowbar #GPLv2 [or rather started it]¹ with #BusyBox and that failed miserably, because now everyone knows BusyBox as the litigatious² folks that one should just not use code from.
There's a reason I chose #0BSD ³ for @OS1337 and it's because I most of the work I do is build and repackage #toybox + #musl / #Linux and I want people to use it as a friendly licensed foundation for their #IoT and #embedded projects down the line.
And that means that I'll also accept contributions on the same license and not expect devs to sign away code under worse terms so I can turn it into #UnfreeSoftware the way Redis and others did...
¹ https://www.youtube.com/watch?v=MkJkyMuBm3g&t=1607s
² https://www.busybox.net/license.html
³ https://en.wikipedia.org/wiki/BSD_licenses#0-clause_license_(%22BSD_Zero_Clause_License%22)
⁴ https://github.com/OS-1337/OS1337/blob/main/LICENSE.md
@msw Basically they tool a #FLOSS and changed the license to #AssholeLicensing!
Shit like this is why I'll never sign-away my right to my code and demand it to be released under the same terms the project was when I committed to it in perpetuality unless they were to yeet my code - which everyone can, git allows for selectively undoing code committed by a certain user...
@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_2
As 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.
@landley yeah...
Worse is only #AssholeLicensing like #AGPLv3 or #SSPL at which point one might just choose some #commercial #SourceAvailable solution (like #Tarsnap is) instead...
#GPLv3 is mostly #Stallmanism and a complete disregard to practicality and the fact that #CCSS exists!
I'd not be surprised if #GPLv4 extends #Copyleft upon all forms of output and input as well as sentencing violators to sponsor/contribute to #GnuHurd as an "indulgence trade"...
One may want to use a permissive license like #BSD or #APL because using i.e. #GPLv3 doesn't work for them or their project...
And stuff like #SSPL is basically "#AssholeLicensing" which I think is legally even more questionable than #AGPLv3.
#NotLegalAdvice OFC...
@mxmehl @element @webmink @matrix so basically they do go with an "#AssholeLicensing" model and I dovexpect them to further worsen from #AGPLv3 to #SSPL just as a means to give everyone a #MiddleFinger who may want to offer commercial #hosting - even if it's done under terms #Element can't comply with if they even wanted to.
And I doubt that they'll not go with an #OpenCore solution like #Mattermost does.
So I'm glad I stuck with #IRC, #XMPP & #Zulip instead since those are #FLOSS...
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst