Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Restore full BambuNetwork support for Bambu Lab printers

github.com

Post reply on HN
Print view View original

221–230 of 344 posts

Re: Restore full BambuNetwork support for Bambu Lab printers

#221

Post by jijijijij »

imhoguy wrote: post #187
shuv1337 wrote: post #173

Earlier quoted context omitted.

it honestly depends on your budget. prusa is definitely overpriced for what you get. but, i bought one anyway specifically because of their stance on OSS, and this kind of bullshit the bambu is pulling. even though bambu objectively has a better or at least equal product for significantly less money.

Less money because you get significantly closed product likely susbidised by state to dominate the open competition.

Yeah, overpriced is a big word when the competition is likely not operating sustainable due to subsidies and a lot of investment cash to burn for market capture.

Eg. they are paying random people to host their models exclusively on MakerWorld (where the CCP tells you what's okay to print; try searching for anything 'Jinping'...). They are obviously pouring enormous amounts of cash into marketing on social media, especially YouTube (a lot of large maker channels became full-on advertisement platforms).

Their expenses are evidently enormous. There is no way they are running sustainable. It's a long con.

Re: Restore full BambuNetwork support for Bambu Lab printers

#222

Post by chopin »

p0w3n3d wrote: post #218
amelius wrote: post #206

Earlier quoted context omitted.

I always put printers (2d and 3d) behind a firewall so they cannot reach the internet. This prevents auto-updates and surprises like disappearing functionality.

that's what I had in my mind - I want to switch back to HP printer because the Brother I bought has inferior picture printing quality, but I am scared of any software update, so I guess I'll connect it to old linux machine and serve via CUPS

I just don't allow outbound connections for our HP printer.

Re: Restore full BambuNetwork support for Bambu Lab printers

#223

Post by joshuaissac »

barnabee wrote: post #181
parasubvert wrote: post #90

Earlier quoted context omitted.

[flagged]

They have no rights to prevent people modifying and using AGPL software however they want. They should have no rights to control how people use hardware they bought. ToS for hardware should simply be unenforceable. People should have full rights to adversarial interoperability, even if it means modifying proprietary software or hardware. It always surprises me when people (on this site particularly) are more interest…

> They have no rights to prevent people modifying and using AGPL software however they want.

AGPL software can be used and modified within the limits of what the AGPL permits. People can do that with their Bambu software running on their own hardware.

That does not extend to using their proprietary BambuNetwork cloud service (somebody else's computer). The AGPL specifically mentions this scenario in section 6. There are open source alternatives to that like the third-party Bambu-Farm and bambuddy that people can self host instead.

Interestingly, Bambu's own initial approach to the AGPL was more in line with "modifying and using AGPL software however they want" (and potentially violating their section 6 obligations), until customer backlash forced them to adhere to the terms of the licence.

Re: Restore full BambuNetwork support for Bambu Lab printers

#224

Post by [deleted] »

bri3d wrote: 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.…

[deleted]

Re: Restore full BambuNetwork support for Bambu Lab printers

#225

Post by bayindirh »

9cb14c1ec0 wrote: post #213
jamesnorden wrote: post #211

Earlier quoted context omitted.

I've been bitten by an HP printer auto updating and my aftermarket ink suddenly not being acceptable. Never buying HP again after that.

I once updated my Epson, and it started rejecting aftermarket ink. Fortunately there is a way to downgrade the firmware. Never buying a cartridge based inkjet printer again.

If you don't care about ink quality, then aftermarket ink is fine.

However, if you want your pictures to last 10+ years under the sun, or being able to read what you have printed after some time, getting the genuine ink is the way.

People think ink is simple. It is not.

Anybody thinking otherwise, some points of pondering:

     - Why Xerox and HP run their own toner/ink labs to formulate their own ink down to molecule level?
     - Look at your standard disposable pens. Gel, liquid, dye, pigment, alcohol/water/oil based, UV resistant or not... It's a hard chemical problem.
     - Similarly even something bland like fountain pen ink has hundreds of different formulations. Not colors, formulations. Washable to cellulose reactive and everything in between...
It's not dyed drinking water.

Lastly, I'm not against people using 3rd party ink at any level. I just want to point out that not every ink cartridge is created equal.

Re: Restore full BambuNetwork support for Bambu Lab printers

#226

Post by mightyham »

bri3d wrote: 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.…

> This isn't actually possible

Bambu absolutely could create a system where their printers both communicate with the cloud and local devices, they just don't want to do the difficult software engineering necessary because it is difficult. This is not theoretical either; I work on production devices with hybrid cloud and local functionality. Engineering around a zero-trust threat model (as in you assume the user can and will tamper with the device) is completely doable.

For instance, using a push-only RPC model where only the cloud can initiate a request is one zero-trust strategy that can be used for ensuring a predictable network load on cloud infrastructure, which seems to be their main concern.

Re: Restore full BambuNetwork support for Bambu Lab printers

#227

Post by MSFT_Edging »

p0w3n3d wrote: post #215
basilikum wrote: post #205

It's maddening that quite a few people are jumping to defend Bambu here. Principally if you sell a device with a certain functionality and you later modify that device later to remove that functionality that is called theft. It does not matter the slightest bit whether you break into someone's house to physically alter the device or whether you remotely install a malicious software update to do that. But what's even…

> later modify that device later to remove that functionality that is called theft. I've always been told it's called business. But I fully agree with you. Just wanted to note that this is the current business model both with hardware and software

This is why the fight/loss for open computing is so important.

Without the ability to run your own code, this will be everywhere and everything.

Without some counter force of open source pushing back and offering alternatives, we'll be putting tokens in a machine to check your email. Reading email will cost 4 tokens and you'll only be able to buy them in groups of 7.

Re: Restore full BambuNetwork support for Bambu Lab printers

#228

Post by johnsea »

hypfer wrote: post #203
johnsea wrote: post #157

Earlier quoted context omitted.

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

Uh, not really. I wouldn't buy an alternative to a P1S, because only the P1S is the best at being the P1S. (Whatever that might entail) Instead, I'd look at things from the perspective of "what do I want?" and not "What does the market offer? Okay, I want that thing. But no, I want an alternative to it that is that thing but without downside" Letting a brand set your frame of reference is the first step into total de…

Thanks for your reply. Only used PLA so far. But later I'll need "engineering parts", Nylon/PA12 or something like this. Strong, water and UV resistant, outdoor.

It shouldn't be too complicated and not too expensive. E.g. while the Prusa Core One+ seemed nice (from a superficial look) it costs more than I wanted to spend. P1S came out as the best (barely) adequate printer for what I thought I would need when I looked at it. But it's difficult to say if you are a beginner and basically have no idea...

Re: Restore full BambuNetwork support for Bambu Lab printers

#229

Post by RobMurray »

mschulkind wrote: post #103
asveikau wrote: post #83

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.

If you turn on LAN mode, it acts exactly like every other printer. You can print directly to it from any slicer over your LAN, or dump gcode on the SD card directly.

not just lan mode, you have to enable developer mode, which blocks cloud access entirely so you lose advertised functionality.

Re: Restore full BambuNetwork support for Bambu Lab printers

#230

Post by bigiain »

joshuaissac wrote: post #223
barnabee wrote: post #181

Earlier quoted context omitted.

They have no rights to prevent people modifying and using AGPL software however they want. They should have no rights to control how people use hardware they bought. ToS for hardware should simply be unenforceable. People should have full rights to adversarial interoperability, even if it means modifying proprietary software or hardware. It always surprises me when people (on this site particularly) are more interest…

> They have no rights to prevent people modifying and using AGPL software however they want. AGPL software can be used and modified within the limits of what the AGPL permits. People can do that with their Bambu software running on their own hardware. That does not extend to using their proprietary BambuNetwork cloud service (somebody else's computer). The AGPL specifically mentions this scenario in section 6. There…

Id Louis Rossman's YouTube rant is correct, nobody involved here modified the AGPLK software. They just used a version of the AGPL software from before Bambu Labs changed the auth code.

While I agree that the AGPL does not grant users any rights to Bambu's cloud service, sending DCMA nastygrams to people hosting copies on old versions of their software isn't the right (or even legal) way to enforce that. And since Bambu choose to build their products and software stack on pre existing AGPL code, they've backed themselves into a corner a bit with other options. They can add new auth to new versions of the code (which is stringer than just hardcoded useragent-like strings in the code) but they'll then have to release the source code to their new version - exactly like the original authors who chose the AGPL intended.

Post reply on HN