Bambu Lab Authorization Control System: Difference between revisions
mNo edit summary |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 6: | Line 6: | ||
|Description=On January 16, 2025,Bambu Lab announced that future firmwares for their 3D printers would have an authorization and authentication mechanism. | |Description=On January 16, 2025,Bambu Lab announced that future firmwares for their 3D printers would have an authorization and authentication mechanism. | ||
}} | }} | ||
On January 16, 2025, the 3D-printer manufacturer '''[[Bambu Lab]]''' announced that future firmwares for their 3D printers would introduce an authorization and authentication protection mechanism for their connection and control, [[Deceptive language frequently used against consumers|in the name of security]]. This mechanism restricts the use of third-party accessories and slicers, such as Panda Touch and OrcaSlicer. | On January 16, 2025, the 3D-printer manufacturer '''[[Bambu Lab]]''' announced that future firmwares for their 3D printers would introduce an authorization and authentication protection mechanism for their connection and control, [[Deceptive language frequently used against consumers|in the name of security]]. This mechanism restricts the use of third-party accessories and slicers, such as Panda Touch and OrcaSlicer. | ||
==Controversy regarding firmware updates== | ==Controversy regarding firmware updates== | ||
| Line 14: | Line 15: | ||
====Editing of initial announcement==== | ====Editing of initial announcement==== | ||
Bambu users were concerned they would not be able to | Bambu users were concerned they would not be able to use their printer if they did not install this update, due to the wording of the blog and the ToS.<ref>[[:File:Bambu tos screenshot.png]]</ref> This caused confusion since users report that Bambu's blog post dated January 16th<ref name="firmware-update-introducing-new-authorization-control-system-2" /> specifically says the following: | ||
<blockquote><strong>What happens if I never upgrade to this firmware?</strong> | <blockquote><strong>What happens if I never upgrade to this firmware?</strong> | ||
| Line 65: | Line 66: | ||
*'''Privacy concerns''': Requiring authentication for LAN mode raises concerns about data being unnecessarily exposed to Bambu Lab's servers, even for local-only operations, though previously, the printer was also connected and could be controlled by the cloud even when sending prints locally. | *'''Privacy concerns''': Requiring authentication for LAN mode raises concerns about data being unnecessarily exposed to Bambu Lab's servers, even for local-only operations, though previously, the printer was also connected and could be controlled by the cloud even when sending prints locally. | ||
**Confidentiality required by US Law - This is in conflict with those that have to comply with 18 CFR § 3a.61, 32 CFR § 117.15, 32 CFR § 2001.47, and other restrictions. | **Confidentiality required by US Law - This is in conflict with those that have to comply with 18 CFR § 3a.61, 32 CFR § 117.15, 32 CFR § 2001.47, and other restrictions. | ||
*'''Loss of offline independence while also using cloud''': Before, users could have hybrid offline setups. The requirement for authentication removes this option unless users revert to older firmware versions | *'''Loss of offline independence while also using cloud''': Before, users could have hybrid offline setups. The requirement for authentication removes this option unless users revert to older firmware versions; Bambu Lab initially indicated rollback would not be permitted, though The Verge later reported that users could still downgrade and use LAN access keys while signed into the cloud. | ||
*'''Increased complexity''': The added authentication layer complicates workflows for users who built custom setups or relied on third-party integrations for LAN control while retaining cloud functionality.<ref name=":4">{{Cite web |last=@edlboston |date=Jan 2023 |title=Full Non-Cloud Based Network Option Needed |url=https://forum.bambulab.com/t/full-non-cloud-based-network-option-needed/3643 |url-status=live |archive-url=https://ghostarchive.org/archive/1ee4F |archive-date=2026-03-30 |access-date=2025-05-01 |website=[[Bambu Lab]] Community Forum |quote=Yes, I know about the LAN mode. But as has been stated by many people, things like the camera will not work, nor will the Handy app. There is no technical reason that these are bound to the cloud. This is the problem and why I titled this FULL Non-Cloud Network.}}</ref> | *'''Increased complexity''': The added authentication layer complicates workflows for users who built custom setups or relied on third-party integrations for LAN control while retaining cloud functionality.<ref name=":4">{{Cite web |last=@edlboston |date=Jan 2023 |title=Full Non-Cloud Based Network Option Needed |url=https://forum.bambulab.com/t/full-non-cloud-based-network-option-needed/3643 |url-status=live |archive-url=https://ghostarchive.org/archive/1ee4F |archive-date=2026-03-30 |access-date=2025-05-01 |website=[[Bambu Lab]] Community Forum |quote=Yes, I know about the LAN mode. But as has been stated by many people, things like the camera will not work, nor will the Handy app. There is no technical reason that these are bound to the cloud. This is the problem and why I titled this FULL Non-Cloud Network.}}</ref> | ||
*LAN-Only mode in Orca Slicer is implemented by passing API Calls to the installed proprietary Bambu Network Plug-In (unlike BTT and other solutions that did indeed communicate with printer directly via MQTT protocol). | *LAN-Only mode in Orca Slicer is implemented by passing API Calls to the installed proprietary Bambu Network Plug-In (unlike BTT and other solutions that did indeed communicate with printer directly via MQTT protocol). | ||
*Plug-In provides controls for Printers "Critical Operations" (as classified by the Firmware Announcement article) and displays these controls within the window of Orca Slicer. | *Plug-In provides controls for Printers "Critical Operations" (as classified by the Firmware Announcement article) and displays these controls within the window of Orca Slicer. | ||
| Line 75: | Line 75: | ||
*While the user experience is different, the flow remains unchanged Orca Slicer slices model -> Orca Slicer Calls API of Bambu Proprietary Software -> Bambu Proprietary Software controls the printer. | *While the user experience is different, the flow remains unchanged Orca Slicer slices model -> Orca Slicer Calls API of Bambu Proprietary Software -> Bambu Proprietary Software controls the printer. | ||
Additionally, Bambu Connect software (downloaded and installed on 19.01.2024 (2025?) | Additionally, Bambu Connect software (downloaded and installed on 19.01.2024 (2025?) before the backlash response) supports adding LAN-Only printers without requiring Bambu Account authentication, the same behavior as the Network Plugin used in Orca Slicer. | ||
===Precedents and comparisons=== | ===Precedents and comparisons=== | ||
Critics have likened this potential functionality to similar cases in other industries where manufacturers remotely restrict product features. | Critics have likened this potential functionality to similar cases in other industries where manufacturers remotely restrict product features. A documented example is [[HP]]'s printer firmware updates that [[HP Instant Ink|rendered third-party ink cartridges unusable]], which became the subject of a class-action settlement.<ref name=":5">{{Cite web |last=Harding |first=Scharon |date=2025-03-19 |title=HP avoids monetary damages over bricked printers in class-action settlement |url=https://arstechnica.com/gadgets/2025/03/hp-avoids-monetary-damages-over-bricked-printers-in-class-action-settlement/ |url-status=live |archive-url=http://web.archive.org/web/20250319231817/https://arstechnica.com/gadgets/2025/03/hp-avoids-monetary-damages-over-bricked-printers-in-class-action-settlement/ |archive-date=2025-03-19 |website=Ars Technica}}</ref> | ||
===X1E firmware 01.01.02.00 LAN only connection "BUG"=== | ===X1E firmware 01.01.02.00 LAN only connection "BUG"=== | ||
| Line 146: | Line 146: | ||
==Communication with OrcaSlicer developers== | ==Communication with OrcaSlicer developers== | ||
Before the official announcement of the new authorization and authentication, Bambu Lab engaged with the OrcaSlicer development team regarding the changes. This communication has sparked | Before the official announcement of the new authorization and authentication, Bambu Lab engaged with the OrcaSlicer development team regarding the changes. This communication has sparked discussion within the 3D-printing community, particularly regarding its timing, tone, and implications. | ||
===Pre-announcement contact=== | ===Pre-announcement contact=== | ||
| Line 158: | Line 158: | ||
===How the community viewed these actions=== | ===How the community viewed these actions=== | ||
This approach has been interpreted by many as a calculated move by Bambu Lab to enforce tighter control over its ecosystem. Primary criticisms of Bambu were: | This approach has been interpreted by many as a calculated move by Bambu Lab to enforce tighter control over its ecosystem. Primary criticisms of Bambu were: | ||
*'''Lack of transparency''': The limited warning to OrcaSlicer | *'''Lack of transparency''': The limited warning given to OrcaSlicer developers indicates that Bambu Lab's internal rollout schedule preceded community engagement with existing customers. Point to the contrary: the new firmware is in beta and Bambu Connect middleware contains temporary compromises to allow third-party slicers to work as before. | ||
*'''Lack of follow-through:''' As of writing, SoftFever, OrcaSlicer's lead developer, still does not have API keys for Bambu Connect, a necessary layer of Bambu software that would need to be integrated into OrcaSlicer. Bambu's original announcement prominently mentioned OrcaSlicer and gave the impression that Bambu is actively providing the necessary assets so that SoftFever would be able to implement the new software architecture so that OrcaSlicer users are able to still use OrcaSlicer to send gcode to their printers without needing Bambu Connect to be installed as a separate program. The lack of active cooperation does not reflect favorably upon Bambu as it seems like their announcement used OrcaSlicer's name to try to make it seem like Bambu is trying its best to make sure that developers have what they need, but in reality, their inaction seems to show that Bambu is not making a sincere attempt to ensure that OrcaSlicer remains supported<ref name=":1" />. | *'''Lack of follow-through:''' As of writing, SoftFever, OrcaSlicer's lead developer, still does not have API keys for Bambu Connect, a necessary layer of Bambu software that would need to be integrated into OrcaSlicer. Bambu's original announcement prominently mentioned OrcaSlicer and gave the impression that Bambu is actively providing the necessary assets so that SoftFever would be able to implement the new software architecture so that OrcaSlicer users are able to still use OrcaSlicer to send gcode to their printers without needing Bambu Connect to be installed as a separate program. The lack of active cooperation does not reflect favorably upon Bambu as it seems like their announcement used OrcaSlicer's name to try to make it seem like Bambu is trying its best to make sure that developers have what they need, but in reality, their inaction seems to show that Bambu is not making a sincere attempt to ensure that OrcaSlicer remains supported<ref name=":1" />. | ||
*'''Disregard for open-source collaboration''': OrcaSlicer is widely used in the community; it is an open-source effort to improve the 3D-printing experience for all customers | *'''Disregard for open-source collaboration''': OrcaSlicer is widely used in the community; it is an open-source effort to improve the 3D-printing experience for all customers. The decision to restrict network APIs in favor of proprietary systems such as Bambu Connect removes customer choice in how the printer is operated. | ||
*'''Token support for third-party tools''': While Bambu Connect provides a workaround for third-party slicer use, it significantly restricts functionality and complicates workflows, leading many to question the sincerity of Bambu's stated support for open-source tools<ref name="bambu-connect" />. | *'''Token support for third-party tools''': While Bambu Connect provides a workaround for third-party slicer use, it significantly restricts functionality and complicates workflows, leading many to question the sincerity of Bambu's stated support for open-source tools<ref name="bambu-connect" />. | ||
*'''Power imbalance''': As the hardware manufacturer, Bambu Lab has the ability to dictate how its products can be used; often to the detriment of third-party developers and users. | *'''Power imbalance''': As the hardware manufacturer, Bambu Lab has the ability to dictate how its products can be used; often to the detriment of third-party developers and users. | ||
| Line 174: | Line 174: | ||
*Provide users with greater flexibility in integrating printers with home-automation systems and workflows. | *Provide users with greater flexibility in integrating printers with home-automation systems and workflows. | ||
However, custom firmware development faces | However, custom firmware development faces several challenges, including: | ||
*Limited documentation and proprietary hardware components, which complicate reverse-engineering efforts. | *Limited documentation and proprietary hardware components, which complicate reverse-engineering efforts. | ||
*The potential voiding of warranties and risks of bricking devices. | *The potential voiding of warranties and risks of bricking devices. | ||
| Line 197: | Line 197: | ||
*Creating local server emulations to replicate the network API previously available before the update. | *Creating local server emulations to replicate the network API previously available before the update. | ||
While these tools provide temporary solutions, they | While these tools provide temporary solutions, they do not fully replace the open ecosystem that existed before the authorization update. | ||
===Re-engineering printer-control electronics=== | ===Re-engineering printer-control electronics=== | ||
| Line 205: | Line 205: | ||
Community members have also organized to advocate for open-source support and rollback options. Suggestions include: | Community members have also organized to advocate for open-source support and rollback options. Suggestions include: | ||
*Allowing an opt-out option for existing users who prefer local network control without cloud dependency. | *Allowing an opt-out option for existing users who prefer local network control without cloud dependency. | ||
** | **This has always been possible; past firmware updates made signing into the cloud at any point unnecessary. This information continues to be ignored by some. | ||
*Providing an official API for third-party slicers under specific licensing agreements that allow secure authorized usage.<ref name="orca-slicer-issue8063" /> | *Providing an official API for third-party slicers under specific licensing agreements that allow secure authorized usage.<ref name="orca-slicer-issue8063" /> | ||
| Line 211: | Line 211: | ||
Currently X1Plus a OPEN SOURCE custom firmware version for Bambu Labs printers(more details on the GitHub page) | Currently X1Plus a OPEN SOURCE custom firmware version for Bambu Labs printers(more details on the GitHub page) | ||
* | *Installation tutorials are available for users who have not yet updated. Installing third-party firmware will void the warranty. Users are advised to consult the GitHub documentation before installation. | ||
*https://github.com/X1Plus/X1Plus | *https://github.com/X1Plus/X1Plus | ||
*The Bambu Labs website offers consumers the ability to request a rootable firmware to be sent to their printers. At the time of writing (Jan 26, 2025), the feature (in the EU at least) is broken such that you cannot finalize the process of requesting such a firmware. Ref: https://bambulab.com/en-eu/third-party-firmware/plan | *The Bambu Labs website offers consumers the ability to request a rootable firmware to be sent to their printers. At the time of writing (Jan 26, 2025), the feature (in the EU at least) is broken such that you cannot finalize the process of requesting such a firmware. Ref: https://bambulab.com/en-eu/third-party-firmware/plan | ||
**The result of accepting the terms of the page titled "Third Party Firmware Plan Guideline" and clicking "Next" takes you to a page titled "Important Notice and Risk Warning" which, when accepting the terms leaves you with an "I got it" button that takes you back to the previous page. | **The result of accepting the terms of the page titled "Third Party Firmware Plan Guideline" and clicking "Next" takes you to a page titled "Important Notice and Risk Warning" which, when accepting the terms leaves you with an "I got it" button that takes you back to the previous page. | ||
==Bambu | ==Cease and desist against the OrcaSlicer-bambulab re-enablement project== | ||
In April 2026, Bambu Lab sent a cease and desist communication to the developer of a third-party OrcaSlicer fork that had restored direct printer control after the Authorization Control System rollout. The project was wiped from public view the same day it appeared, and the developer published a summary of Bambu Lab's allegations but not the letter itself, citing Bambu Lab's refusal to authorize publication.<ref name="jarczak-readme">{{Cite web |last=Jarczak |first=Pawel |title=OrcaSlicer-bambulab — This is the end…. |url=https://github.com/jarczakpawel/OrcaSlicer-bambulab |url-status=live |archive-url=https://web.archive.org/web/20260430001537/https://github.com/jarczakpawel/OrcaSlicer-bambulab |archive-date=30 Apr 2026 |access-date=4 May 2026 |website=[[GitHub]]}}</ref> | |||
===What OrcaSlicer is=== | |||
OrcaSlicer is a free, open-source slicer: a program that converts a 3D model file into the layer-by-layer instructions (G-code) a 3D printer needs to produce the physical object. It is maintained by the developer SoftFever and draws from Bambu Lab's Bambu Studio, which is itself a fork of Prusa Research's PrusaSlicer.<ref name="softfever-orcaslicer">{{Cite web |last=SoftFever |title=OrcaSlicer |url=https://github.com/SoftFever/OrcaSlicer |url-status=live |access-date=4 May 2026 |website=[[GitHub]]}}</ref> OrcaSlicer is widely used by owners of Bambu Lab printers as an alternative to Bambu Studio.<ref name="softfever-orcaslicer" /><ref name="xda-jarczak">{{Cite web |last=Batt |first=Simon |date=23 Apr 2026 |title=A developer restored OrcaSlicer's features that Bambu Lab killed — then the legal threats arrived |url=https://www.xda-developers.com/developer-restored-orcaslicers-features-bambu-lab-killed-legal-threats-arrived/ |url-status=live |archive-url=https://web.archive.org/web/20260427233833/https://www.xda-developers.com/developer-restored-orcaslicers-features-bambu-lab-killed-legal-threats-arrived/ |archive-date=27 Apr 2026 |access-date=4 May 2026 |website=XDA Developers}}</ref> | |||
===What changed in January 2025=== | |||
The Authorization Control System announced on January 16, 2025 gated print initiation, motion control, fan and hotend temperature control, AMS configuration, calibrations, remote video, and firmware upgrade behind a Bambu-issued authentication path. Owners who installed the new firmware could no longer send print jobs from third-party slicers directly over the local network; they had to route those jobs through a new closed-source middleware, Bambu Connect.<ref name="firmware-update-introducing-new-authorization-control-system-2" /> SoftFever was not given API keys for Bambu Connect and stated publicly that direct print sending from OrcaSlicer would not be supported going forward.<ref name=":1" /> | |||
===The OrcaSlicer-bambulab fork=== | |||
On April 23, 2026, the developer Pawel Jarczak (GitHub user <code>jarczakpawel</code>) made public a fork named OrcaSlicer-bambulab at <code>github.com/jarczakpawel/OrcaSlicer-bambulab</code>. The fork restored the ability to send print jobs from OrcaSlicer directly to Bambu Lab printers without routing through Bambu Connect.<ref name="xda-jarczak" /> According to Jarczak's own description, the fork worked by reaching the printer through a Linux-side workflow Bambu Lab had not yet disabled, and was built on publicly available Bambu Studio source code combined with the developer's own integration layer; it did not redistribute Bambu Lab's proprietary networking plugin binaries.<ref name="jarczak-readme" /><ref name="3druck-jarczak">{{Cite web |date=30 Apr 2026 |title=Developer ends OrcaSlicer fork after Bambu Lab threatens legal action |url=https://3druck.com/en/programs/developer-terminates-orcaslicer-fork-after-bambu-lab-threatens-to-sue-32156744/ |url-status=live |access-date=4 May 2026 |website=3Druck.com}}</ref> | |||
===The cease and desist=== | |||
Bambu Lab contacted Jarczak directly and demanded removal of the fork. According to Jarczak's own first-person account, Bambu Lab "referred to legal materials and stated that a cease and desist letter had been prepared", and alleged that the implementation "impersonated Bambu Studio, bypassed their authorization controls, violated their Terms of Use, involved 'reverse engineering', and could allow modified forks to send arbitrary commands to printers."<ref name="jarczak-readme" /> Jarczak rejected the reverse-engineering characterization, stating that his work was based on publicly available Bambu Studio source code, which Bambu Lab releases under the AGPL-3.0 license.<ref name="jarczak-readme" /><ref name="3druck-jarczak" /> Jarczak disputed the broader characterization and asked for specifics: the exact files or commits at issue, and the exact legal or contractual basis. He reports receiving "further broad accusations" instead of that specificity.<ref name="jarczak-readme" /> Bambu Lab refused consent for publication of the correspondence itself, and Jarczak elected to honor that refusal while retaining the letter.<ref name="jarczak-readme" /> The repository was wiped the same day it appeared.<ref name="jarczak-readme" /><ref name="xda-jarczak" /> Jarczak removed the contents voluntarily and stated this was a practical decision, not an admission that the legal or technical allegations were correct.<ref name="jarczak-readme" /> XDA Developers reported that Bambu Lab had not responded to its request for comment as of publication.<ref name="xda-jarczak" /> 3Druck independently confirmed the same set of allegations, citing Jarczak's GitHub statement.<ref name="3druck-jarczak" /> | |||
The publicly documented allegations track Bambu Lab's [[Terms of Service]] and an "authorization bypass" framing.<ref name=":2" /><ref name="jarczak-readme" /> Because the letter itself was not made public, no primary source confirms which specific statute, if any, Bambu Lab invoked; neither Jarczak's account nor the secondary reporting names a specific statute, including the [[DMCA Section 1201|DMCA §1201]] anti-circumvention provision, as part of Bambu Lab's claim. The upstream OrcaSlicer maintainer SoftFever was not named in the cease and desist, has issued no public statement on the fork or the letter, and the upstream repository remains active.<ref name="softfever-orcaslicer" /> | |||
===Consumer-rights significance=== | |||
Bambu Lab printer owners had paid for hardware that, at the time of purchase, allowed third-party slicers to send print jobs directly over their own local network. The January 2025 firmware update removed that capability for owners who installed the update.<ref name="firmware-update-introducing-new-authorization-control-system-2" /> When an independent developer rebuilt the lost capability on top of source code Bambu Lab itself publishes, the company's response was a private legal threat rather than a technical or contractual remedy that the affected owners could read or contest.<ref name="jarczak-readme" /> The developer took the project down and stated he had "no interest in maintaining a prolonged dispute".<ref name="jarczak-readme" /> | |||
==Impact on professional users and privacy concerns== | |||
===Impact on professional users and print farms=== | ===Impact on professional users and print farms=== | ||
The restrictions imposed by the new authorization system create | The restrictions imposed by the new authorization system create operational challenges for professional users who kept their printers signed into the cloud: | ||
*Print farms can no longer use custom automation systems to manage multiple printers | *Print farms can no longer use custom automation systems to manage multiple printers | ||
| Line 241: | Line 262: | ||
While Bambu Lab maintains that cloud processing is necessary for security and functionality, community members argue this represents unnecessary data collection that could be handled locally<ref name="bambulab-forum-134549/12" />. The company's cloud infrastructure costs are significant, leading some users to speculate that future monetization of the cloud services may be planned<ref name="bambulab-forum-3643/5">{{Cite web |last=@NeverDie |date=Jan 2025 |title=Full Non-Cloud Based Network Option Needed |url=https://forum.bambulab.com/t/full-non-cloud-based-network-option-needed/3643/5 |url-status=live |archive-url=https://ghostarchive.org/archive/1ee4F |archive-date=2026-03-30 |access-date=2025-05-01 |website=Bambu Lab Community Forum |quote=I’m not disagreeing, but as a short-term workaround, are you able to write the print files to an SD card and then print from that? I’m too new to have tried it myself, but I thought that was at least an option.}}</ref>. Therefore, people should assess if their use case mandates the use of the cloud service and disable it when it doesn't. | While Bambu Lab maintains that cloud processing is necessary for security and functionality, community members argue this represents unnecessary data collection that could be handled locally<ref name="bambulab-forum-134549/12" />. The company's cloud infrastructure costs are significant, leading some users to speculate that future monetization of the cloud services may be planned<ref name="bambulab-forum-3643/5">{{Cite web |last=@NeverDie |date=Jan 2025 |title=Full Non-Cloud Based Network Option Needed |url=https://forum.bambulab.com/t/full-non-cloud-based-network-option-needed/3643/5 |url-status=live |archive-url=https://ghostarchive.org/archive/1ee4F |archive-date=2026-03-30 |access-date=2025-05-01 |website=Bambu Lab Community Forum |quote=I’m not disagreeing, but as a short-term workaround, are you able to write the print files to an SD card and then print from that? I’m too new to have tried it myself, but I thought that was at least an option.}}</ref>. Therefore, people should assess if their use case mandates the use of the cloud service and disable it when it doesn't. | ||
Users who do not want their print data routed through Bambu's cloud infrastructure can operate their printers in LAN-only mode. | |||
==Customer reactions== | ==Customer reactions== | ||
| Line 251: | Line 272: | ||
Many community members and customers ask whether the significant costs of maintaining and deploying this cloud infrastructure might lead to future monetization of these now-mandatory services,<ref name="bambulab-forum-3643/5" /> with subscriptions required for features that once worked with local access. | Many community members and customers ask whether the significant costs of maintaining and deploying this cloud infrastructure might lead to future monetization of these now-mandatory services,<ref name="bambulab-forum-3643/5" /> with subscriptions required for features that once worked with local access. | ||
So far, '''no changes have been made or indicated for those not using the cloud service'''. Past firmware updates made it possible to avoid using the cloud service completely by allowing pairing the slicer via IP address and access key and doing offline firmware updates without having to sign the printer into the service, not even temporarily, keeping local functionality unchanged. | |||
==Comparisons to similar practices by other companies== | ==Comparisons to similar practices by other companies== | ||
| Line 258: | Line 279: | ||
*'''Forced updates''': Firmware updates have rendered third-party ink cartridges incompatible, forcing users to purchase proprietary consumables. | *'''Forced updates''': Firmware updates have rendered third-party ink cartridges incompatible, forcing users to purchase proprietary consumables. | ||
*'''Restricted features''': Scanner/printer combos that will not scan if the ink is empty. | *'''Restricted features''': Scanner/printer combos that will not scan if the ink is empty. | ||
*'''Consumer backlash''': Users criticized these updates as anti-consumer, with some pursuing | *'''Consumer backlash''': Users criticized these updates as anti-consumer, with some pursuing {{Wplink|class action}} lawsuits]] for deceptive practices.<ref name=":5" /> | ||
Like 2D printers, Bambu Lab's update restricts functionality previously available to users and pushes them toward proprietary software and cloud-based control. | Like 2D printers, Bambu Lab's update restricts functionality previously available to users and pushes them toward proprietary software and cloud-based control. | ||