IRC channel logs
2026-01-12.log
back to list of logs
<dthompson>niklauzg`: wasm and ocapn both have a capability security model but for different levels of the stack <niklauzg`>dthompson`: different levels, yes, just wondering if there's any bridging now or planned? <dthompson`>I'm not sure what bridging would be needed, I guess <niklauzg`>I ask b/c I'm turning over an idea for a Saltstack inspired distributed config-mgmt tool and want to know if the idea of extending the OCapN model to other "parts" of the system is a (1) YesPlease (2) NoPlease (3) BuildYourOwn (4) PreMadeMix -type of situation :) <dthompson>wasm capabilities make it possible to execute untrusted code. one capability you might give to a wasm module is a reference to an ocapn connection <dthompson>I've thought about distributed configuration management for guix quite a bit. ocapn would definitely be useful there but I don't see a clear use for webassembly <niklauzg`>In my mind I'm imagining a mesh that can use Nix/Guix config concepts and apply them using various executors (Nix, Guix, TF, Salt, etc) .. so although Sheperd is already barking up this tree it's interesting to me to see if it could be generalized more broadly <niklauzg`>I acknowledge the answer to my question is probably (5) GitGud .. just wanted to gently touch the surface of the water first before going further <jfred>I could potentially see some uses for it in the absence of language-level isolation like Oaken. Not entirely a fully-formed thought there though <niklauzg`>Yeah whatever else it is, it's definitely a fun idea <niklauzg`>.. and with some sort of RDF as the config layer it (ideally) wouldn't get too unweildy