Thread 105678185

What's the actual best open source license? I usually don't care but people like to be primates about this, so I feel like I need to know.

AGPL

If you have to ask, just paste GPL3 and call it a day. It will protect you and your software from anything that could go wrong. Any other answer is retarded.
Just don't not give it a license, because then people can sue you if they're retarded and break their system with your software.

>>105678185 (OP)
Any +NIGGER license: https://plusnigger.org/

>>105678185 (OP)
MIT or Unlicense if you're into true freedom. (A|L)GPL if you're into cucked """freedom""" or if you're a commie permanently seething about corpos.

GPL with copyleft
or as some anon said N-word plus (no I won't say the hard r word, I'm not racist)

>>105678250
Only one and a half chuds got enough balls to use this for personal projects and 0 under real name.

>>105678250
/thread

Public domain. Licenses are cancer. LOL at all the desperate fags ITT trying to convert you to MIAnigger communism

>>105678185 (OP)
MIT with or without the +NIGGER
licenses just let you use discounted/free lawyers from the foundation supporting it to rape the offender
so you can imagine how well this will go if a russian or chinaman decides they want to use your shit

>>105678185 (OP)
creative commons

>>105678185 (OP)
GPLv2 for applications
LGPL for toolkits
Cuck licenses are irrelevant

>>105678187
this
as more and more software becomes subscripton based software-as-a-service (saas) running in the cloud (i.e. in someone else's PC, not yours) you want to ensure that if they use (a part of) your software they still have to provide the source. with normal GPL that is not the case.

>>105678187
Also this

>>105678185 (OP)
Corpos will use your code as if it is MIT and they call it a day afterwards. It literally doesn't matter unless you police the fuck out of everyone.

>>105678185 (OP)
MIT and BSD are the two main licenses, there's also Apache 2.0. If you want a copyleft license (like you want to force the people who use your code to release their code as open source) then you can look at the GPL and its variations.

>>105678185 (OP)
The only choices for the non-cuck are free copyleft licenses (GPL, AGPL, LGPL) and proprietary anti-freedom.
Anything else is for corporate dick sucking cuckholdry.

>>105678187
>enter thread
>FPBP
you love to see it

>>105678452
i don't think "public domain" is something you can legally place things under in some places. there are practical equivalents though, such as WTFPL, which is literally "do whatever the fuck you want public license", whose sole stipulation demands you do whatever the fuck you want

>>105678452
>Public domain
Have fun with people stealing your work, license it and then sueing you over your own work. You retards only learn the hard way.

gpl et. al. and bsd/mit et. al. is a curious issue
on paper bsd/mit is of course more free, but the obvious issue is that it may not remain free.
so is enforcing freedom freedom? seems like a paradox

>>105679454
that is why you should keep the copyright and only give a "do what you want" license. you retain ownership for legal purposes and only license it out for any use
you may not care about the law now, but they can not care about you harder. guaranteed.