I joined Lemmy back in 2020 and have been using it as @[email protected] until somewhere in 2023 when I switched to lemmy.world. I’m interested in systemd/Linux, FOSS, and Selfhosting.

  • 200 Posts
  • 917 Comments
Joined 3 years ago
cake
Cake day: June 10th, 2023

help-circle









  • I checked the repo but there’s no code? Just some HTML etc.
    It seems like they just plan for this thing to exist but it doesn’t actually exist yet?

    EDIT: Their explanation:

    This repository is currently in its early setup phase.

    At the moment, the repository mainly contains project scaffolding, policy files, and the initial project direction. Firmware sources, board support, build instructions, and flashing guidance are still being prepared.

    That means zgm is early, but it is intentionally early in public. The goal is not to wait until everything is finished before opening the door. The goal is to make the long-term direction visible and let the project grow into a useful open firmware platform in the open.

    I’m not sure if that means that they still have to make it, or that they just have to finish it before publishing it?








  • Huggingface actually had to use an open model to analyze the attack because the guardrails of commerical API’s caused issues.

    When we started the log analysis, we first used frontier models behind commercial APIs. This did not work: the analysis requires submitting large volumes of real attack commands, exploit payloads, and C2 artifacts, and these requests were blocked by the providers’ safety guardrails, which cannot distinguish an incident responder from an attacker. We ran the forensic analysis instead on GLM 5.2, an open-weight model, on our own infrastructure. This had a second benefit: no attacker data, and none of the credentials it referenced, left our environment.

    Security incident disclosure — July 2026