Bambu Lab: Difference between revisions

(13 intermediate revisions by 5 users not shown)

Line 39:

==Incidents==

===Bambu Lab A1 NTC thermistor fire and meltdown hazard===

===Authorization Control System (''2025'')===

Line 51:

Line 54:

===Cease and desist against OrcaSlicer fork maintainer (''2026'')===

{{~~Main~~|Bambu Lab cease and desist against OrcaSlicer fork developer}}

{{Excerpt|Bambu Lab cease and desist against OrcaSlicer fork developer}}

In April 2026, Bambu Lab sent a private cease-and-desist demand to Pawel Jarczak, a Polish developer who had published an OrcaSlicer fork restoring direct printer control on top of Bambu Lab's own AGPL-licensed source code. Bambu Lab alleged the fork constituted impersonation of Bambu Studio, bypassed authorization controls, violated their Terms of Use, and involved reverse engineering.<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=2026-04-30 |access-date=2026-05-04 |website=[[GitHub]]}}</ref> Jarczak rejected these characterizations, stating his work was based on publicly available AGPL source code, and asked for specifics about which files or commits were at issue. He reports receiving further broad accusations rather than specificity.<ref name="jarczak-readme" />

Jarczak removed the repository voluntarily but stated the removal should not be interpreted as an admission that the legal or technical allegations were correct.<ref name="jarczak-readme" /> On May 7, 2026, Bambu Lab published a blog post re-characterizing the dispute as being about "impersonation" through a "falsified" HTTP User-Agent string, rather than about open-source rights.<ref name="bambu-blog-record-straight">{{Cite web |title=Setting the record straight on Cloud Access and Community |url=https://blog.bambulab.com/setting-the-record-straight-on-cloud-access-and-community/ |website=Bambu Lab Blog |publisher=Bambu Lab |date=2026-05-07 |access-date=2026-05-10 |url-status=live}}</ref> The User-Agent string in question is generated by Bambu Lab's own AGPL-licensed source code in <code>src/slic3r/Utils/Http.cpp</code>.<ref>{{Cite web |title=Http.cpp source file (User-Agent setter at line 175) |url=https://github.com/bambulab/BambuStudio/blob/master/src/slic3r/Utils/Http.cpp |website=GitHub |publisher=Bambu Lab |access-date=2026-05-10 |url-status=live}}</ref>

The incident was covered by XDA Developers, Tom's Hardware, 3Druck, and Manufactur3D, and became a flashpoint in the wider 3D-printing community over open-source licensing and consumer rights.<ref>{{Cite web |last=Batt |first=Simon |date=2026-04-23 |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=2026-04-27 |access-date=2026-05-04 |website=XDA Developers}}</ref><ref>{{Cite web |title=Developer re-enables 3D printer features that Bambu Lab disabled, firm promptly threatens legal action — OrcaSlicer-BambuLab project now shuttered |url=https://www.tomshardware.com/3d-printing/developer-re-enables-3d-printer-features-that-bambu-lab-disabled-firm-promptly-threatens-legal-action-orcaslicer-bambulab-project-now-shuttered |website=Tom's Hardware |date=2026-04-29 |access-date=2026-05-10 |url-status=live}}</ref>

===Farm Manager subscription potential===

Line 66:

Line 63:

===Helio Additive===

In mid-2025, Bambu Lab added a new functionality in a form of a third party cloud service where you can send your design to get a thermal analysis, which can be used later to optimize the print adjusting the temperature (for [https://www.helioadditive.com/pricing paid membership]). Besides privacy concerns of sharing the designs with a Chinese startup, the functionality is restricted to an online-only model, with no offline simulation alternative, limiting potential open-source or community-driven innovation.

In 2026 this was integrated into bambu slicer as non-removable advertising <ref>{{Cite web |title=Mastodon post from @[email protected] |url=https://connectified.com/@masukomi/116736929422875166 |url-status=live |archive-url=https://archive.is/1HHyv |archive-date=2026-06-12 |website=connectified}}</ref>

==Comparisons to similar practices==

Line 72:

Line 71:

[[HP]]'s printer firmware updates have rendered third-party ink cartridges unusable, leading to class-action settlements in both the United States and the European Union.<ref>{{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> The Federal Trade Commission's May 2021 report ''Nixing the Fix'' described firmware-mediated cartridge restrictions as a recurring repair-policy issue.<ref>{{Cite web |title=Nixing the Fix: An FTC Report to Congress on Repair Restrictions |author=Federal Trade Commission |url=https://www.ftc.gov/system/files/documents/reports/nixing-fix-ftc-report-congress-repair-restrictions/nixing_the_fix_report_final_5521_630pm-508_002.pdf |website=Federal Trade Commission |date=2021-05-06 |access-date=2026-05-10 |url-status=live}}</ref>

Within the 3D-printing industry, the now-defunct manufacturer [[MakerBot]] followed a similar trajectory, shifting from open-source, DIY-focused machines to closed-source, proprietary ones, which ultimately drove customers to less-expensive open-source competitors and contributed to MakerBot losing its position as an industry leader.<ref>{{Cite web |last=Benchoff |first=Brian |date=2016-04-28 |title=The MakerBot Obituary |url=https://hackaday.com/2016/04/28/the-makerbot-obituary/ |url-status=live |archive-url=http://web.archive.org/web/20251208222057/https://hackaday.com/2016/04/28/the-makerbot-obituary/ |archive-date=2025-12-08 |access-date=2025-05-01 |website=[[Hackaday]]}}</ref>

Within the 3D-printing industry, the now-defunct manufacturer [[MakerBot]] followed a similar trajectory, shifting from open-source, DIY-focused machines to closed-source, proprietary ones, which ultimately drove customers to less-expensive open-source competitors and contributed to MakerBot losing its position as an industry leader.<ref>{{Cite web |last=Benchoff |first=Brian |date=2016-04-28 |title=The MakerBot Obituary |url=https://hackaday.com/2016/04/28/the-makerbot-obituary/ |url-status=live |archive-url=http://web.archive.org/web/20251208222057/https://hackaday.com/2016/04/28/the-makerbot-obituary/ |archive-date=2025-12-08 |access-date=2025-05-01 |website=Hackaday}}</ref>

==See also==

*[[Creality]]

*[[MakerBot]]

*[[Formlabs]]

*[[Bambu Lab Authorization Control System]]

*[[Bambu Farm Manager]]

Line 88:

[[Category:{{PAGENAME}}]]

[[Category:Companies]]

[[Category:Bambu Lab]]

[[Category:Feature Ransom]]

[[Category:3D printers]]

[[Category:Open source]]

[[Category:3D printing]]

@@ Line 39: / Line 39: @@
 ==Incidents==
+===Bambu Lab A1 NTC thermistor fire and meltdown hazard===
+{{Excerpt|Bambu Lab A1 NTC thermistor fire and meltdown hazard}}
 ===Authorization Control System (''2025'')===
 {{Main|Bambu Lab Authorization Control System}}
@@ Line 51: / Line 54: @@
 ===Cease and desist against OrcaSlicer fork maintainer (''2026'')===
-{{Main|Bambu Lab cease and desist against OrcaSlicer fork developer}}
+{{Excerpt|Bambu Lab cease and desist against OrcaSlicer fork developer}}
-In April 2026, Bambu Lab sent a private cease-and-desist demand to Pawel Jarczak, a Polish developer who had published an OrcaSlicer fork restoring direct printer control on top of Bambu Lab's own AGPL-licensed source code. Bambu Lab alleged the fork constituted impersonation of Bambu Studio, bypassed authorization controls, violated their Terms of Use, and involved reverse engineering.<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=2026-04-30 |access-date=2026-05-04 |website=[[GitHub]]}}</ref> Jarczak rejected these characterizations, stating his work was based on publicly available AGPL source code, and asked for specifics about which files or commits were at issue. He reports receiving further broad accusations rather than specificity.<ref name="jarczak-readme" />
-Jarczak removed the repository voluntarily but stated the removal should not be interpreted as an admission that the legal or technical allegations were correct.<ref name="jarczak-readme" /> On May 7, 2026, Bambu Lab published a blog post re-characterizing the dispute as being about "impersonation" through a "falsified" HTTP User-Agent string, rather than about open-source rights.<ref name="bambu-blog-record-straight">{{Cite web |title=Setting the record straight on Cloud Access and Community |url=https://blog.bambulab.com/setting-the-record-straight-on-cloud-access-and-community/ |website=Bambu Lab Blog |publisher=Bambu Lab |date=2026-05-07 |access-date=2026-05-10 |url-status=live}}</ref> The User-Agent string in question is generated by Bambu Lab's own AGPL-licensed source code in <code>src/slic3r/Utils/Http.cpp</code>.<ref>{{Cite web |title=Http.cpp source file (User-Agent setter at line 175) |url=https://github.com/bambulab/BambuStudio/blob/master/src/slic3r/Utils/Http.cpp |website=GitHub |publisher=Bambu Lab |access-date=2026-05-10 |url-status=live}}</ref>
-The incident was covered by XDA Developers, Tom's Hardware, 3Druck, and Manufactur3D, and became a flashpoint in the wider 3D-printing community over open-source licensing and consumer rights.<ref>{{Cite web |last=Batt |first=Simon |date=2026-04-23 |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=2026-04-27 |access-date=2026-05-04 |website=XDA Developers}}</ref><ref>{{Cite web |title=Developer re-enables 3D printer features that Bambu Lab disabled, firm promptly threatens legal action — OrcaSlicer-BambuLab project now shuttered |url=https://www.tomshardware.com/3d-printing/developer-re-enables-3d-printer-features-that-bambu-lab-disabled-firm-promptly-threatens-legal-action-orcaslicer-bambulab-project-now-shuttered |website=Tom's Hardware |date=2026-04-29 |access-date=2026-05-10 |url-status=live}}</ref>
 ===Farm Manager subscription potential===
@@ Line 66: / Line 63: @@
 ===Helio Additive===
 In mid-2025, Bambu Lab added a new functionality in a form of a third party cloud service where you can send your design to get a thermal analysis, which can be used later to optimize the print adjusting the temperature (for [https://www.helioadditive.com/pricing paid membership]). Besides privacy concerns of sharing the designs with a Chinese startup, the functionality is restricted to an online-only model, with no offline simulation alternative, limiting potential open-source or community-driven innovation.
+In 2026 this was integrated into bambu slicer as non-removable advertising <ref>{{Cite web |title=Mastodon post from @[email protected] |url=https://connectified.com/@masukomi/116736929422875166 |url-status=live |archive-url=https://archive.is/1HHyv |archive-date=2026-06-12 |website=connectified}}</ref>
 ==Comparisons to similar practices==
@@ Line 72: / Line 71: @@
 [[HP]]'s printer firmware updates have rendered third-party ink cartridges unusable, leading to class-action settlements in both the United States and the European Union.<ref>{{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> The Federal Trade Commission's May 2021 report ''Nixing the Fix'' described firmware-mediated cartridge restrictions as a recurring repair-policy issue.<ref>{{Cite web |title=Nixing the Fix: An FTC Report to Congress on Repair Restrictions |author=Federal Trade Commission |url=https://www.ftc.gov/system/files/documents/reports/nixing-fix-ftc-report-congress-repair-restrictions/nixing_the_fix_report_final_5521_630pm-508_002.pdf |website=Federal Trade Commission |date=2021-05-06 |access-date=2026-05-10 |url-status=live}}</ref>
-Within the 3D-printing industry, the now-defunct manufacturer [[MakerBot]] followed a similar trajectory, shifting from open-source, DIY-focused machines to closed-source, proprietary ones, which ultimately drove customers to less-expensive open-source competitors and contributed to MakerBot losing its position as an industry leader.<ref>{{Cite web |last=Benchoff |first=Brian |date=2016-04-28 |title=The MakerBot Obituary |url=https://hackaday.com/2016/04/28/the-makerbot-obituary/ |url-status=live |archive-url=http://web.archive.org/web/20251208222057/https://hackaday.com/2016/04/28/the-makerbot-obituary/ |archive-date=2025-12-08 |access-date=2025-05-01 |website=[[Hackaday]]}}</ref>
+Within the 3D-printing industry, the now-defunct manufacturer [[MakerBot]] followed a similar trajectory, shifting from open-source, DIY-focused machines to closed-source, proprietary ones, which ultimately drove customers to less-expensive open-source competitors and contributed to MakerBot losing its position as an industry leader.<ref>{{Cite web |last=Benchoff |first=Brian |date=2016-04-28 |title=The MakerBot Obituary |url=https://hackaday.com/2016/04/28/the-makerbot-obituary/ |url-status=live |archive-url=http://web.archive.org/web/20251208222057/https://hackaday.com/2016/04/28/the-makerbot-obituary/ |archive-date=2025-12-08 |access-date=2025-05-01 |website=Hackaday}}</ref>
 ==See also==
 *[[Creality]]
 *[[MakerBot]]
+*[[Formlabs]]
 *[[Bambu Lab Authorization Control System]]
 *[[Bambu Farm Manager]]
@@ Line 88: / Line 88: @@
 [[Category:{{PAGENAME}}]]
+[[Category:Companies]]
+[[Category:Bambu Lab]]
 [[Category:Feature Ransom]]
 [[Category:3D printers]]
 [[Category:Open source]]
+[[Category:3D printing]]