• 0 Posts
  • 7 Comments
Joined 3 years ago
cake
Cake day: October 5th, 2021

help-circle
  • As far as I’m aware, contributions from major corporations to GNU Core Utilities specifically (e.g. sed, awk, ls) have been limited. Most development has historically come from the GNU community and individual contributors. For example, UTF-8 support was likely added through community efforts rather than corporate involvement. However, as these corporations increasingly back projects moving away from GNU and the GPL, their intent to leverage the permissive nature of the MIT license becomes evident. Should ‘uutils’ gain widespread adoption, it would inevitably lead to a significant shift in governance.


  • Yes, they do. The GPL’s copyleft clause requires companies to release the source code of any modifications they distribute, ensuring contributions back to the community. The MIT license, however, allows proprietary forks without this obligation. In other terms, the MIT license is effectively permitting companies to “jump out” of the open-source ecosystem they make use of.


  • While shifting to Rust might be a good idea for improving safety and performance, adopting the MIT license represents a fundamental change that will enable large tech companies to develop and distribute proprietary software based on the new MIT-licensed Core Utilities. This shift moves away from the original vision of the project which was to ensure that the software remains free and open as enshrined in the GPL’s copyleft principles. The permissive nature of the MIT license also will increase fragmentation, as it allows proprietary forks that diverge from the main project. This could weaken the community-driven development model and potentially lead to incompatible versions of the software.


  • In a capitalist system, finding ethical funding models for free software is challenging but essential. Monetizing user data may seem like a viable solution, but it undermines the very principles of freedom and trust that free software stands for. Instead, we should explore community-driven models, such as donations, grants, or ethical partnerships, to ensure financial sustainability without compromising user rights. Supporting these alternatives is crucial to building a future where free software can thrive ethically.


  • Ubuntu’s search feature, which sent user queries to Amazon without consent, qualifies as spyware due to its lack of transparency and user control. This was not an accidental oversight but an intentional decision to monetize user data, prioritizing profit over privacy.

    Consider the Facebook-Cambridge Analytica scandal, where user data collected under the guise of social engagement was exploited for political manipulation. Similarly, the Lavender study reveals how surveillance data has been weaponized to target individuals in Gaza, with profiling systems feeding military operations and resulting in wrongful deaths.

    These cases highlight how data collection practices, even if introduced for financial or operational convenience, can spiral into harmful misuse. While Ubuntu may not directly lead to such outcomes, normalizing these practices lowers the threshold for future abuse. Vigilance and ethical standards are essential to safeguard against such risks.


  • tiny flaw

    Canonical deliberately spied on its users without their consent by forwarding search queries to Amazon via a malicious feature. Users searching their computer locally would not expect their queries to be broadcast externally. Following public backlash, Canonical allowed users to disable this behavior. However, Canonical continues to collect certain types of user data for commercial purposes. These practices present significant issues for those who support free software principles.

    Ubuntu Spyware: What to do?