| 31 Oct 2024 |
 sophie | if you're using Android, you can put the keys into an encrypted space with the encryption keys protected by the secure element too :) might be possible on iOS too but not tried that | 21:18:52 |
 ElvishJerricco | yea, tough choice between storing a wrapped key on the disk vs storing a wrapped key on the phone | 21:20:40 |
| ElvishJerricco | different tradeoffs between the two | 21:20:46 |
| sophie | could either use the stored key on the phone as the TPM2 pin or have the password be a combination of both keys | 21:22:15 |
| ElvishJerricco | yea that's interesting | 21:23:17 |
| 1 Nov 2024 |
|  Thales Menato joined the room. | 01:28:00 |
|  Ryan Yin joined the room. | 14:20:56 |
| 2 Nov 2024 |
|  Birhaman changed their profile picture. | 03:42:05 |
| Birhaman changed their profile picture. | 03:45:35 |
|  @icarus_dh:matrix.org joined the room. | 14:07:03 |
| 3 Nov 2024 |
|  Sam joined the room. | 14:34:19 |
|  Marco Turchetto left the room. | 16:15:51 |
|  Kiruya Momochi 百地希留耶 joined the room. | 19:50:31 |
| Kiruya Momochi 百地希留耶 changed their display name from 百地希留耶 to Kiruya Momochi 百地希留耶. | 19:57:42 |
| 4 Nov 2024 |
|  @optimusgray:technogeek.ninja joined the room. | 01:18:36 |
|  rhousand joined the room. | 17:23:43 |
| 5 Nov 2024 |
|  liv [she/her] joined the room. | 20:31:27 |
| 6 Nov 2024 |
|  @seapat:matrix.org joined the room. | 13:45:46 |
 Scrumplex | Is there a way I can instruct Nix to prefer building locally over using remote builders?
I am on a x86_64-linux machine and I have a x86_64-linux remote builder. Currently Nix seems to prefer the remote builder, even though I have more cores (and performance per core) locally. The speed factor of the builder is 1 | 14:56:44 |
| Scrumplex | According to the documentation of nix.conf, the speed factor must be a positive integer, so I can't really do something like 0.5 | 14:57:09 |
| Scrumplex | * According to the documentation of nix.conf, the speed factor must be a positive integer, so I can't set it to something like 0.5 | 14:57:15 |
 flare | been using nixos for 2 years now and have only now heard of nix.conf. if anyone has experience on this it would be interesting to see that response | 15:00:44 |
 K900 | In reply to@flare:matrix.darkc0de.one
been using nixos for 2 years now and have only now heard of nix.conf. if anyone has experience on this it would be interesting to see that response Uhh, what | 15:00:58 |
| Scrumplex | * According to the documentation of nix.conf, the speed factor must be a positive integer, so I can't set it to something like 0.5 | 15:01:18 |
| Scrumplex | In reply to @flare:matrix.darkc0de.one
been using nixos for 2 years now and have only now heard of nix.conf. if anyone has experience on this it would be interesting to see that response I assume you have configured nix.conf just never directly. The options nix.settings.* will be used to generate /etc/nix/nix.conf on NixOS | 15:02:32 |
| K900 | In reply to@scrumplex:duckhub.io
Is there a way I can instruct Nix to prefer building locally over using remote builders?
I am on a x86_64-linux machine and I have a x86_64-linux remote builder. Currently Nix seems to prefer the remote builder, even though I have more cores (and performance per core) locally. The speed factor of the builder is 1 speedFactor isn't even considered for local builds | 15:02:39 |
| Scrumplex | In reply to @flare:matrix.darkc0de.one
been using nixos for 2 years now and have only now heard of nix.conf. if anyone has experience on this it would be interesting to see that response * I assume you have configured nix.conf, just never directly. The options nix.settings.* will be used to generate /etc/nix/nix.conf on NixOS | 15:02:42 |
| K900 | There's some weird heuristics | 15:02:53 |
| Scrumplex | In reply to @k900:0upti.me
speedFactor isn't even considered for local builds I feared this would be the case | 15:02:58 |
| Scrumplex | I think my biggest wish for Nix would be more dynamic allocation of resources. It would be great if Nix could somehow "look-ahead" and dynamically allocate more cores to build jobs.
Like let's say you are building a large closure and Nix will soon need to spend time building a single derivation that every remaining derivation depends on. It could just allocate all available cores to that derivation, while when building many derivations in parallel it could allocate a small amount of cores to not overwhelm the system | 15:06:57 |
