Prusa has been around for years though, not just popped up before this X’mas.
The replacement printer package may include Prussa. I watched the industry since forever, watching as the early adopters fleshed out the promise. It was cool then, cool now, and going places Gene Roddenberry went on shrooms.
It’s amazing.
So you must have been aware of Prusa which started in 2012. Bambu Lab is actually quite new, starting their Kickstarter in 2022.
If you are so against printers made by chinese companies, why wouldn’t you use Prusa exclusively since years ago?
and after all thise, it is still a “may” include Prusa ![]()
My X1C has been blocked from the internet since January. It still reminds me to lube the lead screws.
I get being upset, i own an x1 as well. But being snippy with a support agent just makes someone elses life harder.
I may have to build my own. X1C gonna help.
You may want to double check where the kit to build your own printer come from. For example, a voron kit is most likely from China.
Also by continuing to use your X1C, aren’t you worry that it will become a participant in a global bot attack?
![]()
I’m learning to talk to it.
I think it is important to remember that the people that staff the support chat are not the CEO or head of marketing, they don’t even have a direct line to them. Often support people are pretty low on the totem pole. It’s a pretty crappy job because people think they have some right to be straight up rude to you. Basically you shouldn’t expect “support” to have the latest info of where the company is headed. They are there to help you with your order.
…by not being helpful (in any way, form or shape) at all…(playing the dead possum with paying customers, where dead means stupid)
My X1C is not blocked from the 'net. It is in LAN/Dev mode and permitted to ping microsoft.com for connectivity and pool.ntp.org for time. All other outbound connection attempts are killed as they appear, and new ones show up occasionally. The printer may be receiving tracking cookie instructions via mqtt via connection to the 'net proxied by MakerWorld or this forum. I’m studying the process, and am interested in what else is embedded in the mqtt connection.
I recognize the risk of being on the internet is real. There are so many ways to misuse our data. IE being a bot army.
There are lots of reasons that the company would want that data. For example, finding out what features are used. what problems… Can help the company focus attention on what to fix.
Even if it was open source, The data would be useless unless you understand the context. Only the ones collecting the data (and would not share that data) know enough of its providence to use it.
My hat goes off to you for digging into this. I look forward to your findings, and feel free to DM me if you’d rather discuss offline. Your work mirrors concerns I’ve had from my background in cyber security, where Bambu Lab’s data practices and transparency have looked shaky since their first product release. As my confidence dropped, I switched to LAN-only mode in January 2024 because I didn’t trust their lack of openness, especially around encrypted logs.
That same lack of transparency fueled the community backlash in January 2025 when they forced Bambu Connect under a security claim that collapsed within a day.
For me, that was the breaking point. I left their ecosystem and now support companies that take their customers seriously. Mistakes can be forgiven. A repeated pattern of disregard cannot.
Thankyou for your comments. There is much about BBL’s business model that runs contrary to basic 1st world practice; similar methodology and character as Huawei.
From the git-go Bambu Connect stunk. And still stinks. Why would you push out an obviously weak excuse to a non-existent problem? The answer, for me, was distraction. Distraction from what was upgraded alongside Connect: the network plugin.
I use Orca. I’m not 100% sure this setting was there prior to the emergence of Connect but I don’t recall seeing it:
Orca Stealth mode showed up in the Spring of 2024, and it was one of the signals that pushed me to question Bambu Lab’s data practices. By that point I had already moved to LAN-Only mode and frozen my firmware because of the pattern that appeared with the jump from 1.03 to 1.04. That was the first time Bambu blocked users from backrevving their firmware. If you upgraded to 1.05 and the system became unstable, you had no ability to roll back as a diagnostic step to 1.04.
The second indicator came from SoftFever. Orca’s developers added an explicit option to block outbound data. That feature has nothing to do with print quality, which suggests the team saw enough risk to justify the work. Their decision aligned with what many users suspected but couldn’t prove.
Individually these issues could be dismissed. Taken together, they show a pattern of behavior from Bambu that raises legitimate trust concerns.
Thanks for that; I thought it may have been a followup to this, as softfever gained access to the network plugin code. The monitoring continues…
That link is important context. I left Bambu Studio behind before the Bambu Connect situation, so I wouldn’t have seen Noisyfox’s post on GitHub. For those not familiar with who he is, his response is significant because he was a core early contributor to Bambu Studio and the primary force behind Orca, all on a volunteer basis. Bambu even expressed gratitude to him for significant contributions to Bambu Studio.
His criticism of the anti-debugging code isn’t a minor complaint. It points directly to a shift in how Bambu treats the developers who helped strengthen their ecosystem. When someone with his history publicly objects, it exposes how much distance Bambu has created between itself and the community that supported the product from the beginning.
The points raised in that GitHub thread reflect the same pattern discussed throughout this forum thread: decisions made without regard for the community, followed by frustration from the people who contributed the most to the platform’s growth.
Howdy mates,
I am a huge BambuLab fan and I love the community and these awesome printers.
Being of meager means
(however embarrassingl but honest, handicapped & artist = probably the worst financial combo on the planet?)
I bit the bullet, got the loans, and got the X1CC very early followed by a second X1CC not far after, incredibly happy with them and the endless possibilites doing art, prototypes or just experience fun stuff other shared.
The reality is I will be paying back the loans on these for another couple of years, and possibly even worse, drooling after something larger buildplate in the H series…
But now the X1C is “sold out”, does this mean they basically are absolete and Bambu dropped us supporter and fanclubmembers like a hot potato?
Forgive me but I’m neither clever enough nor knowledgeable enough about the 3D printing world to assess what to read out of this?
(I was hoping I happily could use my X1CC’s for a decade or more if I kept them in top shape & fully maintained by schedule.)
I was thinking about trippling up on going full r and maxing up my downpayment schedule and get the H2C, but honestly now I’m scared to even go for the H2S since I cant figure out if the Bambu printers by above deduction is only a couple of years before discontinuation?!?
Has anyone heard anything about this, and if not how is it possible they simply sell out the flagship and give no feedback to us fans, customer & owners of their flagship products?
I paused my purchase basket and look forward to your knowledge mates!
Your thoughts are most welcome mates!
/TheSwedishChupacabra




