[–] 28 points 1 week ago (1 child)

Not saying fixed bugs aren't good, I'm just so fed up with this marketing-driven fearmongering. They're overhyping every god damn bug they can because they know most people won't know how bad it actually is. They do worse security practices than most homelab enthusiasts and then prophesize the AIpocalypse because their linear algebra "escaped" (the door was wide open). Hell, they don't even manage to understand proper bug disclosure practices. They're playing the "Social" Media outrage game on a global scale to drive sales and everyone is suffering for it. I'm so, SO done with all of this bullshit. When the bubble finally crashes I'll throw a raging party with blackjack and hookers.

  • source
  • parent
  • context
  • [–] 4 points 1 week ago (3 children)

    For server crashes, but not for RCEs. The only proven case of this I know of was with a specifically prepared PHP instance as honeypot that had an optimal attack surface and was done by Perplexity (another AI company). Outside of that there's no credible large-scale RCE exploitation that's any worse than the bugs that get fixed on a daily basis. It doesn't even remotely justify the panic and media frenzy.

    it was merely dangerously exploited by AI bros.

  • source
  • parent
  • context
  • [–] 101 points 1 week ago (8 children)

    This is shady as hell. It's an AI company again (Anthropic), they do not follow rules of responsible disclosure (again), it's a race condition again, they do not provide a proof of concept (obviously since they shouldn't talk about it at all until after we got the patch) but instead create big media fuzz about their glorious AI… hell, they do not even tell us the kernel versions or anything.

    If we find out eventually that you have to disable default mitigations for this to become dangerous (like the stunt they did with Firefox) it's too late, the media won't give a shit anymore. Like we just had with PHP - huge panic, enormous media circus, barely any real-life consequences in the end and the responsible disclosure process being a total mess to blow it up even more.

    Honestly, every time I see some AI company hyping yet another huge and super dangerous exploit only their superior AI found "after X years of nobody seeing it" I now expect a nothingburger.

    We're probably fine, nothing out of the ordinary to see here.

  • source
  •  

    I'm currently looking into upgrading one of my old printers with a filament cutter since filament ramming gives me headaches. It's supposed to be controlled by the printer but I don't find a clear answer what kind of servo or actuator to best use (which is both lightweight but also strong enough). I still have some servo pins available on my board, no stepper though.

    Can someone give me a hint what to look for?

     

    I'm somewhat puzzled which settings I need to look at in PrusaSlicer to solve those thin slits between perimeters. I've dialed in the flowrate optimally for dimensional correctness and 245°C (PETG) works really well for both flow and overhangs.

    At first I thought of extrusion width, but that also increases the distance between each line. Raising the flowrate closes them, but also makes the printed parts grow in each dimension outside if the intended size.

    Where am I missing something? Which settings do I need to adjust to not screw up everything else?

    EDIT: It's not just corners!

    Close-up of a 3D printed part on the build plate currently in progress of being printed. Two arrows point at locations where the perimeter lines aren't attached to each other.
     

    I'm trying to find the reason why my bigger printer suddenly decided to constantly create blockages as high as the PTFE tube in the cooling block (so a little bit above the heatbreak).

    It's an older V6 head. The discolouring on the heating block comes from the single time the nozzle came lose and PETG was pressed through the threads upwards, that was a year ago though. I didn't change anything, from one day to another it just decided that (for both PLA and PETG) it'll now stop working properly.

    Waiting on a stronger cooling fan (strongest Sunon I could find, the one with 9000rpm). Other than that I'm just confused why this suddenly happens.

    Close-up of some dirty parts of a 3D printer's print head. There's the nozzle, the heating block (where the nozzle sits in, fitted with a heating element and a temperature sensor), the heatbreak (a thin metal tube connecting the heating block with a cooling block have a controllable melting point for the plastic) and the circular cooling block. The parts are rather dirty and discoloured.
     

    I'm thinkin about getting one of those ruby nozzles for my printers to basically be able to print anything without ever having to worry about a degrading nozzle. I've seen quite a few videos about it, but I still don't know two things:

    • Given the surrounding material is brass and only the tip being out of ruby, doesn't the filament path where the molten filament gets pushed through still wear out over time (heavily so with CF or GF filament)?

    And also

    • How good are the cheaper ones, specifically the "DUROZZLE" one (since that's the one I could find that's 0.6mm and cheap)?
    Screenshot of the german Amazon shop showing a "Volcano Ruby-Nozzle 0.6mm" from DUROZZLE
    view more: next ›