How a Private Message Could Reshape 3D Printing
▼ Summary
– Bambu Lab, a leading 3D printer maker, faces backlash after asking developer Paweł Jarczak to remove code that enabled remote control of its printers without its proprietary software.
– The 3D printing community, including advocates like Louis Rossmann and GamersNexus, is funding a legal defense for Jarczak and forking Bambu’s code in protest.
– Bambu’s software is built on open-source AGPL code from PrusaSlicer, and critics argue the company violates the license by locking down its system and threatening users who fork it.
– Legal experts disagree on whether Bambu’s proprietary networking plug-in must be shared under AGPL, noting the lack of clear court precedent on the license’s scope.
– Bambu claims its actions are for security, citing DDoS attacks, but Jarczak and others argue the company could fix vulnerabilities server-side instead of targeting developers.
A private message sent on Reddit has ignited a firestorm in the 3D printing world, pitting one of the industry’s most celebrated companies against a coalition of developers, YouTubers, and open-source advocates. The dispute threatens to reshape how 3D printers operate and who ultimately controls the hardware consumers own.
The conflict began when developer Paweł Jarczak received a direct message from Bambu Lab, the company widely recognized for producing the best and most accessible 3D printers on the market. Bambu asked Jarczak to remove code he had shared that enabled remote control of its printers without using the company’s proprietary software. What seemed like a simple request quickly spiraled into a full-blown confrontation over open-source licensing, digital rights, and the future of 3D printer accessibility.
Jarczak had created a fork of OrcaSlicer, itself a fork of Bambu’s own open-source software, to bypass a proprietary authentication mechanism Bambu had introduced. The company, which builds its software on the AGPL open-source license, wanted to lock down its system. But the community saw this as a betrayal of the very principles that made Bambu’s success possible.
The response was swift and fierce. Consumer rights advocate Louis Rossmann pledged $10,000 to defend Jarczak in court, declaring he wanted to “teach Bambu Labs a lesson.” Maker Jeff Geerling announced he would never buy another Bambu printer and offered to contribute financially. GamersNexus went further, pledging $10,000 and halting previously unannounced plans to purchase $150,000 worth of Bambu hardware for a 3D printing project. The outlet’s editor-in-chief, Steve Burke, told The Verge, “Go ahead, Bambu: Sue us.”
The Software Freedom Conservancy has now joined the fight, hosting a project to reverse engineer Bambu’s code and vowing to serve as a watchdog. Bradley Kühn, the architect of the AGPL license and a policy fellow at the organization, stated bluntly, “They’re bad actors, straight-up, and the community should do whatever we can.”
At the heart of the dispute is a fundamental question: Does Bambu’s reliance on open-source code obligate it to share the proprietary components that interact with that code? Bambu argues that its networking plugin is “separately delivered” and therefore not covered by the AGPL’s “Corresponding Source” requirements. But Kühn and Jarczak contend that the plugin’s intimate communication with Bambu’s open-source code makes it subject to the license’s sharing obligations.
Legal experts are divided. Kyle Mitchell, an independent tech lawyer, notes that the AGPL’s language is ambiguous enough that only court rulings could provide definitive answers. Heather Meeker, a prominent open-source licensing attorney, acknowledges that a plugin would “generally be part of Corresponding Source” but concedes that the law is unsettled.
Bambu maintains that its motive is security, pointing to millions of “abnormal requests” including DDoS attacks. But critics argue that the company could implement proper server-side authentication rather than relying on a lock that can be picked using its own open-source code. Jarczak insists he did not attack Bambu’s infrastructure, stating, “If they truly believed this was a live vulnerability, they should have fixed or disabled it on their side instead of threatening one developer.”
The standoff has galvanized thousands of open-source advocates who are now forking Bambu’s code and daring the company to take legal action. The Software Freedom Conservancy is seeking to raise over $250,000 to “liberate AGPLv3-violating 3D printers,” while Rossmann’s group has pledged $15,000.
Bambu has softened its stance somewhat, telling The Verge, “Our intention from the start was to reach out and find a path forward together. We regret that our communication did not land that way.” The company says it is now focusing on strengthening its infrastructure rather than escalating conflict.
Kühn offers a simple solution: “They should release all the code, even if the AGPL doesn’t require it, because their business is selling hardware anyway.” Alternatively, Bambu could rewrite its software from scratch. But Jarczak warns that a fully closed system would not be better for users, only “more honest.”
As the battle unfolds in the court of public opinion, the outcome could determine whether the next generation of 3D printers remains open and accessible or becomes locked down like today’s inkjet printers. For now, the community is watching closely, ready to act if Bambu’s worst tendencies prevail.
(Source: The Verge)
