BambuLab basically locks down their entire 3D printer ecosystem with this ridiculous cloud authorization system.
You want to print locally via your LAN? Sorry, the cloud needs to authorize your g-code first.
Want to use another slicer to send your job to the printer? Sorry, no.
Would it really still surprise anyone if DRM'd filaments are next on their agenda? Their printers are good, their prices are cheap, but please, stop supporting this company.
https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/
@fribbledom@mastodon.social that's not true, you still can use other Slicers as described in the linked article, you just need an additional piece of software to sign your requests, to make sure that the printer cannot be used from unauthorized users
@kitsune_yasu I didn't claim otherwise. But let's not pretend this has anything to do with security.
Want to use another slicer to send your job to the printer? Sorry, no.I'd argue that this part is quite misleading.
let's not pretend this has anything to do with securityWell, if you want to make sure, that only authorized people can use the printer, than you need to add an authentication layer into the current protocol.
This system also prevents people, that can access your WLAN, to manipulate your printer as long as they don't have authorization to use it.
There would have been a multitude of ways to actually improve their security:
an Oauth API, API tokens, token/PIN exchange on the printer's display and/or a QR-code, an actual LAN-only mode, manual certificate exchange, ... I'll stop here.
All of these solutions would be absolutely feasible, actually secure, and would not lock you out from using a third-party slicer. Their solution isn't about security at all, it's only about controlling their ecosystem.
@fribbledom@mastodon.social This would still require you to have an additional piece of software that allows the authentication on top of the default protocol.
I agree that there should be an open solution for others in the long run.
Yes, but that's a solution that slicers can simply adopt and implement. Like they do for dozens of other protocols and auth mechanisms.
@fribbledom@mastodon.social Yes, but read the article.
THIS IS A BETA
The app is only there, so maintainers of slicers don't need to implement an Auth-System, as long as it is in an experimental phase.
I'll give you some time to read up on the news. I'm sure you'll eventually reach the same conclusions.
They also already made it very clear that they're not interested in working with OrcaSlicer or others to find a solution.
Bambu Lab will release technical documentation, new software, and offer support to assist partners in adapting their systems and developing software solutions compatible with the new X Series firmware and authorization controls.https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/
Yep, sounds that they are not interested in working with maintainers of other slicers /s
Please, try to catch up on the news first, so we can have a more informed discussion.
https://github.com/SoftFever/OrcaSlicer/issues/8063#issuecomment-2599741800
try to catch up on the news first, so we can have a more informed discussionI'd like to have qualified sources and not some randoms in forums talking/speculating about things.
As far as I can see, BambuLab has already published ways for 3rd-Party Tools to still be able to work with their 3D-Printers.
And yes, I agree that it is not very comfortable if you need an additional tool to be able to send things to your printer.
But at the same time, you argue, that BambuLab is not interested in helping 3rd-Parties, which is wrong.
If they would like to restrict 3rd-Parties, they would not have developed the Connector, cause it is already integrated into their Network-Plugin for the Bambu Studio Slicer.
Additionally, there are some FAQs (which they updated 2 days ago) with the following statements:
Our team is actively working on submitting the integration code for Bambu Connect. Once submitted, it will be up to Orca to decide when and if to incorporate it into the slicer, enhancing the user experience. We anticipate the code will be available on GitHub within the next few days, ready for integration into the Orca codebase.
It’s important to note that this update is not intended to restrict third-party software use. In fact, we’ve actively collaborated with third-party print farm management software providers in the past and continue to support such partnerships. To further improve the user experience, we are introducing a new software solution that will address these limitations and enhance overall print farm management capabilities.
In these cases, we cannot guarantee long-term support for unofficial accessories unless they have been approved by us in advance. Once we became aware of the Panda accessories, we communicated these updates to their creators.https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/
That said, we welcome official collaborations with companies interested in developing accessories for Bambu Lab printers, as we have successfully partnered with other companies in the past, including E3D and Slice Engineering.
"Some randoms in forums". This is the author & maintainer of OrcaSlicer 
@fribbledom@mastodon.social
1. I was not talking about the GitHub-Link you send
2. Even if I meant that link, there is no evidence to proof that what they claim is true
3. I presented evidence that the claim is untrue, which you're just ignoring...
I don't see our discussion continue, if you just ignore the content of my statements.