Post AwCmRCBCeMn42xkdG4 by jbqueru@floss.social
 (DIR) More posts by jbqueru@floss.social
 (DIR) Post #AwCmR47Mckxx2jtSAC by jbqueru@floss.social
       2025-06-20T14:27:36Z
       
       0 likes, 1 repeats
       
       It's common to say that the "free" in #FreeSoftware is closer to "free as in speech" than to "free as in beer," and that is true.However, "free as in speech" only resonates so far with me. To me, Free Software is even closer to free will than to free speech, in the sense that, with Free Software, I have control over my actions in how they relate to that software, i.e. how I have control to decide how to modify it, how to use it, whether to maintain it, whether to deploy it or distribute it.
       
 (DIR) Post #AwCmRCBCeMn42xkdG4 by jbqueru@floss.social
       2025-06-20T14:34:11Z
       
       0 likes, 0 repeats
       
       A situation that appears more and more, though, is that "with great power comes great responsibility." When using Free Software, you might only have yourself to rely on to maintain the software you use.Don't get me wrong, most maintainers will go through great lengths to help their users, but that's from being kind and decent human beings, not from being contractually required to.When using Free Software, it's also "free as in puppy": no upfront cost, but maintainance is on you.
       
 (DIR) Post #AwCmRKDclFTqymwg8u by jbqueru@floss.social
       2025-06-20T14:37:42Z
       
       0 likes, 0 repeats
       
       In my little world of #RetroComputing, I have stumbled across minor issues in some of the tools that I use.I've had two cases so far where maintainers very quickly took my suggestion and made it available in their main branch. I've also had one where I haven't heard back from the maintainer, i.e. where I'm going to need to maintain my own fork (for #RiscV compatibility). And that's OK. Beyond being glad that I got help, I'm glad that the original authors allow me also to do the work myself.