Apparently some group has broken Bambus encryption.

Apparently, as he claims, the logs reveal not only (further) licensing issues with Bambu, they also apparently send the complete Model you want to print to Bambu, which would be a huge issue for any companies using them.

What do you think?
Anyone ever checked on the size of the logs? Does it make sense that they actually send the whole Model?

/e: clarification, apparently the logs do not get sent to bambu by default on every print (even while in LAN-Mode) as it can be understood here, but all of this info is in the logs you can manually choose to send to Bambu (i.e. in the case of an issue with a print(/er) bambu is reasonably likely to ask for this).

  • arc@lemm.ee
    link
    fedilink
    English
    arrow-up
    1
    ·
    11 months ago

    I have a P1S and I don’t really follow why it is necessary at all to send prints off to the cloud. Yes, it could be useful if printer and PC / app are on separate networks. But if they’re on the same network then they should directly communicate.

  • ERPAdvocate@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    11 months ago

    Man you guys think this is bad? My partner bought a Cricut because they thought it would be good for quilting (fancy vinyl cutter) and its a locked down nightmare.

    Proprietary software with no alternative, cloud upload required to print anything, even over USB connection… Oh and repair-ability, total nightmare with very little access to replacement parts, with Cricut regularly bricking older models as they reach EoL.

    Sorry rant over lol

    • charles@lemmy.ca
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 months ago

      As much as I love the projects I’m able to make with my Cricut, I know I won’t be getting another one when it eventually dies. Cricut’s software and approach to the customers is so awful.

      Wish I’d heard about Silhouette before getting my machine but I’ve definitely learned my lesson now.