• 0 Posts
  • 40 Comments
Joined 5 个月前
cake
Cake day: 2026年4月7日

help-circle


  • I use windows 11 for work as a linux/hpc admin, as it’s a mostly microsoft shop. Most of my work is done in a wsl almalinux terminal, which works fine.

    The most important things I’ve done to make the rest of it more comfortable all come from the powertoys suite:

    • fancyzones, to replicate a tiling window manager (I really hate floating windows)
    • workspaces, to group apps and window placements so I can easily launch mail/chat/terminal/browser into predetermined places, etc
    • keyboard manager, to set up shortcuts to everything
    • run, for a keyboard-driven launcher

    With all of that, if you squint and don’t think about it too much, it’s almost like a dreadfully slow sway desktop haha







  • You’re interacting with a server managed by someone else - everything that flows through it is ultimately under their control, and you’re trusting them with it. They could log everything, or nothing. Even if storing passwords hashed is the default, an admin can replace any part of the code they want, so they could grab and store raw passwords if they really wanted to, or take over your account and impersonate you, or any number of other unlikely but possible things.

    So use a unique password, and only provide data (your real source ip, your saved posts, views, votes, etc) that you trust the admins of your server with.


  • This is a week-old repo with a 163,000-line initial commit, and the test repo that init was dumped in from is filled with hundreds of claude/codex co-author commits. Regardless of whether it’s to hide the ai co-authoring, it’s shady to obscure a repo’s initial work like that.

    I could be wrong, of course, but this smells like yet another overambitious ai-slop project that’ll get abandoned in a month.








  • I run the immich container stack on a vm with 4GiB memory and 2 cores, with db on local disk and external libraries over smb, and it runs perfectly fine. I offload the machine learning jobs to another sometimes-on machine, sometimes, but don’t really need to unless I’m dumping thousands of new images into the external library at a time and want it all to process quickly.


  • Looks like both of your vms probably have the same mac address - the 172 ip address is likely a self-assigned fallback when the dhcp server replies to the second vm that it can’t give it an address. Double-check and make sure the mac address in each vm’s proxmox network adapter settings match your pfsense dhcp reservations, and let me know if that resolves it.