| 9 Apr 2026 |
 zoë (she/her) |
a Signal group
one more messaging app to install...
| 10:32:06 |
| zoë (she/her) | 
Download 1775730716788.jpg | 10:32:10 |
| zoë (she/her) | *
a Signal group
one more messaging app to install...
| 10:32:19 |
 raitobezarius | i mean, the matrix channel is usually not very usable in practice ^^ | 10:53:47 |
| zoë (she/her) | oh no i definitely agree it's a better choice | 10:55:04 |
| zoë (she/her) | * | 10:55:20 |
| zoë (she/her) | * | 12:11:45 |
| zoë (she/her) | * on matrix I'm not sure, but there also the zulip channel (and the con's website for general info) | 12:12:00 |
 delroth | meanwhile, FOSDEM: | 12:12:58 |
| raitobezarius | i was in the FOSDEM Matrix server and I couldn't use it personally ^^' | 12:14:57 |
| raitobezarius | (I was also in the LPC Matrix server etc etc) | 12:15:25 |
 blitz | Hey lixers! Does anyone know what the current status of the work on capnproto is? I'm wondering what my options are to talk to the Lix daemon from Rust without FFI to C++ | 17:41:33 |
| blitz | (background: I'm currently removing the FFI in attic that talks to the nix daemon via the c++ libraries and I'm wondering whether shelling out to nix-store is the only option at the moment) | 17:43:09 |
 piegames | The status is please hold the line | 17:47:14 |
| piegames | Should be all set up within the next 6 months | 17:47:27 |
| piegames | Current work status is we have some internal protocols running on Capnproto already, but the main protocols need an interop story and everything's FUBAR and the person driving this got a bit burnt working on it and is currently taking a little break to recover. | 17:49:25 |
| blitz | That's fair | 18:00:51 |
| blitz | So shelling out it is 😅 | 18:01:15 |
 Yureka (she/her) | you could also directly implement the existing nix daemon protocol | 18:02:11 |
| Yureka (she/her) | or whatever version of it | 18:02:41 |
| Yureka (she/her) | https://codeberg.org/gorgon/gorgon/src/branch/main/nix-daemon | 18:04:56 |
| Yureka (she/her) | https://git.snix.dev/snix/snix/src/branch/canon/snix/nix-daemon | 18:04:58 |
| Yureka (she/her) | here are two implementations of it in rust. neither of them support getting NARs out of the nix store but the author of the gorgon one wasn't opposed to adding that | 18:05:26 |
| Yureka (she/her) | Redacted or Malformed Event | 18:05:38 |
| blitz | Will check. | 18:21:00 |
 neobrain | Is there a recommended way of implementing nix-based tooling? For example, say I wanted to generate and build a nix expression without relying on cppnix or lix specifically being installed on the system.
Presumably talking to the daemon would be preferred for that? And if yes, what's the typical communication protocol? (Do I pull in a library or do I just, like, open a Unix socket or something?) | 18:36:35 |
 K900 | The daemon doesn't do eval | 18:43:49 |
| K900 | Only the clients do | 18:43:53 |
| neobrain | oh right... so I would have to pull in something like snix to evaluate the expression, and then request the daemon to realize the evaluated expression? And creating an out-link (with a GC root) would be a client-task again presumably that I just can't really abstract over at all?
(Trying to get my terminology in line here) | 18:58:32 |
| neobrain | Interesting, looking at the unstable nix C API, there's apparently a plugin interface too. That might be suitable for the particular type of tooling I'm looking into atm | 19:02:38 |
