Bambu's proprietary networking plugin uses the agpl libraries from slic3r/prusaslicer, by not releasing the source code they're violating the AGPL.

Some time ago the printers were able to communicate over both cloud and local protocols. Then, in a firmware update, they created distinct modes for those. You can still use the printers with OrcaSlicer, but in a mode that prevents being controlled by cloud too.

> I’m not going to sit through another angry Louis Rossmann video

Try https://youtu.be/0tdZ5Z7nRDY?si=vjnJ90p6ba_Xik9B for a less emotive take on this specific case, and the closely related matter of Bambu's attempt to circumvent some of AGPL's protections.

Very useful comment. I’ve had an A1 Mini for a year now and it has been my favourite purchase in years. Like when I got my first mobile phone, I feel like I’ll have some sort of 3d printer for the rest of my life. Bambu made it super easy and inexpensive for this to happen.

I’m completely against bullying and attempts to lock out open source software from using 3d printers directly; if they locked out OrcaSlicer from direct control I’d have a big problem with that.

But trying to interact directly with Bambu’s private infrastructure/APis seems reasonable for Bambu to block. I think a cease and desist might backfire on Bambu but i don’t think it’s unreadable. (Didn’t watch the video. Just getting context from parent comment. )

Although local LAN control is still unhindered, browsing the filesystem on the printer from the slicer is locked behind cloud mode.

Getting cloud mode means using Bambu Studio. Getting Bambu Studio means one more notch in slowly getting locked into the walled Bambu garden.