Bambu Lab Authorization Control System: Difference between revisions

Conflict with Open Source and Maker Values: this is just not true, deleting
Line 150: Line 150:
* Providing an official API for third-party slicers under specific licensing agreements that allow secure authorized usage.<ref>https://github.com/SoftFever/OrcaSlicer/issues/8063</ref>
* Providing an official API for third-party slicers under specific licensing agreements that allow secure authorized usage.<ref>https://github.com/SoftFever/OrcaSlicer/issues/8063</ref>
== Bambu Corporate Strategy vs Maker Community Values<!-- the framing of this whole section comes across as quite opinionated, and it repeats a lot of factual information from earlier. reccommend cutting most of it, and reducing to a paragraph or two detailing the community response -->==
== Bambu Corporate Strategy vs Maker Community Values<!-- the framing of this whole section comes across as quite opinionated, and it repeats a lot of factual information from earlier. reccommend cutting most of it, and reducing to a paragraph or two detailing the community response -->==
=== Conflict with Open Source and Maker Values ===
Bambu Lab's printers had previously been praised for their integration with open-source tools & community-developed software{{Citation needed}}. The authorization system departs from , moving from an open ecosystem where users could freely modify & automate their printers to a closed, manufacturer-controlled environment. This change impacts:
* Users of open-source slicing software like OrcaSlicer
* Community developers who create tools and modifications
* Users who modify their printers' behavior through custom scripts and automation
* Those who prefer local network control over cloud-based solutions<ref>https://forum.bambulab.com/t/this-new-auth-system-will-make-me-sell-my-printers/135400</ref>


=== Impact on Professional Users and Print Farms ===
=== Impact on Professional Users and Print Farms ===