Concerns regarding potential copyright infringement

[jchv]

Bambu Studio Version

2.6.1

Where is the application from?

Bambu Lab GitHub releases, Built from source by yourself or others

OS version

NixOS

Additional system information

No response

Printer

Bambu Lab X1C

How to reproduce

1. Fork the source code
2. Await Bambu Lab legal council

Actual results

It seems that this results in a cease and desist that Bambu Lab does not seem to want published.

Expected results

Since the code is AGPL, I would not expect this to happen. Since the aforementioned code was based on code from this repo, I can only surmise that the code in this repo is actually infringing on the copyright of Bambu Lab and should not be included in an AGPL release.

This is an interesting development. Last time Bambu Lab was in the news, I had to block my printer access from the network. This time, I think the most appropriate workaround may be to change vendors.

Project file & Debug log uploads

Project File: https://github.com/bambulab/BambuStudio
Log File: https://youtu.be/jIbpQtoz6hs

I sincerely hope you find the infringing code.

Checklist of files to include

• Log file
• Project file

[hotellonely]

The bambu networking plugin is based on non-free libraries. It is optional to the Bambu Studio and provides extended networking functionalities for users. By default, after installing Bambu Studio without the networking plugin, you can initiate printing through the SD card after slicing is completed.

[jchv]

It seems though the legal complaint doesn't actually surround the code of the proprietary Bambu Lab network plugin, but rather code surrounding it. As far as I can tell, this is largely based on code from this repository. That seems to be the issue. OrcaSlicer does not redistribute the Bambu Lab proprietary network plugin in any of its repositories to the best of my knowledge. Of course, I can't tell what the complaint is actually about, since Bambu Lab appears to not want anyone to read it, which is usually a good sign that it's a strong argument.

[hotellonely]

It seems though the legal complaint doesn't actually surround the code of the proprietary Bambu Lab network plugin, but rather code surrounding it. As far as I can tell, this is largely based on code from this repository. That seems to be the issue. OrcaSlicer does not redistribute the Bambu Lab proprietary network plugin in any of its repositories to the best of my knowledge. Of course, I can't tell what the complaint is actually about, since Bambu Lab appears to not want anyone to read it, which is usually a good sign that it's a strong argument.

Both parties haven't published the original mail exchanges yet so there are too many guesses around.
The problem is that even the Linux plugin is still proprietary for BBL. So yes, you can reverse engineer that protocol and utilize it (even if it's against the user agreement/EULA, it's still your right in most countries, and the only thing bambu can really do against you is to block your user account). So now it comes to where that dev live and what did he exactly do, what bambu exactly wrote.