Lots of drama with Bambu lately. Archive: https://archive.today/HrySB From the post: >>This text describes the problem with bambu_networking based on the public Bambu Studio source code. This is not about whether Bambu Lab must allow every fork into its cloud. That is a separate topic. This is about something simpler: Bambu Studio is an AGPL v3 program, and its public code shows that the closed bambu_networking component is downloaded, installed, dynamically loaded and used as an integral part of the program's operation. In my opinion, this is an AGPL compliance problem, because the AGPL requires the "Corresponding Source" of the program to be provided, and the definition of "Corresponding Source" also includes the source code of shared libraries and dynamically linked subprograms if the program is specifically designed to require them through intimate data communication or control flow. That is exactly the kind of situation visible in the Bambu Studio code.