[–] 45 points 1 month ago* (3 children)

posted it. Got dunked on for AI slop

101 upvotes and 14 downvotes... dunked?

Anyway, I stopped reading and downvoted after the

Ipso facto, for all the AI “Akshually” pedants, I’ve tagged this as AIP. Politely go fuck yourselves :)

typing the word "politely" or a smiley doesn't make a very rude remark any less rude.

Moreover, splitting the community into a pro-AI faction and an anti-AI one isn't healthy (for the community, whether it's healthy for you is a can of worms that I don't want to open right here and now) and ridiculing the other "faction" can only radicalize things and we already have more than enough of that, both in lemmy and, sadly, also IRL.

So, personally, I donwvoted your post, not your project.

  • source
  • [–] 31 points 1 month ago (19 children)

    What risk are you trying to mitigate, specifically?

    If it's the CA taking over your site, control over your CA specifically doesn't really give any advantage to an attacker (they would have to hijack traffic and provide a new certificate - nobody will notice if the certificate is from a different CA).

    Note that your CA cannot decrypt the exchanges between your server and its clients.

  • source
  • [–] 4 points 1 month ago (1 child)
    FILENAME='birthday_0' $(cat command_ffmpeg_SYNCAUD)  
    

    cat prints out a file without altering it's contents.

    If it's important to keep the commands in a separate file, you could use sed to find/replace, or use eval, or use some external template engine (lookup "bash expand variables in file").

    What you probably want to do instead, I assume, is to replace the external files with regular bash variables:

    filename="some-file"
    command="ffmpg -i ${filename}.mpg -bla -blabla ${filename}.mkv"
    echo "$command"
    
  • source
  • [–] 3 points 1 month ago* (last edited 1 month ago) (2 children)

    IDK what makes Eric Bailey prefer a cooperative to a non-profit, the article doesn't explain it.

    Unlike corporations, co-ops don’t have to be motivated by profit. Not needing to focus growth at all costs means co-ops can instead prioritize and incentivise things like preservation and cultivation. It is also a successful model of operation [links to a page titled "employee ownership"], one that even already exists and flourishes in the tech space [links to a page about a specific software consultancy coop that doesn't publish a knowledge website].

    I might be jumping the gun here, but... it would seem he doesn't really know what the point of a cooperative is?

  • source
  • [–] 9 points 1 month ago (4 children)

    It's on line 3: nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable".

    Change it to github:NixOS/nixpkgs/nixos-26.05 for the latest nixos stable (which is not rolling, meaning you'll have to update the URL every now and then)

  • source
  •  

    I'll copy the whole announcement here for those who don't want to click:

    I regret to inform everyone that my copy of QBittorrent escaped its sandbox last night and downloaded a whole bunch of content owned by major corporations, and then my copy of Jellyfin broke containment and added those unfortunately-downloaded media files to its various libraries. I'm conducting an internal investigation to figure out how this happened, which will involve consuming these media files until the answers become apparent. Thank you for your cooperation during this trying time.

     

    I'm looking for a forgejo cli (something similar to gh for github or glab for gitlab - neither of which I've ever used).

    I found one named forgejo-cli and another named fgj but, from a quick look at the source, both seem to save my API key in a plaintext file, which... I just find unacceptable (and, frankly, quite dumb).

    Do you know of any others?

     

    Here it is https://codeberg.org/gmg/concoctions/src/branch/main/sh-scripts/nixos-rebuild

    (if you try it and find any bugs, please let me know)

    edit: I didn't realize the screenshot shows just instead of nixos-rebuild... that runs a script ("recipe") that calls nixos-rebuild so the output shown is from the (wrapped) nixos-rebuild

     

    I'm trying to get my scripts to have precedence over the home manager stuff.

    Do you happen to know how to do that?

    (not sure it's relevant, but I'm using home-manager in tumbleweed, not nixos)


    edit:

    Thanks for the replies - I finally got time to investigate this properly so here's a few notes (hopefully useful for someone somehow).

    ~/.nix-profile/bin is added (prepended) to the path by the files in /nix/var/nix/profiles/default/etc/profile.d/, sourced every time my shell (fish, but it should be the same for others) starts (rg -L nix/profiles /etc 2> /dev/null for how they are sourced).

    The path I set in homemanager (via home.sessionPath, which is added (prepended) to home.sessionSearchVariables.PATH) ends up in .nix-profile/etc/profile.d/hm-session-vars.sh, which is sourced via ~/.profile once per session (I think? certainly not when I start fish or bash). This may be due to how I installed home-manager... I don't recall.

    So... the solution is to set the path again in my shell (possibly via programs.fish.shellInitLast - I din't check yet).

     

    I'd like to give my users some private network storage (private from me, ie. something encrypted at rest with keys that root cannot obtain).

    Do you have any recommendations?

    Ideally, it should be something where files are only decrypted on the client, but server-side decryption would be acceptable too as long as the server doesn't save the decryption keys to disk.

    Before someone suggests that, I know I could just put lucks-encrypted disk images on the NAS, but I'd like the whole thing to have decent performance (the idea is to allow people to store their photos/videos, so some may have several GB of files).


    edit:

    Thanks everyone for your comments!

    TLDR: cryfs

    Turns out I was looking at the problem from the wrong point of view: I was looking at sftpgo and wondering what I could do on the server side, but you made me realise this is really a client issue (and a solved one at that).

    Here's a few notes after investigating the matter:

    • The use case is exactly the same as using client-side encryption with cloud storage (dropbox and those other things we self-hoster never use).
    • As an admin I don't have to do anything to support this use case, except maybe guiding my users in choosing what solution to adopt.
    • Most of the solutions (possibly all except cryfs?) encrypt file names and contents, leaking the directory structure and file size (meaning I could pretty much guess if they are storing their photos or... unsavory movies).
    • F-droid has an Android app (called DroidFS) that support gocryptfs and cryfs

    I'll recommend my users try cryfs before any other solution. Others that may be worth it looking at (in order): gocryptfs, cryptomator, securefs.

    I'll recommend my users to avoid cryptomator if possible, despite its popularity: it's one of those commecrial open source projects with arbitrary limitations (5 seats, whatever that means) and may have nag screens or require people to migrate to some fork in the future.

    ecryptfs is to be avoid at all costs, as it seems unamaintaned.

    view more: next ›