Live data from Hacker News

Restore full BambuNetwork support for Bambu Lab printers

github.com

151–160 of 344 posts

Re: Restore full BambuNetwork support for Bambu Lab printers

#151

Earlier quoted context omitted.

But in this case the users want to use those features locally and are being blocked. Using a resource constraint argument doesn't make sense for it. It seems more likely they want it as a revenue source at some point.

> But in this case the users want to use those features locally and are being blocked No, we aren’t being blocked. Turn on LAN mode, pair regular Orca slicer, ignore Bambu for the rest of eternity. Plenty of people have done it.

> No, we aren’t being blocked. Turn on LAN mode, pair regular Orca slicer, ignore Bambu for the rest of eternity. Plenty of people have done it.

You're just saying that Bambu users feel the need to purposely circumvent Bambu's artificial restrictions to be able to continue to use Bambu hardware they bought and paid for.

No matter how you frame this, this ain't right.

Re: Restore full BambuNetwork support for Bambu Lab printers

#152
post #7

This looks to be a clone of the prior state of the repository that caused all the Bambu drama earlier this week. I did a ton of research because I didn't understand what people wanted here, and this is what's going on: Right now, Bambu have adjusted their system into two modalities: * "default" or "Cloud" mode, where you get an app, remote monitoring, but you have to use Bambu Studio or Bambu Connect to send prints.…

There is some context missing, which this video [0] explains.

tl;dr: The original developer does not (or cannot) go into legal battle with Bambu Lab, so Louis Rossmann's project picked up the fight and hosts the (allegedly) troublesome code on their organization. As they have more financial resources, they look forward to the C&D letter.

The point he has (and I agree with that): The original developer is using the un-modified AGPL-code to talk to the cloud API. Bambu Lab states that the modified client pretends to be a Bambu lab client. But in fact, the modified client just uses the code as-is, which is perfectly fine from a AGPL perspective. From my non-lawyer point of view: If Bambu Lab would have made the User Agent a configurable variable, which gets set by some configuration files from outside the code, that get bundled with the binary version, but not the source code, they wouldn't have this leverage.

[0]: https://www.youtube.com/watch?v=1jhRqgHxEP8

Re: Restore full BambuNetwork support for Bambu Lab printers

#153

Earlier quoted context omitted.

You're missing two things from the whole picture: 1. Cloud mode works without local network access, so their server is involved in the transit of the data to the printer. This is pretty minor, but still within their rights to preserve. 2. For printing from the app, they actually run the computationally expensive slicing algorithm on their servers, so this is totally reasonable to protect.

> 2. For printing from the app, they actually run the computationally expensive slicing algorithm on their servers, so this is totally reasonable to protect. That's an artificial vendor tie-in, and arguably a feature that only involves their client app and their backend. It's understandable if access to their backend is restricted to a subset of their users if that's the business model they wish. Preventing paying cu…

Is it artificial though?

They've bought a machine that executes gcode and that it does (at least to my understanding) regardless of where that gcode comes from.

If you want special secret sauce gcode from the bambu cloud, you need to use the bambu cloud.

Those are not the same thing, so IMO it is legit what they do there, because it's such a clear-cut split. You own the physical thing but not the ecosystem around it.

___

I would of course personally never buy a bambu lab printer, because they're cloud-tied nonsense that was going to behave exactly like that (the split between hw and ecosystem), but other people knew that too and still bought it, because "what a nice ecosystem".

idk. I just don't think that "right to repair" should mean "right to be saved from the consequences of my own bad actions".

Those bad actions continuing to have no real painful consequences (and with that no real learnings + behavioral correction) after all is why the state of tech has become as bleak as it is right now.

And, honestly, if you can afford a bambu premium machine, there's a 97% chance that you could easily shoulder a total write-off. There's also a 97% chance that your ego can't, but that's the main thing causing all the bad things in the world and should've died a long time ago. Approximately post-highschool.

Re: Restore full BambuNetwork support for Bambu Lab printers

#154

Earlier quoted context omitted.

I've wondered the same thing because lately I've noticed a bunch of consumer companies forcing cloud-required models where it's not necessary and many/most users have no need for whatever features cloud connectivity may provide. Yet the companies keep insisting on it even when there's significant user blow back and bad brand PR. When they even bother to comment on "why", the answers never make much sense. When it's c…

>lately it's been going on since the fucking cloud-into-everything fad started ~15 years ago

This. No conspiracy tin foil hat bs, just money. Everything got cloud because investor story time, just like everything has AI now, in every talk I have with either my boss, potential partners and clients its: “where is the AI”? (Source: i am in China). There are a couple of other things that other can maybe highlight, like how every one is blocking Chinese IP’s and vice versa, maybe something on the legislative side also? Not sure. Something something malice/incompetence

Re: Restore full BambuNetwork support for Bambu Lab printers

#155

A lot of the distrust toward Bambu is because they originally announced cloud auth would be required even for printing locally in LAN mode, and only backpedalled on that when they saw the backlash. I'm not sure why their entire domain has been excluded from archive.org but you can still see the original post for now: https://blog.bambulab.com/firmware-update-introducing-new-au... -- Critical Operations That Require A…

>I'm not sure why their entire domain has been excluded from archive.org

Think about why they'd make such a request to archive.org.

Re: Restore full BambuNetwork support for Bambu Lab printers

#156

Earlier quoted context omitted.

> This isn't actually possible This is only true due to a firmware they pushed last year. It's an artificial limit. There's no reason at all a local client couldn't just talk to a local printer without any cloud. Every problem BambuLabs have here is self-inflicted. They could allow simultaneous cloud and local queue management with or without authentication.

[flagged]

> many prefer to break their license agreement because They Really Want It

By "many" do you mean Bambu Lab themselves who are violating the AGPL license of Prusa slicer & predecessors with their non-AGPL, proprietary networking plugin?

They're choosing to violate the license because they don't think anyone will actually dare to sue them, and they're probably right. Ascribing some sort of moral righteousness to Bambu's actions and accusing users of breaking their license is hysterical.

Re: Restore full BambuNetwork support for Bambu Lab printers

#157
post #153

Earlier quoted context omitted.

> 2. For printing from the app, they actually run the computationally expensive slicing algorithm on their servers, so this is totally reasonable to protect. That's an artificial vendor tie-in, and arguably a feature that only involves their client app and their backend. It's understandable if access to their backend is restricted to a subset of their users if that's the business model they wish. Preventing paying cu…

Is it artificial though? They've bought a machine that executes gcode and that it does (at least to my understanding) regardless of where that gcode comes from. If you want special secret sauce gcode from the bambu cloud, you need to use the bambu cloud. Those are not the same thing, so IMO it is legit what they do there, because it's such a clear-cut split. You own the physical thing but not the ecosystem around it.…

Nice post. May I ask what you would buy instead (e.g. for the P1S)?

Re: Restore full BambuNetwork support for Bambu Lab printers

#158
Reminder about the way Ubiquiti does this, as a vendor who wanted to provide users remote access to their own devices behind NAT: Unifi Cloud handles the auth and connection brokerage through a public portal, but you’re then connected straight to your own gear using your web browser (or one of the apps, if you choose). I can even turn all this off if I want to handle the remote access side of it myself.

Other vendors take note !

Re: Restore full BambuNetwork support for Bambu Lab printers

#159
post #12

Earlier quoted context omitted.

That’s an LLM generated website if I’ve ever seen one the explanation for that is here https://youtu.be/II2QF9JwtLc basically louis found that not using AI to design his website drastically reduced the hits he would get from google.

[flagged]

> Vibe coding a slop website drastically increases your bounce rate and reduces trust in your project.

The masses love this. Really! They love their slop like the good little cattle they are. Source: I work in this field with customers, they love the AI-slop corpo-fied website that looks like an app.

Re: Restore full BambuNetwork support for Bambu Lab printers

#160

A lot of the distrust toward Bambu is because they originally announced cloud auth would be required even for printing locally in LAN mode, and only backpedalled on that when they saw the backlash. I'm not sure why their entire domain has been excluded from archive.org but you can still see the original post for now: https://blog.bambulab.com/firmware-update-introducing-new-au... -- Critical Operations That Require A…

> I'm not sure why their entire domain has been excluded from archive.org

Because they have a track record of altering their website, gaslighting the community, and then getting caught through archive.org so they simply blocked it, not realizing that other archives exist and then getting caught again.

They tried to alter their warranty terms and got caught. They altered their ToS which would allow them to block prints until the printer firmware was updated. When the community got upset, they not only backpedaled but altered the associated blog post and accused everyone of spreading baseless misinformation because "it's clearly explained in this [edited, backdated] article".

That's precisely the article you linked to. See the original version:

http://archive.today/2025.01.16-173123/https://blog.bambulab...

Post reply on HN