Bambu Lab Authorization Control System: Difference between revisions

Line 113:

=== 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:

* '''Lack of transparency''': The limited warning to OrcaSlicer devs suggests that Bambu Lab prioritized internal rollout schedules over community engagement with existing customers. Point to the contrary: ~~The~~ new firmware is in beta and Bambu Connect middleware contains temporary compomises to allow third-party slicers to work as before.

* '''Lack of transparency''': The limited warning to OrcaSlicer devs suggests that Bambu Lab prioritized internal rollout schedules over community engagement with existing customers. Point to the contrary: the new firmware is in beta and Bambu Connect middleware contains temporary compomises 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. By abruptly altering the compatibility landscape, Bambu Lab is seen as undermining good-faith initiatives to improve the ecosystem for everyone. The decision to restrict network APIs in favor of proprietary systems such as Bambu Connect represents a broader industry trend of closing off ecosystems that were once open, removing customer choice, privacy, and freedom.

* '''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.

== Community-driven workarounds and technical alternatives ==

@@ Line 113: / Line 113: @@
 === 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:
-* '''Lack of transparency''': The limited warning to OrcaSlicer devs suggests that Bambu Lab prioritized internal rollout schedules over community engagement with existing customers. Point to the contrary: The new firmware is in beta and Bambu Connect middleware contains temporary compomises to allow third-party slicers to work as before.
+* '''Lack of transparency''': The limited warning to OrcaSlicer devs suggests that Bambu Lab prioritized internal rollout schedules over community engagement with existing customers. Point to the contrary: the new firmware is in beta and Bambu Connect middleware contains temporary compomises 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. By abruptly altering the compatibility landscape, Bambu Lab is seen as undermining good-faith initiatives to improve the ecosystem for everyone. The decision to restrict network APIs in favor of proprietary systems such as Bambu Connect represents a broader industry trend of closing off ecosystems that were once open, removing customer choice, privacy, and freedom.
 * '''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.
 == Community-driven workarounds and technical alternatives ==