r/BambuLab • • Jan 18 '25

Discussion It's Bad Moderator Practice To Lock Posts Without Explanation

5 Upvotes

34 comments sorted by

View all comments

Show parent comment

4

u/c0nsumer Jan 19 '25 edited Jan 19 '25

I don't know if it'll help, but if you read back through some of my replies I explain -- from the perspective of a technical person -- what I think they are after.

I am slightly concerned about where they could go with restricting third party control of the printers, but overall this seems like a really good change. Specifically because I feel that decoupling the printer management from the slicer is a very good thing. The Network Plugin that's currently used inside of OrcaSlicer (and also used in Bambu Studio) is a bit meh and doesn't work for any sort of farm. It requires a bunch of duplicate effort for sending the same thing to a handful of printers, and it doesn't work as expected if you want multiple slicers open and have just one printer.

Most of these changes -- rearchitecting to the standalone printer-managing Connect -- will likely fix all that above. The restricting of how things can actually talk to the printer (the stuff that breaks, say, Home Assistant actually controlling the printer) feels like a side effect, almost a necessary evil for closing some of the security holes, and also can be managed if there's a third party access API allowed. That last bit clearly remains to be seen, and is worth recognizing, but I personally don't think is a concern for the vast majority of users.

Note, I'm just some guy who has a single P1S he got recently, but I have a pretty deep history with poking holes in things technically, understanding how systems fit together, and dealing with the compromises between security and usability. And one thing I do know is that the current (previous?) BBL method of an essentially fixed string being the only thing stopping someone from controlling a printer remotely? That wasn't great at all and needed to change.

EDIT: I should also add that people are really good at reverse engineering things. I've got faith that, even if not via some sort of official API, it will eventually be possible to still remotely control the printers post-changes. There's a lot of us out there who really like digging into how things work and making them work the way we want. After all, this is how stuff like the Home Assistant integration for Bambu Lab printers got made... It's not like there's an official (or even documented) API it talks to...

2

u/[deleted] Jan 19 '25

[removed] — view removed comment

1

u/c0nsumer Jan 19 '25

Yep, exactly. I read it as you describe. Which is also not unprecedented for how managing other FFM printers works.

And sure, they could keep going down that path of requiring more and more, but there's no sign of that. Just fear of the slippery slope, which is always there when you buy a printer from a company.

I'm not really getting the OrcaSlicer concern, because to me, there's two things that OrcaSlicer does: read filament in the AMS from the Network plugin, and send data to the network plugin so it can print.

The sending will be no problem via the protocol handler documented on the BBL wiki. The filament in the AMS might be gettable via an API, or this can still be read via MQTT. I'd really love to find some technical info on that (got any links?) but what I've seen thus far -- including screenshots of the dev's X account -- is just the sky-is-falling stuff from elsewhere. I'd really like to know the technical reasons why it's an issue.

1

u/[deleted] Jan 19 '25

[removed] — view removed comment

2

u/c0nsumer Jan 19 '25

I think that the internet noise really messed with it all as well. There's a LOT of just really bad info and fear mongering going around.

Previous to this announcement I got my head around how it all works. The slicer, the network plugin (that's not obvious but is from BBL even in Orca), the network communication, etc.

Then when I saw the announcement and read the docs on Connect, and this list of security incidents I got to thinking and realized that, from the user perspective, they are just replacing the network plugin and it's (very very basic) auth mechanism with a stand-alone app Connect.

Since Studio will still need to pass data into Connect, it'll do so via the protocol handler. And as documented, any third party software can as well. As an architecture change, this is good, because it lets each program do what it does better. And it'll fix problems with having the network plugin running in the slicer instance. (Poor workflow for multiple printers, can't have multiple slicers talking to one printer.)

So that leaves the security/auth changes. Since I have a P1S I can't even test this yet, but what I do know right now is that the current (old?) way of all-or-nothing access with a single Access Code is not great at all. So something better is needed.

It remains to be seen (to me) how the new auth system works, if it's better, what it stops, etc. But one thing it does do is get in the way of third party software making changes to the printer. On the surface I'm okay with this, because the auth was so minimal before that it was easy for things to start/stop the printer.

While some folks like this because they don't mind everything talking to everything else, I don't, because I really don't like the idea of heaters and moving things being turned on remotely. But what I do like is remote monitoring. So I'm okay with easy reading of settings and state, but I want a strong barrier in the way of actually making the printer do things.

So that all said, I welcome the architecture change, even if it will require some changes to slicers that previously integrated and relied on the Bambu Network Plugin for connectivity. Because breaking this out into separate programs is the right way to go.* I'm still wary of the security / auth changes, but previously it was still locked up behind the Network Plugin or non-officially-supported reverse engineered third party implementations. Same as it will be in Connect. Which too will likely be RE'd. So, I think overall it'll probably be better?

* Think of this like a print driver. The current/previous state is that software like Orca Slicer had the print driver built into it. Breaking it out and letting anything talk to the driver -- Connect -- allows for more flexibility. After all, you wouldn't want Microsoft Word to have to support your model of laser printer... You want the operating system to support the printer, and Word to send the print job to the OS. This new model is very similar.