Bambu Lab is abusing the open source social contract
1399 points
• 6 days ago
• Article
Link
Jeff Geerling 一直批评 Bambu Lab 将其 3D 打印机转向"始终在线"的云模式。在 Bambu Lab 把云服务设为默认后，他通过 OPNsense 防火墙切断打印机的互联网连接，停止固件更新，将设备锁定在开发者模式，并把工作流从 Bambu Studio 换到 OrcaSlicer，以此维持对自己 P1S 的控制权。他承认自己希望完全拥有已购硬件的想法并不普遍，但 Bambu Lab 近期的做法促使他更严厉地发声。
导火索是 Bambu Lab 对一个名为 OrcaSlicer-bambulab 的 OrcaSlicer 分支的反应。该分支允许用户在不通过 Bambu 云的情况下使用打印机全部功能。 Bambu Lab 没有置之不理，而是以冒充和安全风险为由威胁开发者采取法律行动，尽管该分支照搬了 Bambu Studio 上游的 AGPL 授权代码。 Geerling 认为这种回应既令人费解又不成比例，尤其是在该分支在收到停止函前使用量极少的情况下。
Bambu Lab 在一篇博客中将该分支描述为严重的安全威胁，声称其会注入伪造的身份元数据，可能对其服务器造成结构性漏洞。 Geerling 指出讽刺之处：Bambu 自己的某个分支在 2022 年曾导致 Bambu 用户的遥测误发到 Prusa 的服务器上，Prusa 并未以法律威胁回应。他认为 Bambu 在滥用从中受益的 AGPL 许可，同时也误解了开源文化和基本安全原则——毕竟公开的 user-agent 字符串并不能作为防御 DDoS 的可靠手段。
Geerling 把 Bambu 的强硬做法与可行的温和处理方式对比，例如仅以商标为由要求开发者在分支名中去掉 "bambulabs" 。然而，Bambu 却公开将潜在的基础设施问题归咎于一名开发者。这与去年他们把社区的反弹称为"令人遗憾的误导信息"的做法一脉相承。更荒谬的是，涉事开发者此前还在 Bambu 的 GitHub 上帮助 Bambu Studio 用户解决 Linux 和 Wayland 问题。
更大的问题在于 Bambu Lab 正在逐步封闭其生态，背离了曾帮助他们建立社区的开源原则。 Geerling 指出，最简单也最有利可图的选择本来是无为而治，但他们选择压制那一小部分高级用户。 Louis Rossmann 已承诺出资 1 万美元帮助该开发者应对 Bambu 的法律威胁，Geerling 也愿意出力，但开发者可能并不想继续成为 Bambu 的靶心。对于重视开源和硬件所有权的用户来说，最实际的结论或许就是避开 Bambu Lab 。
Jeff Geerling has been a vocal critic of Bambu Lab's shift toward an always-connected cloud model for their 3D printers. After Bambu Lab started pushing their cloud solution as the default, he took steps to maintain control over his own P1S printer by blocking its internet access via his OPNsense firewall, stopping firmware updates, locking it into Developer mode, and switching from Bambu Studio to OrcaSlicer. He acknowledges he's unusual in wanting full ownership of hardware he purchased, but Bambu Lab's recent actions have pushed him to speak out more forcefully.
The immediate trigger for this post is Bambu Lab's response to a fork of OrcaSlicer called OrcaSlicer-bambulab, which allowed users to access all printer features without routing prints through Bambu's cloud. Instead of ignoring this small project, Bambu Lab threatened the developer with legal action, accusing the fork of impersonation and posing a security risk, despite the fork using Bambu Studio's upstream AGPL-licensed code verbatim. Geerling finds this response baffling and disproportionate, especially since the fork had minimal uptake before Bambu's cease and desist.
Bambu Lab published a blog post framing the fork as a serious security threat, claiming it injected falsified identity metadata and could cause structural vulnerability to their servers. Geerling points out the irony, noting that Bambu's own fork once caused Bambu users' telemetry to hit Prusa's servers in 2022, and Prusa didn't respond with legal threats. He argues that Bambu is misusing the AGPL license they benefit from and misunderstanding both open source culture and basic security principles, since a public user agent string is hardly a robust defense against DDoS attacks.
Geerling contrasts Bambu's heavy-handed approach with how the situation could have been handled, such as simply asking the developer to remove "bambulabs" from the fork's name for trademark reasons. Instead, they publicly blamed one developer for potential infrastructure problems, echoing a pattern from last year when they dismissed community backlash as "unfortunate misinformation." The developer in question had previously helped Bambu Studio users with Linux and Wayland issues on Bambu's own GitHub, making the legal threat especially absurd.
The broader issue is Bambu Lab's increasing lock-in of their ecosystem, moving away from the open source principles that helped build their community. Geerling notes that it would have been easier and more profitable for Bambu to do nothing, but they chose to suppress a tiny fraction of power users. Louis Rossmann has pledged $10,000 to help the developer fight Bambu's legal threats, and Geerling would contribute too, but the developer may not want to remain in Bambu's crosshairs. The practical takeaway for users who value open source and hardware ownership might be to simply avoid Bambu Lab altogether.
427 comments • Comments Link
• Bambu Lab 的打印机以无与伦比的易用性和性价比著称，但其封闭的生态、对云服务的依赖以及最近对开源分支采取的法律行动，已经疏远了注重隐私和开源的用户。 Prusa 等替代品牌更开放、便于维修，但价格显著更高；而来自 Elegoo 、 Creality 和 Qidi 等的新一代廉价机型在限制更少的情况下，也能提供颇具竞争力的功能。
• 在主要厂商中，Prusa 仍然被视为对开源最友好的品牌。尽管他们最近为打击中国克隆机而限制了设计的商业使用——有人认为这是求生之道，也有人认为这背离了开源精神。 Core One 系列高度可靠且可升级，但缺乏强力腔室加热，难以应对某些高端材料。
• Bambu 要求打印任务通过其云服务器路由，即便是在局域网打印的情况下也一样。这一做法引发了强烈反弹。虽然存在仅局域网模式，但要启用该模式现在需要关闭云功能或进入开发者模式，而这会移除访问控制。许多人认为这不是技术限制，而是有意为之的锁定策略。
• 当 Bambu 向一个模仿其用户代理的开源 OrcaSlicer 分支发出停止令时，争议进一步升级。批评者认为这违背了 Bambu Studio 所采用 AGPL 许可证的精神，而 Bambu 则声称该分支未经授权访问其服务器导致服务中断并违反了用户协议。
• 有人推测 Bambu 的做法受到国家压力影响，尤其有报道称中国制造的无人机在乌克兰被远程停用开关禁用。然而也有反驳意见指出，Bambu 的云依赖早于战争开始，且在无互联网条件下的局域网打印仍能正常运行，使得间谍指控难以证实。
• 尽管存在道德和隐私方面的担忧，许多用户仍然容忍 Bambu 的做法，因为其硬件"开箱即用"，在一个挑剔的打印机市场中带来了媲美 iPhone 的使用体验。对非技术用户而言，便利往往比隐私或开放性更重要，尤其是当仍可通过 SD 卡离线打印时。
• 更广泛的趋势反映了开源理想与商业现实之间的张力：像 Prusa 与 Bambu 这样的公司从社区贡献中获益，但又面临着保护收入免受克隆品与未经授权使用的压力。这催生了一种"源码可得但非真正开源"的混合模式，模糊了开放与控制的界限。
• 远程打印在专业环境中很常见，但将敏感设计通过 Bambu 的服务器路由，确实带来了合理的知识产权和安全顾虑。即便遥测数据并无恶意，缺乏加密与潜在的数据泄露风险也使其在企业或国防相关场景中存在危险性。
• 3D 打印市场竞争日益激烈。 Bambu 的主导地位促使竞争对手在易用性和可靠性上加紧追赶，但目前尚无替代品能在速度、自动化与开箱即用体验上完全匹配 Bambu，这使其仍是初学者的默认选择，尽管围绕其做法的争议不断。
• 归根结底，这场辩论的核心在于用户是更看重所有权、隐私与自由，还是更看重无缝的功能性。尽管 Bambu 的硬件广受好评，其日益收紧的软件策略和对开源开发者的对抗姿态表明，除非市场压力迫使其改变，否则用户对设备控制权可能会进一步被削弱。
讨论显示出实用主义者与纯粹主义者之间的深刻分歧：前者重视 Bambu 带来的无与伦比的易用性，后者则认为其封闭生态与法律打压与用户自由根本不相容。虽然存在替代方案，但在同等价位上很少有能提供同等即插即用可靠性的产品，这使许多用户陷入两难。 Bambu 针对开源开发者的做法已经损害了信任，但其出色的硬件仍让愿意妥协的用户继续使用。这一局面凸显了科技行业的常见模式：便利往往会占上风，直到反弹达到临界点。 Bambu 是否会修正航向，可能取决于它愿意冒多大风险失去市场份额给更开放的竞争对手。 • Bambu Lab printers offer unmatched ease of use and price/performance, but their closed ecosystem, cloud dependencies, and recent legal threats against open-source forks have alienated privacy-conscious and open-source advocates. Alternatives like Prusa are more open and repairable but significantly more expensive, while newer budget options from Elegoo, Creality, and Qidi offer competitive features with fewer restrictions.
• Prusa remains the most "open-source-friendly" major brand, though they've recently restricted commercial use of their designs to combat Chinese cloning—a move seen by some as necessary for survival and by others as a betrayal of open-source principles. Their Core One line is highly reliable and upgradeable, but lacks strong chamber heating for advanced materials.
• Bambu's requirement to route prints through their cloud servers—even for local network printing—has sparked major backlash. While LAN-only mode exists, enabling it now requires disabling cloud features or using developer mode, which removes access controls. This design choice is viewed by many as intentional lock-in rather than a technical limitation.
• The controversy intensified when Bambu sent a cease-and-desist letter to an OrcaSlicer fork that impersonated Bambu's user agent to enable cloud printing without official software. Critics argue this violates the spirit of AGPL, under which Bambu Studio is licensed, while Bambu claims unauthorized access to their servers caused outages and breaches user agreements.
• Some speculate Bambu's behavior stems from state pressure, especially given reports of Chinese drones being disabled in Ukraine via kill switches. However, others counter that Bambu's cloud requirements predate the war and that LAN-only printing remains fully functional without internet access, making espionage claims unproven.
• Despite ethical concerns, many users tolerate Bambu's practices because the hardware "just works"—comparable to the iPhone experience in a market plagued by finicky printers. For non-technical users, convenience often outweighs privacy or openness, especially when prints can still be done offline via SD card.
• The broader trend reflects a tension between open-source ideals and commercial reality: companies like Prusa and Bambu benefit from community contributions but face pressure to protect revenue from clones and unauthorized use. This has led to hybrid models that are "source-available" but not truly open, blurring the line between openness and control.
• Remote printing is common in professional settings, but routing sensitive designs through Bambu's servers raises legitimate IP and security concerns. Even if telemetry isn't malicious, the lack of encryption and potential for data exposure makes it risky for corporate or defense-related use.
• The 3D printing market is becoming more competitive, with Bambu's dominance pushing rivals to improve ease of use and reliability. However, no current alternative matches Bambu's combination of speed, automation, and out-of-box experience—making it the default choice for beginners despite its controversies.
• Ultimately, the debate centers on whether users prioritize ownership, privacy, and freedom versus seamless functionality. While Bambu's hardware is widely praised, its increasingly restrictive software policies and adversarial stance toward open-source developers suggest a future where user control continues to erode unless market pressure forces a change.
The discussion reveals a deep divide between pragmatists who value Bambu's unmatched usability and purists who see its closed ecosystem and legal aggression as fundamentally incompatible with user freedom. While alternatives exist, none offer the same plug-and-play reliability at a comparable price, leaving many users conflicted. Bambu's actions—especially targeting open-source developers—have damaged trust, but their hardware excellence ensures continued adoption among those willing to accept trade-offs. The situation underscores a recurring tech industry pattern: convenience often wins until backlash reaches a tipping point, and whether Bambu course-corrects may depend on how much market share it risks losing to more open competitors.