• 0 posts
  • 13 comments
Joined 1 year ago
Cake day: February 15th, 2025
  • I’m just speaking for me, as a senior software architect with a decade of experience:

    • Solving problems is the fun part.
    • Designing a good architecture is the fun part.
    • Making sure the project is high quality, clean and elegant is the fun part.

    Typing all of that out (for momths and years mind you) is the boring part. For me typing is what comes after thinking. My brain goes into that adhd state where I have to pay enough attention to type the code, but not enough to be engaged. I’m getting so bored while typing code, I can’t sit still for 30 seconds. Time gets slow. I get uncomfortable. I keep being distracted. I start thinking about something else and start making stupid mistakes.

    I much rather explain my vision, architecture and solution in a detailed text (which helps me think about it in more detai) and then do hours of code review (guess I’m weird for liking that) and “thats wrong, redo it” until I’m happy then type all of that out myself.

    There is a lot I hate about “AI”, but sparing me from that rage-inducing manual slave labour is not one of those.

    If I could hire a human to do the typing I’d do it. But an LLM subscription is so much cheaper than even the worst apprentice.

  • OP asked:

    How can you grant access to an account to write remotely, but also protect the data from this account?

    So I was thinking that the account should not be able to delete the filesystem in an unrecoverable way. Like overriding the current fs with random data or an encrypted fs and filling it etc.

    Like I said on a Hetzner storage box, multiple users get access to the same system, but each one only has file editing commands, not fs editing and they can only access their assigned directory. So if the system does scheduled snapshots (outside of that user’s scope of access) there is no way for a user to delete the files beyond recoverability. (no matter if their own files or other users files).

    The user can still delete their own data. But because the fs is cow with snapshots (like btrfs) and they can not touch that, the data can be recovered easily.

  • I think you could do it somewhat like hetzner does for their storage boxes. You get an account that has read and write access to a directory and nothing outside. The accound can only run a limited set of commands, like ls, cat, nano, rsync etc. but has no access to commands that modify the filesystem.

    Then you can use a copy on write fs like btrfs and make scheduled staggered snapshots.

    I usually do 1x per year, 1x per month of current year, 4 per week of current montg, 7 per day in current week.

    I have no clue what they use to limit the user accounts like that btw. but maybe that gives you a new jump off point for further research.

  • Must be difficult if you judge an OS based on whether other users of it are nice online… how do you get anything done?

    Sarcasm aside, I used to mod ad artix community back when I was using it and it was 99% support requests that have already been answered somewhere else… so like most other linux communities. And I’ve seen my share of toxic people in most of them. I mean, maybe it changed for the worst from when I last experienced it, but then, just don’t participate in the community?

    The OS itself is alright. Pretty much same as arch, but you hage to tinker more… It gets somewhat annoying writing your own init/unit files for each app that needs systemd, thats why I switched back to plain old arch. I can see the tradeoff being worth it if you dislike the systemd direction/philosophy enough.

    And I hate that artix puts it’s flair on KDE, just give me the vanilla experience, I don’t want to manually remove your ugly theme.

  • The problem is that your desktop environment’s shortcut handler intercepts Alt+V before KeePassXC ever sees it, so the internal keybinding never fires. And when pgrep finds the process running, your command simply does nothing.

    The fix is to use KeePassXC’s --auto-type CLI flag, which sends the auto-type signal to a running instance:

    Command for your custom shortcut (Alt+V):

    bash -c 'pgrep -x keepassxc > /dev/null && keepassxc --auto-type || keepassxc'
    

    Not sure how keepass behaves though. Maybe you don’t need the condition at all and can just run keepassxc --auto-type from the shortcut.