Post #4165913

I figured it might actually be time to explain myself about this. I release most of my software CC0/Unlicense because I want my software to belong to the commons. The things I don't, I have a deliberate reason to do. The thing is... I don't make much stuff that a company would likely want to "steal." What company will want a beep program? Or an optimising brainfuck interpreter/compiler? Or a regex crate? Or an async wrapper around getaddrinfo()/getnameinfo()? What's the path to monetisation for them? lol I want my software to be useful for everyone. If a company uses it, it's not the company using it. It's a programmer who works at that company using it. If I made their day at the Capitalism shop a little easier, then I'm glad I could be of service. There are certain things I make GPL, like luminate will be GPL/LGPL because I want it to remain free and it is absolutely the kind of thing a company will take and never give back to. Even then, I do not see myself as "owning" luminate. It belongs to everyone. (I still need to release it on GitHub but I'm slacking and need to clean things up a bit more) Now the thing is. Someone might use my code in something I don't like. I have code in Linux for example. Someone is probably running that code on some drone or something being used to blow up people. That code I wrote has nothing to do with drones, of course (it's mostly just for phone tethering stuff), it's just a side effect. What can I realistically do about it? I'm not the one who put the code on a drone, and I didn't tell them to put Linux on them. That's not on me. I'm not responsible for that. Same thing with LLMs scraping it or whatever. They're gonna do what they're gonna do. I'd rather my stuff be useful to the commons than try to put on some limitation they won't obey anyway, a limitation that would make my software non-free and unable to be used in a lot of places I would actually like to see it be used.