| 19 Dec 2024 |
 @hexa:lossy.network | and you only get the json subset in nix | 23:33:40 |
 ghostbuster91 | I don't need my generated json/yaml to be compact or readable | 23:34:05 |
| ghostbuster91 | I don't care about low-level assembly format | 23:34:16 |
| ghostbuster91 | (apart from debugging it :D ) | 23:34:41 |
| 20 Dec 2024 |
 spacekitteh | 'cus yaml sucks | 02:24:39 |
| spacekitteh | xml all the way baybee | 02:24:53 |
| @hexa:lossy.network | no. | 02:24:57 |
| @hexa:lossy.network | yaml before 1.2 sucks | 02:25:12 |
| @hexa:lossy.network | basically yaml 1.1 sucks | 02:25:16 |
| spacekitteh | does this room support polls | 02:25:34 |
| @hexa:lossy.network | so in python use https://github.com/perlpunk/pyyaml-core or ruamel.yaml | 02:25:45 |
| spacekitteh | yes yes it does, good | 02:25:51 |
| @hexa:lossy.network | it does | 02:25:53 |
| spacekitteh | can i make a poll about how to implement something in the thread border router module i'm working on? | 02:26:26 |
| @hexa:lossy.network | why does it neeed to be a poll? | 02:26:49 |
| @hexa:lossy.network | do you want people to just click an answer without any particular reasoning? | 02:27:08 |
| spacekitteh | 'cus there are several ways i can implement some settings, and i want to see which will be the most convenient for people | 02:27:22 |
| spacekitteh | basically, do people want to supply a binary blob for their configuration file, or would they prefer setting a whole bunch of options which then is used to make a script which runs after service startup; if the former, would they want the configuration file to be mutable or not | 02:30:02 |
| spacekitteh | i get why it's a binary blob, as it's usually for storage on flash/EEPROMs, and posix is a special case, but damn it's annoying | 02:32:21 |
| @hexa:lossy.network | what is the binary blob? | 02:32:52 |
| spacekitteh | basically a bunch of TLVs describing the network configuration | 02:33:38 |
| @hexa:lossy.network | so it sounds likely that the user wants to configure that | 02:34:28 |
| @hexa:lossy.network | in an easy way | 02:34:33 |
| spacekitteh | yeah. but there is basically no easy way other than using the daemon's CLI to set stuff, and then grabbing the file | 02:35:44 |
| spacekitteh | however, it /is/ persisted | 02:36:30 |
| spacekitteh | basically, most of these settings need to be set/initialised one way or another: https://github.com/openthread/openthread/blob/main/src/cli/README_DATASET.md | 02:39:03 |
| spacekitteh | and a few others should be customisable | 02:40:01 |
| spacekitteh | the more i'm thinking about this the more i think i'll go the script way, and tack on an extraConfigScript option to run after the necessary ones | 02:42:15 |
| spacekitteh | that way, the entire config file doesn't have to be treated as a secret, rather than just the PSK | 02:43:34 |
| @hexa:lossy.network | probably for the best | 02:44:53 |
