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

  • 3 posts
  • 11 comments
Joined 3 years ago
Cake day: June 10th, 2023
  • 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

  • From my personal experience, most companies don’t look at the benchmarks and simply buy “AI” from a company based on their perception of that company.

    All the Chinese models are scary and “dangerous”, Grok too (but for slightly more legitimate reasons), Meta that’s Facebook and everyone knows they’re bad at privacy (even your boss), so they end up choosing Microsoft’s AI, OpenAI, or Anthropic.

cross-posted from: https://lemmy.world/post/35221872

I often get reports with just “Breaks Community Rules” and no additional context. This is because Voyager automatically sets the mandatory report reason as “Breaks Community Rules” without actually adding a reason. However, it’s often not clear why a post would break those rules and which rule would be broken.