I use the cheapest filament I can find on Amazon. I have a huge amount of non-Bambu filament in-stock; in fact, I have zero Bambu filament in-stock. If they are going to limit my X1C to Bambu filament, then the printer will go silent and put in a closet.
This is a joke, they are not going to do that. They have clarified that, and that would be highly illegal.
No it is not. Maybe if you didn’t “use the cheapest filament I can find on Amazon” then you would have less failures.
3 Likes
I second this. I’ve been trying to avoid everything that depends on cloud. The whole bambu handy cloud thing is an eyesore that we have to live with.
This new auth system is just the last straw that tips people over.
I wonder if this is the time for someone to go a great length to rip apart all electronics of x1c or p1s and slap some opensource 3d printer motherboard on it. I think it is viable.
2 Likes
What a great idea. Buy a perfectly working expensive device and then tear out the guts and replace the guts with hardware and software of questionable reliability.
1 Like
Between the sales, unshipped item and now this. This forum isn’t what it was when I joined.
I’m just watching everyone fall apart until the smoke clears and everyone realizes all is going to be fine.
4 Likes
I’m just watching everyone fall apart until the smoke clears and everyone realizes all is going to be fine.
Famous last words…
3 Likes
My life doesn’t revolve around 3D printers, they do what I want them to do. Read through the proposed update, don’t see anything that’s going to keep my printers from printing.
2 Likes
My life doesn’t revolve around my phone either. Yet if Apple tells me that, due to security reasons, I am no longer allowed to choose a provider and therefore must use Apple’s own service and only their service. I get suspicious.
4 Likes
Ok, I lied a bit there. I use my phone more than I care to admit… But you get the point 
Let me know your price and I’ll pay shipping!!!
2 Likes
If my understanding of the last update is correct with this “developer mode” feature, I might be able to tolerate it (if I some day accidentally upgrade the firmware). Assuming nobody points out something I missed that would be a deal breaker.
Buying another BL printer remains off the table, though. Trust level doesn’t fall back into place so easily. Oh well.
Probably the only thing that’d repair the damage for me is something that would be considered drastic, like making all firmware source-available, and releasing anything else crucial for us to have full control over our hardware.
I won’t hold my breath.
1 Like
Already happening.
9 Likes
BL seems to be in the gaslighting “don’t believe your lying eyes” and “you didn’t really read what you think you just read” mode.
Stop deflecting, obfuscating, wordsmithing, and BSing, BambuLab.
Until then, and until you reverse course completely on this “security” update, you won’t see another dime from me.
14 Likes
What timing; I just acquired a P1S, A1 Combo, and a bunch of filament last week. Luckily, I’m still within my return window to Micro Center and Bambu (14 days) which gives me time to think about my printer refresh with Prusa CORE One, and maybe a Creality. After reading/watching over a few viewpoints and standpoints from various channels, my biggest takeaway is the “security” reason behind locking out OrcaSlicer. Not to mention the “security” architecture is rudimentary at best…it’s a shame since many peers speak highly about these printers in terms of ease of use and quality.
Ooooooooh, the fun had already started before BBL pulled this stun.
Now it just need more people getting involved
5 Likes
I have one of their filament dryers, complete junk.
In the end repurposed a food dehydrator at 1/4 the cost and 200% the power.
I was just thinking of buy a A1 until I saw this stunt. I am very grateful I saw this before I purchased. I am big on open-source, people owning the things they bought, and as such freedom to do whatever you want with what you bought. If I bought this printer and saw that I would immediately have refunded.
1 Like
You’re a bit late to the party, there were a couple of things that BambuLab backtracked on from the original announcement that started this whole debacle:
- They announced upcoming changes to the X1 firmware (and P/A series to follow) which introduce an additional middleware that one must use to talk with their printers regardless of mode they’re running - this effectively breaks every 3rd party tool commonly used with their printers including Orca Slicer which is, arguably, used more than their own Bambu Studio (and for a good reason).
- They said that they are working with 3rd party tool developers to address this, where we got back from Orca Slicer devs that they were downright denied to implement the new protocol (allegedly, BL did create a PR which embeds their Connector in Orca but that wasn’t available at the time)
- BL TOS explicitly said (and still says) that your printing requests might be denied until a firmware update is applied - where BL in their follow-up tried to gaslight everybody that this is not the case
- BL edited the original announcement to add that you don’t have to update your firmware (which kind-of contradicts the aforementioned TOS) - but then say goodbye to the promised 5 years of updates
- The middleware itself wasn’t explained well leading to people wondering what all this ‘authorization’ means and leading to a very valid conclusion that their printers alongside with the said Connector will need to, at least occasionally, speak with BL servers to establish this authorization - this effectively means no real LAN-only mode
- It was cleared up later (in posting the authorization pathway diagram and post-factum adding a so-called Developer Mode) that in LAN-only mode the printer will not have to speak with BL servers - but then this raises a valid question - how does then this new middleware improve security? (which it doesn’t)
This all happened in the span of 5 days so sure, the situation is a bit clearer now, but there are still many, many unanswered questions. All BL got out of this is a severely broken trust.
No matter how you slice it [ha!], this is both a PR and technological disaster - PR because they even to this day cannot come up with coherent message and seem to only do reactive damage control using gaslighting, vague promises and assurances (which do not work all that well when the trust is lost), and technological because everything we found out both from BambuLab’s own posts and disassembling of their new Connector screams: amateur hour. They’re literally attempting to pull security-through-obscurity, a very badly implemented one at that, and are alienating their loyal user base in the process without increasing their security whatsoever.
This whole disaster could’ve been easily mitigated with a ~$20k cybersec consultant fee. Of course, I’m still coming from the good-will argument that their goal here was to actually increase security, not to further tighten down control over the pathways to talk with their printers in the hope of putting everything through one funnel - and then figuring out how to monetize their control over that funnel.
14 Likes
Or even a much cheaper dinner with a couple of security expert / open source software friends… 
I mean, c’mon… even I could figure out a static private/public key pair you are gonna distribute with every copy of the middleware was a very bad idea … ffs… it should be no different to SSH keys … generate locally , transfer to printer, done. No central copy, no bambu servers, nada. Not that I’m saying the middleware was a good idea either… but still… another episode of “what were they thinking” 
7 Likes