Live data from Hacker News

Restore full BambuNetwork support for Bambu Lab printers

github.com

141–150 of 344 posts

Re: Restore full BambuNetwork support for Bambu Lab printers

#141
post #115

Earlier quoted context omitted.

The ACCC is more than happy to explain unenforceable terms, if you'd like to do business with Australia. Feel free to consult Steam, Google, Meta and others, if a software license is enough to ignore consumer rights.

I look forward to them sternly changing Bambu Labs' practices!

They will just fine them into oblivion; they are known to fine companies AUD10M to AUD50M for this sort of thing, and from 1st April this year they can now fine up to AUD100M.

Will this mean that Bambu will withdraw from the Australian market? Possibly maybe probably, but the ACCC takes a very hard stance against bait and switch.

Re: Restore full BambuNetwork support for Bambu Lab printers

#143
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."; but only for a subset of the potential audience.

This is something I learnt early in my start up career, "You are not your customer"; what you value and what your customers value may not be the same.

Re: Restore full BambuNetwork support for Bambu Lab printers

#144

[flagged]

> whether users can keep using hardware they already own without depending on a vendor cloud path.

That’s a complete misunderstanding of the current state of affairs. Bambu didn’t take away local network support, and you can use any Bambu printer without any cloud or internet connection.

What you can’t do is use a 3rd party slicer with their cloud servers…

Re: Restore full BambuNetwork support for Bambu Lab printers

#145

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]

The AGPL covers the line of code that includes the user agent, the only "security" bambu uses.

By attempting to stop users from using their AGPL code they are behaving illegally.

Re: Restore full BambuNetwork support for Bambu Lab printers

#146

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.

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.

Re: Restore full BambuNetwork support for Bambu Lab printers

#147
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.…

> (...) I don't see the current system as particularly bad and find the appetite to restore "untrustworthy" cloud functionality a bit amusing.

This is a very dubious opinion to hold. Taking your claim about local mode at face value, there is absolutely no reason to disable monitoring when working on LAN mode. You need to go way out of your way to implement that restriction so that it works differently when the thing phones home or not. You are free to criticize implementation decisions that you feel make it "untrustworthy" but those are trivial to address if you think about it.

I really recommend you to reassess your whole philosophical stance on having corporations prevent you from using what you bought and paid for.

Re: Restore full BambuNetwork support for Bambu Lab printers

#148
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.…

Personally I'd be fine with the LAN mode assuming I don't have to use their cloud even once.

Re: Restore full BambuNetwork support for Bambu Lab printers

#150
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.…

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 customers from using the hardware they bought and paid for by imposing artificial restrictions is not cool.

Post reply on HN