[object Object]

Autocorrect hates me, I am sorry.

  • 0 Posts
  • 345 Comments
Joined 1 year ago
cake
Cake day: July 20th, 2025

help-circle


  • Just a heads up, I pulled the drive stats from Backblaze’s drive survey, for most brands failure rates accelerate at 4-5 years.

    At that point Hitachi, Toshiba, and Seagate all increased in failures. Western Digital didn’t, except for their 2014 batch that immediately dropped off.

    Western Digital post 2020 are the most reliable drives.

    Hitachi, Toshiba and Seagate seem to hit a cliff around 2-5 years now, but that only kills about 10% of their drives, so with replication you’re probably fine, just make sure to mix drives so you don’t get correlated failures.



  • It is, usb4 and thunderbolt are (as I understand) extensions of the pcie bus or something, so they do require escalated security permissions in all operating systems.

    macOS desktops auto approve, laptops request permission, and windows does its own approval.

    Linux requires approval until you set your computer’s security settings, but I think it only approves on user level security by default (hence the gnome issue).

    I’m also not an expert, so if your device shows up in boltctl as approved it could very well be a different issue. I’ve only done this on amd.









  • I hope this doesn’t come off as too harsh, but the text reads as very AI generated, and I think if you rewrote the main text you could do a much better job.

    It’s not clear to me why to use it, the pitch today is that it makes failures loud, which is nice, but very poorly described.

    The tool itself looks good, but the website looks very “Claude”, especially the text at the top saying “ONE BINARY · LINUX · MACOS · WSL · 25 MB RAM IDLE”

    Those are great pros, but are they the guest thing the user should see?

    Honestly the first paragraph of the quick start is a much better pitch:

    RunWisp is one small Go binary. You list the shell commands you want to run in a runwisp.toml, and RunWisp takes care of the rest — firing jobs on cron, restarting services when they crash, and capturing every line of stdout and stderr so you can go back and look at what happened. There’s a TUI in your terminal and a Web UI in your browser for poking around. No external database, no agent, no sidecar

    This tool looks decent, but for me I find nix helps manage the complexity of systemd well