Bambu Lab, the company behind my favorite 3D printers<\/a>, has given itself one hell of a week. Now, I\u2019ve got answers to some of my burning questions, answers which you might also hopefully appreciate. But first, some backstory.<\/p>\n<\/div>\n Since last Thursday, some creators have pledged not to buy Bambu printers anymore, even removed some of their 3D models from its online repository, after the company revealed it would add a new proprietary authentication mechanism<\/a> that could keep you from using third-party tools to remote control your printer. <\/p>\n<\/div>\n While you\u2019d still be able to stick a file on an SD card and physically put it into your printer or use Bambu\u2019s proprietary cloud, the old way of printing remotely from a third-party slicer would be no more \u2014 unless you downloaded a new proprietary Windows and Mac \u201cBambu Connect\u201d desktop app to be the middleman between your slicer and Bambu\u2019s hardware.<\/p>\n<\/div>\n \u201cUnauthorized third-party software will be prohibited from executing critical operations\u201d \u2014 Bambu<\/p>\n<\/div>\n<\/div>\n While Bambu was clear early on that this would be an optional<\/em> update, one you could simply choose not to install, the company also positioned it as a necessary<\/em> one to secure printers against remote hacks. Some owners immediately saw that as a potential bridge to enshittification<\/a>, however.<\/p>\n<\/div>\n They noted how Bambu printers can already detect if you\u2019re using an official roll of filament and imagined a future where Bambu can keep you from using third-party filament at all. They noted how Bambu already seems to be planning a subscription service for its print farm software, one that requires regular cloud activations<\/a> and imagined a future where your Bambu printer stops working if you don\u2019t pay up. <\/p>\n<\/div>\n Bambu has denied these and many other such fears in a subsequent \u201csetting the record straight\u201d blog post<\/a>, and explained that its new tool doesn\u2019t require internet access or a user account \u2014 and has also backpedaled very slightly, pledging to offer an at-your-own-risk \u201cDeveloper Mode\u201d that maintains local access to your printer without any new proprietary authentication at all. Unfortunately, that mode may also disable your ability to access your printer via the cloud<\/a>. <\/p>\n<\/div>\n Meanwhile, Bambu didn\u2019t do itself any favors by keeping people from using the Wayback Machine<\/a> to scrutinize its changing statements, by allegedly censoring criticism of the company on its subreddit, and by claiming that the developer of Orca Slicer was working with Bambu on a seamless way to continue to print directly from his popular third-party slicer when they had not actually pledged their support<\/a>. <\/p>\n<\/div>\n It has also not helped confidence that Bambu\u2019s own security around its new Bambu Connect app is such that hackers have already extracted its private key and authentication certificate<\/a>, or that users have discovered that Bambu gives itself the right to block new print jobs until a printer has finished automatically downloading firmware updates in its Terms of Use<\/a>.<\/p>\n<\/div>\n Anyhow, I think the real question here is: are<\/em> these changes a stepping stone to more enshittification, or at least more of a walled garden, or not? <\/p>\n<\/div>\n Here are the questions I sent Bambu and the answers I got, via spokesperson Nadia Yaakoubi:<\/p>\n<\/div>\n 1) Will Bambu publicly commit to never requiring a subscription in order to control its printers and print from them over a home network?\u00a0<\/strong><\/p>\n<\/div>\n For our current product line, yes. We will never require a subscription to control or print from our printers over a home network. However, there might be specific business scenarios in the future that require exceptions, i.e a 3DP vending machine, but these would apply to entirely different applications and customer needs. If such a product line is introduced, we will clearly communicate this before its launch.\u00a0<\/p>\n<\/div>\n 1c) Will Bambu publicly commit to never putting any existing printer functionality behind a subscription?<\/strong><\/p>\n<\/div>\n 2) Will Bambu publicly commit to never restricting the use of third-party filament in any way, shape, or form?<\/strong><\/p>\n<\/div>\n For our current product line, yes. We have no plans to restrict the use of third-party filament in any way.\u00a0<\/p>\n<\/div>\n 3) Will Bambu publicly commit to never monitor files and prints transmitted between users and their printers over a home network?\u00a0<\/strong><\/p>\n<\/div>\n Let\u2019s be clear about how this works:<\/p>\n<\/div>\n Bambu has additionally agreed to add a new Developer mode. Some users are concerned that this move is just temporary and that Bambu can simply remove the developer mode and claim that it was too much of a security risk or say that not enough users opted to use it to justify keeping it around. <\/strong><\/p>\n<\/div>\n 4) Will Bambu publicly commit to permanently keep the Developer mode with local MQTT, livestream and FTP and never remove it in any future update or shipping batch of\u00a0the X1, P1, A1, and A1 Mini?\u00a0<\/strong><\/p>\n<\/div>\n Yes. However, if a severe security issue arises in the future, we may need to make adjustments to address it. Users can always choose whether to update their printer firmware or not.\u00a0<\/p>\n<\/div>\n 5) Will Bambu publicly commit to offering and keeping the local Developer mode available in any future printers it releases?<\/strong><\/p>\n<\/div>\n We cannot commit to features for non-existent future printers.\u00a0However, we will clearly communicate all relevant details before customers make their purchase decisions.<\/p>\n<\/div>\n 6) Will Bambu publicly commit to its current and future printers permanently being remotely controllable over LAN without user account or Internet access?<\/strong><\/p>\n<\/div>\n For current models: Yes. For future products, while we aim to retain this functionality, we believe committing to a specific technical approach indefinitely is not responsible. However, we will clearly communicate all relevant details before customers make their purchase decisions.<\/p>\n<\/div>\n Bambu has announced that Bambu Connect will integrate with third-party slicers like Orca, but some users are confused why an app like Bambu Connect is required at all when you could instead add more secure authentication to the printer itself, with industry standard practices like having the printer generate a secure token\/API key instead of creating a proprietary middleman authentication app.\u00a0<\/strong><\/p>\n<\/div>\n 7) Did Bambu consider and reject interoperable ways of securing its printers, like tokens?<\/strong><\/p>\n<\/div>\n 7b) Will Bambu commit to changing its authentication system to an interoperable one? If Bambu did reject interoperable secure authentication systems, why?<\/strong><\/p>\n<\/div>\n If software communicates and interacts with our cloud system, it is reasonable for us to have a say in how it operates. As highlighted\u00a0in our blog post<\/a>, unauthorized third-party software has created ongoing challenges to the stability of our cloud services and machines for a long time. <\/p>\n<\/div>\n While we trust that most developers act with good intentions, users are often unaware of the hidden complexities within such software and the security requirements. This lack of transparency of all software makes interoperable secure authentication systems insufficient to fully resolve these issues. Our goal is to safeguard the entire Bambu Lab product ecosystem, providing every user with confidence that our products are secure and easy to use\u2014free from concerns about complex network configurations. And with the changes done, we are one step closer to integrate third-party access in a secure way.<\/p>\n<\/div>\n 8) Is it true that the developer of Orca Slicer was not actually working with Bambu on the integration and that Bambu announced their involvement without approval?<\/strong><\/p>\n<\/div>\n We have been in ongoing discussions with SoftFever, the developer of Orca Slicer, since January 14 regarding the firmware update and potential integration into the new release. \u201cWork with\u201d might be ambiguous. To be more specific, messages were exchanged, files were sent, and their receipt was confirmed along with an indication that they would be reviewed.\u00a0<\/p>\n<\/div>\n 9) Will <\/strong>Panda Touch<\/strong><\/a> and similar accessories continue to work under Developer Mode?<\/strong><\/p>\n<\/div>\n We guarantee keeping the port\/channel open, but implementations are up to third-party developers.<\/p>\n<\/div>\n 9b) Is Bambu answering that company\u2019s questions?<\/strong><\/p>\n<\/div>\n Since the release, we have received many inquiries from third-party software developers, including BigTreeTech, via\u00a0devpartners@bambulab.com<\/strong><\/a>. We are currently in the process of finalizing our response. It\u2019s worth noting that we warned third party developers in a\u00a0blog post\u00a0<\/a>from March 2024:\u00a0\u201dIf you\u2019re developing a device that controls the entire printer, including heating elements and motion systems, please do not expect long-term support unless it has been approved by us in advance. This is especially applicable to for-profit organizations.\u201d<\/em><\/p>\n<\/div>\n 10) Will you allow users to roll back to the old firmware, for reasons like if they accidentally upgrade without understanding the limitations?<\/strong><\/p>\n<\/div>\n Yes. Firmware rollback was and always will be available.<\/p>\n<\/div>\n\n