• 2 Posts
  • 73 Comments
Joined 8 months ago
cake
Cake day: October 17th, 2025

help-circle



  • A shame one of the alternatives mentioned in the article is down but available via wayback machine. They wrote their own reply after being linked to:

    https://web.archive.org/web/20250905155850/https://belkadan.com/blog/2023/11/GitMounter/

    A few days ago Julia Evans posted this:

    has anyone made a read-only FUSE filesystem for a git repository where every commit is a folder and the folder contains all the files in that commit?

    the idea is that you could just run cd COMMIT_ID and poke around instead of checking out the commit

    and maybe the branches could be symbolic links to the commit folders?

    And I did in fact do something very like that, back when I was playing with FUSE! But I never put it up anywhere cause it had an annoying build process, and didn’t seem to add much, and—

    Well, in any case, Evans asked to see it, so here it is, cleaned up to be a plain old SwiftPM package. It should work on macOS and on Linux as long as you have FUSE (macFUSE or libfuse-dev), libgit2, pkg-config, and Swift installed; on Linux you’ll have to create the mount directory first. (If you run the command and it fails it’ll tell you what path it tried to use.)

    % swift run mount-git /path/to/checkout
    

    By the way, if you don’t know who Julia Evans is, they make blog posts and zines exploring all sorts of software in a way accessible to newbies and veterans alike, all with a lovely sense of discovery and enjoyment. This follow-up post to the original prompt really underscores their approach:

    guys this is such a fun idea I cannot believe people are in the replies trying to explain to me why they think it is impractical

    the whole point of computers is to do impractical things and see what happens

    You should definitely follow them and/or subscribe to their newsfeed. :-)




  • This is the meat of the headline:

    For example, the Anthropic-claimed 181 Firefox exploits ran with the browser sandbox turned off and the FreeBSD exploit transcript “shows substantial human guidance, not autonomy.”

    Additionally, the “‘thousands of severe vulnerabilities’ extrapolates from 198 manually reviewed reports. The Linux kernel bug was found by Opus 4.6, the public model, not Mythos,” Devansh said.

    Another researcher, Davi Ottenheimer, pointed out that the security section (Section 3, pages 47-53) of Anthropic’s 244-page documentation “contains no count of zero-days at all. With no CVE list, no CVSS distribution, no severity bucket, no disclosure timeline, no vendor-confirmed-novel table, no false-positive rate.”

    Ottenheimer likens it to “the ending of the Wizard of Oz, a sorry disappointment about a model weaponizing two bugs that a different model found, in software the vendor had already patched, in a test environment with the browser sandbox and defense-in-depth mitigations stripped out.”










  • For restic:

    1. Every backup is incremental after the first or rather restic makes no distinction because it chunks and dedups the data on the way in so if it’s already in the repo it doesn’t get stored twice.
    2. Restic has customisable ‘forget’ cmd that can do whatever you want
    3. Restic has filtering flags, you can use a gitignore style file also. Many people use a wrapper though like autorestic.
    4. The ghost files are interesting. Restic has nothing special for this. A script that mirrored those files and wrote them all as 0 bytes which restic could then backup would be possible, this would work same for any backup tool.
    5. You get that summary after every restic backup. You can also compare snapshots and mount them all to run your own analysis if you want.
    6. Again if you mount a restic backup you have access to every file and snapshot taken in the repo. You could compare or diff them using usual tools.
    7. There is a ‘exclude-if-present’ option where you can say if a file with the name of your choosing is present do not backup that dir etc