this post was submitted on 20 Jan 2025
47 points (89.8% liked)

3DPrinting

15976 readers
709 users here now

3DPrinting is a place where makers of all skill levels and walks of life can learn about and discuss 3D printing and development of 3D printed parts and devices.

The r/functionalprint community is now located at: or [email protected]

There are CAD communities available at: [email protected] or [email protected]

Rules

If you need an easy way to host pictures, https://catbox.moe may be an option. Be ethical about what you post and donate if you are able or use this a lot. It is just an individual hosting content, not a company. The image embedding syntax for Lemmy is ![](URL)

Moderation policy: Light, mostly invisible

founded 2 years ago
MODERATORS
 

tl;dr: "Fuck You, we're right, but here's a crumb from the table" but in PR-speak.

There'll be a Lan-Mode (still requiring Bambu Connect), and a Dev-Mode (which will continue MQTT, live steam and FTP).

The Writing continues to be on the wall.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 14 points 18 hours ago (1 children)

The Security argument doesn't hold water when you're pushed toward the cloud use for transmitting data over your own network cable would suffice.

Define APIs and API keys (local and cloud).
Instant safe communication, local and/or cloud.

[–] [email protected] 1 points 17 hours ago

But don't they currently allow local connections and also use them if the printer is running in cloud mode? I would assume if the printer can be "seen" by your machine locally, Bambu Studio would connect locally for some of its data transfer? Regardless of printer configuration (LAN only or Cloud) it still has its local ports open, which currently can be used by e.g. Home Assistant without any cloud connection. This is nice, but at the same time can be a security risk, as any local malware might also send commands. So a way to secure the local connections is definitely needed.

API keys would be nice for any type of connection, but it's something they'd need to implement, including a way to request/revoke them from either your Bambu account (cloud again, not preferred by the open source community) or directly from the printer (might be a hassle to use with the P1S' small screen). Instead they decided to go full-throttle by using some form of certificate authentication, possibly using per-device and per-account certs in the future, that might be generated locally and signed by their endpoints using your Bambu account.