The FSF considers large language models

On the interaction between free-software licensing and large language models.

The FSF considers large language models

The Free Software Foundation's Licensing and Compliance Lab concerns itself with many aspects o [...]

LWN.net
Con la nueva era de la AI (Bullshit Generators) todos los q promovian las licencias permisivas no entendieron la puta vibra (si te veo a ti #OpenSource fundation), si los proyectos estan con #GPL no podrían ser usado el código para alimentar la AI sin violar la licencia, al tener q distribuir todo codigo derivado sobre la misma licencia, igual creo es necesario una #GPLv4 para protección contra empresas #AI que hacen millones, impacto ambiental a costa del código de otros sin dar nada a cambio

@katyswain I din't think that #CCSS is good either, but the demands of #GPLv3 are not compatible with the (adnitteldy shitty) reality of how #IP, #Licensing and #Patents work and thus it kneecaps a lot of things.

I chose #0BSD for _OS/1337 because as with any "intellectual labour", one cannot force others to collaborate and I'd rather have people join in out of the goodness of their hearts instead of just dumping some random git commit that is useless.

#OS1337

Upgrade to #GPLv4?

Nothing wrong with #GPLv3, but I feel it does need to be updated to specifically make it unlawful to put the code on any repository owned or operated by an entity that is engaging in software theft (eg. Micros(ha)ft servers). That means no code on git-hub(dot) com.... includes forks and mirrors obviously.

Microsoft supports #softwareTheft via their so-called "ai".

(NOTE: The new license wouldn't need to add anything about "AI" because the existing license is clear, but it probably should explicitly name micros(ha)ft as barred for the sake of clarity.)

@rms @fsf @jeffcliff @silverpill @r

@landley @lispi314 @libreleah at least with #FLOSS, people can't pull code from circulation and prevent others from forking and improving upon it, even it seems to be horrible code with nonexistant documentation

  • Unlike with #CCSS like #SCORE (which suffers from being pulled off shelves) and neither the former maintainer nor his heirs giving a damn about it.

Personally, I wished #copyright would be void and nullified once it's not offered for licensing anymore under #FRAND terms, because #ArtificalScarcity benefits neither consumers nor creators and only rewards #scalpers and other #ValueRemoving #RentSeekers.

  • As can be seen with those #NFT shitshows…

I hope #GPLv4 will ban #paywalling access to code (like #grsecurity and #RedHat did) assuming the writers don't double-down on ideologically motivated terms as per #GPLv3.

  • I guess that's even more wishful thinking…
Maintaining the Unmaintainable: Picking up the Baton of a Secure Kernel Patchset

YouTube

@Elucidating It works in both ways, but either way:

You cannot actually force people to contribute to any #FLOSS project...

I'm shure some folks like RMS would love to make #GPLv4 that penalizes violations with #ForcedLabour on #GNU / #Hurd or some other * " #Abandonware " * but that completely ignores that one can't really force people to do mental labour...

OFC I think freeloading is antisocial - espechally by the #GAFAMs - but then again it's kinda more antisocial if one does a #rugpull with worse #licensing terms...

And yes, I'd never contribute to anything that does require me to sign a " #ContributorAgreement " aka. away my #copyright because then I basically donated to a #Corporation with no strings attached and if I invest my time and effort without pay I'd at least expect the terms to stay the same...

@fsf #GPLv4 when? I don't want a repeat of the Red Hat situation.

@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"...

And yes, #Stallmanists and #RMS himself rambling ideological nonsense and shoehorning it into a license aka. #GPLv2 and espechally #GPLv3 killed #Copyleft and inspired Assholes to go with #SSPL aka. the "You can't make money off it, but worse!" license.

I mean what's next?
#AGPLv4 which demands #LicensingFees to #upstream projects in proportion to the sales price of the product [like #ARM wants nowadays] or #GPLv4 which demands #ForcedLabour on #GnuHurd for violations?

https://www.youtube.com/watch?v=SGmtP5Lg_t0&t=910s

Embedded Linux Conference 2013 - Toybox: Writing a New Command Line From Scratch

YouTube

Time for a #GPLv4 that guarantees source code availability, and cannot be locked behind a paywall or business agreement?

#RedHat
@fsf