Restore full BambuNetwork support for Bambu Lab printers

Murfalo

https://www.fulu.org/ https://www.youtube.com/watch?v=1jhRqgHxEP8

hsuduebc2

If Bambu Lab responds to this criticism with lawyers instead of clear technical answers, it will only make the forced cloud requirement look more suspicious. To me, this is an obvious security risk. These printers are often used in labs, startups, engineering teams, and potentially even government environments. If print data, models, logs, or usage patterns are routed through a company controlled infrastructure, that creates a real opportunity for corporate espionage or data harvesting. I would not be surprised if Bambu Lab eventually faces the same level of scrutiny that Huawei network devices did.

nubinetwork

> This version of OrcaSlicer restores full BambuNetwork support for Bambu Lab printers I thought that was the point, that people didn't want to be tethered to their servers?

Our_Benefactors

For a moment I thought this was a way to get cloud printing restored to bambu printers without leaving lan-mode, would have been nice

bri3d

This looks to be a clone of the prior state of the repository that caused all the Bambu drama earlier this week. I did a ton of research because I didn't understand what people wanted here, and this is what's going on: Right now, Bambu have adjusted their system into two modalities: * "default" or "Cloud" mode, where you get an app, remote monitoring, but you have to use Bambu Studio or Bambu Connect to send prints. They implemented this by adding cloud auth to their "internal API;" the client application has to get a token from Bambu's servers, even if the request it eventually makes is a "local" one. * LAN / Developer mode, where the device displays a token and you put it into your app. This disables all of the remote monitoring but in exchange, clients can send prints locally. What users want is to "have their cake and eat it too;" they want the local token authentication _and_ the cloud authentication enabled at the same time. This isn't actually possible, so this plugin approximates it by emulating the interface to the cloud authentication to make the "Bambu Network" cloud RPC calls from a local slicer (one of these calls is a local_print call, so ostensibly this allows you to send prints without running them through the cloud, although with all of the online functionality still enabled and required, this seems like a pretty brave thing to trust). Personally, I find the Bambu reaction distasteful, and there's an argument that the offline mode only exists due to similar outrage, but I don't see the current system as particularly bad and find the appetite to restore "untrustworthy" cloud functionality a bit amusing.

h4kunamata

Two words: Good luck! At this poting BL is just like USA tech companies, touch their food and you are toasted. Sell your printer while you can get the its worth back.

amazingamazing

I have an Ender3 that I use plugging in a microsd card to do prints with. What am I missing here? Seems like you can do the same with these printers. People want to use the cloud?

laweijfmvo

Imagine if traditional printers were this big of a pain to use… oh

djfergus

What is Bambu’s motivation here? What do they get for damaging their credibility like this? Just usage data? Training a model on everyone’s STL files?

asveikau

Squashing the git history is not cool.

ghostpepper

A lot of the distrust toward Bambu is because they originally announced cloud auth would be required even for printing locally in LAN mode, and only backpedalled on that when they saw the backlash. I'm not sure why their entire domain has been excluded from archive.org but you can still see the original post for now: https://blog.bambulab.com/firmware-update-introducing-new-au... -- Critical Operations That Require Authorization The following printer operations will require authorization controls: Binding and unbinding the printer. Initiating remote video access. Performing firmware upgrades. Initiating a print job (via LAN or cloud mode). Controlling motion system, temperature, fans, AMS settings, calibrations, etc.

shevy-java

It was a mistake by BambuLab to piss off and alienate the community. They poked the bear; stung the bee; squashed the frog. This is literally the Barbara Streisand effect in the modern era. Now people are watching. Reputation went out the window already: "If they can sue one of us, they can sue all of us". (Well, threaten to sue at the least, aka applying financial pressure on that developer.)

mrdoosun

The important part here is not just printer support, but whether users can keep using hardware they already own without depending on a vendor cloud path. Local network support tends to look like a convenience feature until it disappears. Then it becomes obvious that it was part of the ownership model.