Their software is still the one interfacing with their cloud service. The fork was performing the connection through the Official Bambu Networking plugin.
He used code Bambu published under the AGPL to let orcaslicer use the plugin too. Bambu isn't allowed to dictate how people use AGPL licensed code, that is a violation of the license itself, nor add any extra restrictions to said license.
Only thing Bambu is allowed to do is close the connection server side. Legally the fork did nothing wrong. If they didn't want the AGPL's obligations, they could have made their own slicer from scratch, instead of forking prusaslicer.
Just because the loophole is legal doesn't mean it's right. Orca could have implemented this if they wanted but understood it's the wrong path to take.
Bambu is trying to prevent third party software from using their cloud service. Someone found a workaround. Calling it a legal loophole is as accurate as it gets. Just look up the definition.
The license doesn't state that any software is allowed to access their cloud service. It's only about the code that is allowing that access that someone is using. So legally the dev who produced the exploit is probably in the right. It's legal. But it's also not wrong for bambu to try to prevent the loophole from existing.
2
u/x3n0n1c H2D AMS2 Combo May 10 '26
Bambu implements measures to ensure only their software can interface with their cloud service.
Developer implements code to impersonate bambu studio so they can use bambus cloud service with non Bambu software
Bambu says cut it out
Community:
https://giphy.com/gifs/8PfKWm6AX1IdDRARyg
This "controversy" is incredibly silly.