• 1 Post
  • 21 Comments
Joined 3 years ago
cake
Cake day: July 1st, 2023

help-circle




  • Klipper is a different beast but once you get it going it’s leaps and bounds ahead.

    No more compiling and editing firmware. Since the Klipper firmware itself is built and deployed to the board so the logic of what features, pins, etc can be controlled by your pi.

    E.g. the board is no longer the “brains” of the printer but the brain stem. Where the brain (the pi) tells it on pin A “tell this stepper motor to turn this”, on pin J “tell the heater to cycle on” etc.

    Basically you download Klipper, look at a printer.cfg for the board you have, and then just use that as a starting point.

    Here’s the generic printer.cfg for your new board

    https://github.com/Klipper3d/klipper/blob/master/config/generic-creality-v4.2.7.cfg

    The real power comes from having the option to use macros for things like START_PRINT and END_PRINT.

    For example, when I added a Nevermore fan on an skr mini e3v3 board I just had to wire it, find the “pins for the plug” on the board and then add the necessary config change.

    Didn’t work? Comment it out and restart firmware and you’re no worse than it not being there. Adjust, restart, and go.

    So where I’d avoid a marlin update because of the hassle of building and updating I now just check for updates, ssh in and build it with a command and update the board over USB.

    And that’s just to update the Klipper firmware on the board for whatever fixes/changes are needed for Klipper. For things like new macros or existing items changed around you just update the config and “restart” and it does the rest.

    The only thing that you lose with an ender is the screen. Their screens aren’t dumb… they have their own weird firmware. Personally I just use the website and now the moonraker mobile app to control everything and I don’t bother with a screen at all.






  • I love the internet archive but yeah, there was just no way this wasn’t going to backfire. And by handling things the way they did they damaged the reasonable defense of archivist (not only for themselves) because publishers and others often cite that archival and backups are just “pseudonyms” “synonymous” for piracy.

    They aren’t but the way this was handled made it impossible for them to argue otherwise and it also creates a legal precedent for lawsuits and judgments by publishers against others who are doing such work.






  • I wonder if they’re doing that to reduce the write cycles on the cells and since they’re “encrypting” the contents of the cells they figure the overall IO flag of the data being deleted is “good enough”.

    So, in a perfect world, when you wipe the phone it’s basically just trashing the encryption key and so it’s useless data.

    That’s all assuming that the encryption method/keys are foolproof which is always a bad bet.

    And, this here makes me wonder how effective that is.

    And a person claimed in a later post that “around 300” of their old pictures, some of which were “revealing,” appeared on an iPad they’d wiped per Apple’s guidelines and sold to a friend.

    That’s a huge issue. Not just for photos but also files for sensitive data, secrets, etc. this, if true, is a massive issue overall since it even happening at all shouldn’t be possible.







  • There’s a real risk of survivorship bias here. Somebody asking about a car gets that and thinks nothing of it. A privacy minded person, however, would find it odd. And being the kind of person concerned about what could have been the cause considered the prior conversation.

    I’m not saying its an unreasonable concern or technically not feasible. It’s just not how the LLM’s tend to work.

    Id consider it more likely to be a bug, or general inquiries like you said, or that SO had a bunch of documents locally that reference privacy or browsing history (anytime really) that MS could have used as a kind of “here’s more about the person asking you a question”