3 ms·

>Nobody at the FSF cared about cloud or mobile Stallman back in 2010 about SaaS https://www.gnu.org/philosophy/who-does-that-server-really-serve.html https://

>Nobody at the FSF cared about cloud or mobile Stallman back in 2010 about SaaS https://www.gnu.org/philosophy/who-does-that-server-really-serve.html https://www.gnu.org/philosophy/who-does-that-server-really-s... Also, https://www.gnu.org/licenses/why-affero-gpl.html https://www.gnu.org/licenses/why-affero-gpl.html "We don't see any sensible way to address the SaaSS problem with license conditions on particular programs. Even to write a legal condition to distinguish between SaaSS use and non-SaaSS use would be a challenge, and if we had that, we don't see anything that the program's license might require in the SaaSS case that would correct the inherent wrong of SaaSS. Thus, our solution to the problem of SaaSS is simple: refuse to use services that are SaaSS."

shadowgovt 7y ago
Unfortunately, that's not a solution; that's throwing up one's hands and ignoring the issue with extra steps. Refusing to put pieces on the field means the other players can move without your input. They did, and now whether the OS on my machine is open is somewhat irrelevant because the things that provide services I care about won't talk to it unless I'm running closed-source blobs they control.
- AstralStorm 7y ago
  It still matters, as you will have options to build open replacements, ignore lock in. Hardware and firmware are bigger problems, as per cryptographic signing and legal framework to prevent breaking these solutions.