News for hackers. Stuff that matters.
Re:Richard Stallman reveals he has cancer in the GNU 40 Hack... by rakoo on Friday September 29, 2023 @04:01AM (#37700647)
The FSF has created the AGPL 16 years ago (https://en.wikipedia.org/wiki/GNU_Affero_General_Public_Lice...), so it's not like they didn't see the turn that software was going into. But it was already a losing battle, because every developer wants to think they might become millionaire and won't use it.

Whether the software runs on my computer or not, if I am the user, I must be in control.

Whether the meal is prepared in my kitchen or not, if I am going to eat it, I must be in control.

Re:Richard Stallman reveals he has cancer in the GNU 40 Hack... by loxdalen on Friday September 29, 2023 @04:13AM (#37700734)
OT, but how are you in control if you buy food that you haven't produced yourself?
Re:Richard Stallman reveals he has cancer in the GNU 40 Hack... by rakoo on Friday September 29, 2023 @05:23AM (#37701224)
Just like you aren't in control of your software if you didn't write your compiler yourself, if you didn't build your compiler yourself, all the way down to the minerals.

You're never 100% in control, but that doesn't mean you should try and maximize it.

Re:Richard Stallman reveals he has cancer in the GNU 40 Hack... by layer8 on Friday September 29, 2023 @06:12AM (#37701544)
One difference with food is that you can switch your food supplier any time, it doesn't hold your data or account connections hostage.
Re:Richard Stallman reveals he has cancer in the GNU 40 Hack... by 0xDEF on Friday September 29, 2023 @04:04AM (#37700670)
AGPL is also the license you should use if you don't want big corporations to use your software. Big Tech even avoids GPL-3 and stick to GPL-2 from what I have noticed.
Re:Richard Stallman reveals he has cancer in the GNU 40 Hack... by hardwaresofton on Friday September 29, 2023 @04:13AM (#37700738)
Note that AGPL does not actually protect your software from big companies (or small companies) running your software as a service. It requires them to contribute back or make source available when they make changes, and IIRC thats to the user (who could be an enterprise customer under some other agreement even, but none of this is tested in court).

If you want that sort of protection, BSL, SSPL, Elastic license, etc are what you want.

If you want to make Free Software, make it. Know that people you don’t like may use your software, even criminals may. That is what Free Software is. OSS is slightly different but similar.

If you want to make shareware, make shareware — no judgements on people who want to make money with their software and believe thats the best path.

Re:Richard Stallman reveals he has cancer in the GNU 40 Hack... by rakoo on Friday September 29, 2023 @05:18AM (#37701193)
I'm fine with big corporations use my software: the deal is that whatever they do with it, they must give it back to the users with the same license. Make it live beyond the company's existence and control. It's still better than my software being non-copyleft and being used by a company.

I wish they would give back all the profit as well but that's another topic and the AGPL doesn't touch that.

Re:Richard Stallman reveals he has cancer in the GNU 40 Hack... by enriquto on Friday September 29, 2023 @06:50AM (#37701836)
> AGPL is also the license you should use if you don't want big corporations to use your software.

Don't know about "big corporations", but in academia most people use Overleaf to share the editing of LaTeX papers, and it's AGPL software. In my lab we collaborate with many industrial partners, and they see no problem using that software either. We bought a quite expensive lab-wide license for Overleaf so that we can use more resources of their online offering. I have a friend at google who also uses it (but it's just a single data point).

I honestly don't understand what you are talking about.