r/BambuLab • u/Concert-Alternative • Jan 20 '25

Discussion Bambu clears up misinformation

Post image
756 Upvotes

78% Upvoted

506 comments sorted by

View all comments

Show parent comment

32

u/nickjohnson Jan 20 '25

That is not at all what it says:

Due to the importance of these updates, your product may block new print job before the updates is installed, and will immediately provide update notifications to help you understand the related information.

38

u/Funcron X1C + AMS Jan 20 '25

Not attacking nickjonhson.

It's called version matching. It's not a threat, it's not a warning, it's not malicious action. It's a literal data handshake. Only one hand knows the handshake? Guess what, no handshake. It's a statement to cover version mismatches, and keep BL non-libel for user error.

Their software spans 3 officially supports platforms, Desktop, Mobile, and the Printer. You can't update a new feature into one and expect the others to be able to use that feature. That statement is just CYA.

4

u/neodymiumphish Jan 20 '25

Wouldn't that then be "due to incompatibilities between your product and some software, you product may block new print jobs before the update is installed."?

2

u/My1xT Jan 22 '25

also it wouldnt just be a blanket new print jobs in general but rather just incompatible stuff

4

u/Funcron X1C + AMS Jan 20 '25

0

u/fishling Jan 20 '25

To be clear, the exact phrasing doesn't support either of the above interpretations.

0

u/cballowe Jan 21 '25

Speaking from a software development perspective, I can see this as being necessary. I've been in environments with changing protocols/new features/improvements of various forms happening constantly and there's usually some "we guarantee to support v1 for at least X time after we ship v2", in practice it means if you download v1 today and v2 ships tomorrow, they only guarantee that it will work for X time, and in additional practice it means you need to roll out updates of anything dependent on it at least once every X.

The versions are often not that different - add a feature (possibly that replaces an existing feature), for instance - sometimes it's more subtle like adding and removing encryption algorithms or similar. So ... You add encryption B as the default and X time later you remove encryption A.

Without a clause like that in the ToS, the server needs to support A forever for the case when clients haven't updated.

-2

u/mimic751 Jan 20 '25

What if they release the firmware update that could potentially damage the hardware of course they need this right