Event JSON
{
"id": "d327a3c3f5a8afef98e6ca71e2068d8e1caa4fe0a8bc397820c744a3a437aca3",
"pubkey": "4ebc018b65a1b352f90f937be79b5c338651f1528960889fa64caa94be982f8a",
"created_at": 1688057553,
"kind": 1,
"tags": [
[
"p",
"12d3ff8e62b788f72e38a5d1b9fafefd06ac6a5ea51e2b9f55f1abb26e08b994",
"wss://relay.mostr.pub"
],
[
"p",
"bdf8e6a9c859b03b22181316d0f52e886a65f134ab5502c7d7ee2659a988409a",
"wss://relay.mostr.pub"
],
[
"e",
"e291d04ab58da6e6f7de50437acb837fb137ef396c385dc389c4eaac46eac18c",
"wss://relay.mostr.pub",
"reply"
],
[
"emoji",
"blobfox3c",
"https://social.vlhl.dev/emoji/blobfox/blobfox3c.png"
],
[
"mostr",
"https://social.vlhl.dev/objects/64033732-6f35-4ebf-b7ae-8d1c7a40b868"
]
],
"content": "nostr:npub1ztfllrnzk7y0wt3c5hgmn7h7l5r2c6j7550zh8647x4mymsghx2q88nzmz couldn't you use chroots instead of containers? or have a wrapper script for codium that sets a new XDG_RUNTIME_DIR? (tho if you're on wayland, that will break wayland socket detection ://... but so would the process having a new mountpoint)\n\ni think what i would do is have a script to build a chroot and link only the stuff needed to it (wayland-0 socket, pw-socket, /dev, etc), and just start apps from those chroots (or just a single tmux session in each) (actually this sounds quite like the useful tool to have as a setuid or CAP_*... hmmm... another thing to the list of ideas :3)\n\nor i'd be lazy and just install every tool on my main system anyway :blobfox3c:",
"sig": "3336121bbd76978e42fa62063ad3fce06694459e69c0203b7f1cd376cf016bc6299320aae40304b8ba7fee9849d3d31e1bb2ea76c524af455a35f940994a01f8"
}