malte-v

Another idea: Do all configuration and plugins prior to compiling similar to how the [suckless](https://suckless.org/) people do it. The end-user would clone a repo/crate that depends on the `helix` crate...

> Scripting languages are better suited for tasks like this, and locking it into a language has a steep learning curve might not be the best decision. Most scripting languages...

I assume support for hardware OpenPGP keys needs to be implemented by us, then? It looks like PGPainless doesn't support this kind of functionality.

For hardware security key support, I think this might be of use: https://github.com/cotechde/hwsecurity It's GPL3 licensed, pure Java and thoroughly documented at https://hwsecurity.dev/.

I think that since Cargo is doing all the heavy lifting for us, we basically already have WASM support. You just need to set `CARGO_BUILD_TARGET` to `wasm32-unknown-unknown` and maybe use...

I started working on this in my fork (https://github.com/malte-v/vulkano/tree/external-objects) and added all the necessary functions, structs and constants to `vk-sys`. Now we need to come up with a way to...

Same issue on Linux.

I'm running into the same issue right now. It's pretty easy to reproduce: ``` # bwrap --unshare-all --share-net --cap-add cap_net_bind_service --ro-bind /usr /usr --ro-bind /lib /lib -- nc -l 20...

I think the problem is that `--cap-add` grants capabilities in the new user namespace, rather than the parent user namespace. That makes it pretty useless in conjunction with `--unshare-user`. See...

> my workaround was to just do a sysctl net.ipv4.ip_unprivileged_port_start=442 Yep, that's what I do too. I don't think Linux supports granting parent user namespace capabilities to a child user...