• nick@midwest.social
    link
    fedilink
    arrow-up
    14
    ·
    14 days ago

    I’ve been holding off on Bambu mostly because i don’t want my data being sent to Chinese cloud servers.

    Guess I was right.

  • Dagamant@lemmy.world
    link
    fedilink
    arrow-up
    8
    ·
    14 days ago

    I was planning to get a bamboo, was saving up for it. Money will go to a resin printer from someone else now.

  • shoulderoforion@fedia.io
    link
    fedilink
    arrow-up
    7
    ·
    14 days ago

    Repair advocate Louis Rossmann, noting Bambu’s altered original blog post, uploaded a video soon after, “Bambu’s Gaslighting Masterclass: Denying their own documented restrictions.” Rossmann also took aim at Bambu’s Terms of Use, suggesting that the company was asking buyers to trust that Bambu wouldn’t enact restrictive policies they otherwise wrote into their user agreements.

  • 5in1k@lemm.ee
    link
    fedilink
    arrow-up
    1
    ·
    13 days ago

    Wow, fuck Bambu. I have several printers and I will never ever use them.

  • nate3d@lemmy.world
    link
    fedilink
    arrow-up
    2
    arrow-down
    9
    ·
    14 days ago

    Nobody has read the full release notes and is making this out to be a much bigger deal than it is.

    Firstly, they’re leaving the existing functionality in place and you just have to enable it and approve a prompt that you’re responsible for your network security.

    Secondly, they’re providing a software solution to allow any gcode to be sent to the printer and any of the many 3rd party slicer vendors are welcome to incorporate it.

    Locking down a cloud connected product with proper authentication methods is a good idea but their initial press release butchered the details and led to the community uproar.