• 119 Posts
  • 35 Comments
Joined 2 years ago
cake
Cake day: December 19th, 2024

help-circle







































  • They are using an open source license. They threatened a developer to remove the code, most people believe that they want to lock the printers in the same way that HP does. They want you to pay a subscription. What they basically did form my understanding is take an open source code and add a cloud component to it, but they did not make that open source even though the open source license requires that all code be made open source

    It was built on top of PrusaSlicer, which itself came from Slic3r. Both predecessors carry the AGPLv3, and so does every derivative built from them. SFC looked at both the userspace software and the firmware running on Bambu’s devices and pointed out the violations.

    The first is about libbambu_networking, a networking library that ships with Bambu Studio across Linux, Windows, and macOS. It handles all communication between the slicer and Bambu’s cloud.

    Bambu has never made the source code for it available, despite AGPLv3 requiring that any code distributed alongside an AGPLv3 project be released under the same terms. SFC says Bambu’s own README has effectively sat with this admission for years now.

    The second violation comes from how Bambu handled Paweł Jarczak, a developer who built a fork of OrcaSlicer that could communicate with Bambu’s servers by studying the incomplete Bambu Studio source code.

    He did not touch the proprietary library at all. Bambu still contacted him, demanded removal, and stated a cease-and-desist letter had been prepared, arguing its terms of service take precedence over the license.

    You see the problem? The AGPLv3 explicitly says no one can place additional restrictions on the rights it grants. The SFC says going after Pawel the way Bambu did is itself a violation.

    https://itsfoss.com/news/bambu-lab-caught-violating-agplv3/