@chaseadam17 - What advice or lessons would you share for others looking to pursue a company which focuses on public good or nonprofit?

Well done, OP.

Every single other previous advance that could have done that has NOT produced the less stressed part - imagine taking an 1800s subsistence farmer and arming him with modern equipment and tooling; he'd be ecstatic.

The key is always internal, personal, once you right yourself, the world starts feeling much better.

I really enjoyed Zork. I am enjoying your creation and the ability for it to translate instructions into multiple steps makes it much more enjoyable than the original.

> it is possible to design a sw stack capable of making updates to traditionally burned-in components.

This is interesting - is the software stack essentially acting as "light" translation layer or abstraction layer on components?

I have been receiving a large number of spam emails in my "Important and Unread" areas which is anomalous. I was wondering exactly why and this helps. thanks!

@carderne I think el_pa_b has an idea on how to commercialize it.

In all seriousness, how is it not useful for gold mining or phracking?

I like it - I had been taking screenshots with Cmd-Shift-4. ha!

Well $hit. I have been using Docker for installing NPM modules in interactive projects I was testing out. I believed Docker blocked access to the underlying host (my computer).

Thanks for mentioning it - but now... how does one deal with this?

If you didn’t mount docker.sock or any directory above it (i.e. / or /run by default) or run your containers as --privileged, you’re probably fine with respect to this angle. I’d still recommend rootless containers under unprivileged users* or VMs for extra comfort. Qubes (https://www.qubes-os.org/) is good, even if it’s a little clunkier than it could be.

* but if you’re used to bind-mounting, they’ll be a hassle

Edit: This is by no means comprehensive, but I feel compelled to point it out specifically for some reason: remember not to mount .git writable, folks! Write access to .git is arbitrary code execution as whoever runs git.

As sibling mentioned, unless you or the runtime explicitly mount the docker socket, this particular scenario shouldn't affect you.

You might still want to tighten things up. Just adding on the "rootless" part - running the container runtime as an unprivileged user on the host instead of root - you also want to run npm/node as unprivileged user inside the container. I still see many defaulting to running as root inside the container since that's the default of most images. OP touches on this.

For rootless podman, this will run as a user with your current uid and map ownership of mounts/volumes:

    podman run -u$(id -u) --userns=keep-id

Podman makes this easier to do safely by default. I'd suggest checking that out.

I think one or both also have Roku channels as well