[bdcravens]

They used a plugin to communicate print jobs (and other integrations), so that third party software could be used pretty seamlessly. Now they're moving to a new authentication model, and will be requiring users to send files to a separate print app. (Bambu Connect) It adds friction to the process, especially for those who were looking to run print jobs at scale, using "print farm" software or building their own solutions.

[c0nsumer]

I do wonder how much friction it'll really add, since the slicers can send the data to Connect via a protocol handler.

It also means that Connect could act as a farm / queueing system as well, more like a print driver vs. individual printer support within the app.

[bdcravens]

I've tried the URL handler (the software is in beta). It only sends the print job (sliced file), it doesn't start it. You still have to assign it to the printer, etc, and press the start button.

[c0nsumer]

That doesn't seem any harder because you have to do that with the Network Plugin via a popup window. Or am I missing something else?

[intothemild]

Its pretty much this, nothing seems to be blocking any third party slicer like Orca from working with bambu printers as they are now.. just the print button would now send the file to Bambu Connect, where you would most likely only press an extra button..

Getting info from the printer or AMS? MQTT still works. They specifically said they are not touching that.

Sadly the usual groups of people are screaming, and the open printer people are laughing. But at worst.. this is just friction.

Anyone pointing this out seems to get downvoted. But its all there in the bambu press statement and subsequent pages. Those that are upset seemed to have not read those, and instead just read or watched something inflammatory.

[autoexec]

> just the print button would now send the file to Bambu Connect, where you would most likely only press an extra button..

Today it's just one extra button press. In 5-10 years when they shut down the servers for Bambu Connect nobody would be able to print anything at all. It's only because people were vocal in their complaints that their unsupported dev mode was made an option that would let people continue to use what they paid for

[c0nsumer]

Did you happen to see this? Interesting development, they are basically going to keep the current wide-open-barely-auth'd state and call it a developer mode. And submitted a PR to make Orca Slicer work with the new auth: https://blog.bambulab.com/updates-and-third-party-integratio...

And yeah, I'm realizing that about the downvotes. It's sad the state of things, but SKY-IS-FALLING-GET-PITCHFORKS wins the day over technical analysis, even on purportedly technical forums. But alas, that's an aside.

I'm really looking forward to this rolling out, as I want to monitor my printer with Home Assistant but I /really/ don't like how much control the current (non-beta, non-future) state gives HA. I /want/ auth of some sort when submitting jobs, and it looks like I'll have that.

(I also really want the slicer decoupled from the print management stuff, because I tend to keep a few slicers open and experiment.)

[bdcravens]

My understanding is that the "addition" of the developer mode (basically the current status quo) is the result of the feedback/pitchforking. I don't believe that was originally planned.