Bambu Lab Authorization Control System: Difference between revisions
→Customer Reactions: correcting FUD |
→Advocacy for Open Ecosystem Support: correcting FUD |
||
| Line 147: | Line 147: | ||
Community members have also organized to advocate for open-source support and rollback options. Suggestions include: | Community members have also organized to advocate for open-source support and rollback options. Suggestions include: | ||
* Allowing an opt-out option for existing users who prefer local network control without cloud dependency. | * Allowing an opt-out option for existing users who prefer local network control without cloud dependency. | ||
** It should be pointed out that this has always been possible and past firmware updates made signing into the cloud at any point completely unnecessary. This information continues to be ignored by some. | |||
* 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 -->== | ||