Ivan :nix_snowflake_logo: / is on Nostr

he/him 
I like writing software, #rust, and #nixos Author/maintainer of #crane

Last Notes

2024-06-10 18:26:10

This is my first foray into the #matrix ecosystem. Started with Element because it’s the flagship/recommended app, but so far I’m not super impressed.
Is Element pretty jank, or is a lot of that the fault of the protocol/home server?
Anyways feel free to send me client recommendations

2024-05-23 21:10:12

- reply

@npub1uu6…58s2 really digging this one!

2024-05-17 02:59:56

Remember folks: if your data is not end to end encrypted with keys only you control, some aspiring business type will inevitably act on the urge to extract (more) value out of it sooner or later
https://awscommunity.social/@Quinnypig/112452921509401306

2024-05-11 01:14:05

Every time I’d reach for `xargs` in a shell pipeline crunching a lot of inputs I’d always worry about there being too many arguments and blowing past the system exec limits, and manually try to limit invocations with a guesstimate of how many max args to use
Except I just learned that `xargs` can not only inspect the system and figure out how many args to use safely, it does it *by default*!
Easily one of my favorite utilities that went up in my list today

2024-05-11 01:10:12

- reply

But seriously though, I don’t understand why GitHub decided the only blessed way to get post-hooks is to write an action that must be executed by NodeJS. You can easily write a JS script that executes a shell script, so why not cut out the middle man entirely?
Sure GitHub publishes some npm packages which give you some cross platform APIs, but for a simple, Linux-only CI a shell script is more than plenty

2024-05-11 00:32:59

Writing a GitHub Action be like: why do something in 10 lines of bash when you could write 200 lines of JavaScript and pull in 30 package dependencies instead

2024-05-06 02:04:41

Configuring #gitea to sign merge commits
https://ipetkov.dev/blog/configuring-gitea-to-sign-merge-commits/
#selfhosted

2024-04-29 17:12:43

One aspect of #NixOS modules no one ever talks about: if you fetch and import modules written by someone else, you are effectively trusting them with root access to your machine

2024-04-19 07:26:32

- reply

@npub1hg2…k372 that’s fair yes. I deploy my static site with Nix so it’s at least easier to debug/reproduce the build locally ;)

2024-04-13 08:35:15

- reply

@npub1hg2…k372 GitHub logic: “lack of a reported failure is proof of a successful run” 🙃

2024-04-04 04:08:39

A #NixOS PSA for anyone trying to garbage collect the malicious versions of #xz and wondering why it’s not going away even after deleting previous generations and gc roots: make sure `keep-outputs` and `keep-derivations` is disabled in your Nix conf. You can turn them back on after running `nix-collect-garbage`

2024-02-11 21:30:25

- reply

@npub13w6…479m oh I’m not angry at debugging failed jobs (I have all the reproducibility I need thanks to #Nix) I’m angry at how badly designed the job syntax is. You’re basically forced to copy pasting stuff endlessly because all their abstractions sort of barely work and are unsuitable for anything beyond trivial examples