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.

  • 428 Posts
  • 2.13K Comments
Joined 3 years ago
cake
Cake day: June 10th, 2023

help-circle


  • I just followed the opt out link and they’re making you open a public issue with a Markdown list with all your repositories you want removed.

    Surely there has to be a better way to do this (probably the point).

    Also why are they storing 4.71 TB in a Git repo? How are they going to deal with removal requests?

    EDIT: It seems like they’re manually responding to the issues, wtf? There’s a perfectly fine GitHub auth system that they could use to verify everyone’s GitHub account / repository ownership

    EDIT 2: This is apperently a collaboration between Hugging Face and ServiceNow, why is my companies IT ticketing system scraping all of GitHub?






  • Too many people gloss over the fact how insane it is that some people genuinely believe non-believers burn forever in a magic post death torture world. Like how can someone think that while talking with someone, and be like, aw sucks for them, glad I submit to this ancient chain email creepypasta.

    It still baffles me when I realize someone thinks like that.












  • 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