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.
i'm mostly printing small mechanical parts and i can't say i have any complaints, i assume a modern prusa would be much better, surely there are other FDM printers that are good?
I thought that was the point, that people didn't want to be tethered to their servers?
There are many reasons one might prefer OrcaSlicer over Bambu Studio. One might be perfectly fine using Bambu's cloud services while preferring OrcaSlicer for different reasons; this is for those people.
Others might not want to use Bambu's cloud services at all; OrcaSlicer as it currently exists is fine for them.
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.
This sounds really unpleasant to use. Maybe users just want a better UX for the local mode?
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.
Murfalo•1h ago
https://www.youtube.com/watch?v=1jhRqgHxEP8
Aurornis•24m ago
There’s basically no information there. Is this just a copy of the other GitHub repo that was removed and someone is trying to rebrand it as their own? Or did they do some different work?
em-bee•16m ago
the explanation for that is here https://youtu.be/II2QF9JwtLc
basically louis found that not using AI to design his website drastically reduced the hits he would get from google.
andhug•9m ago