3 ms·
that's an interesting approach i think you could probably get pretty far by creating a new x11 socket with fresh xauth for each new program launched; then, ins
by kragen 4y ago
that's an interesting approach
i think you could probably get pretty far by creating a new x11 socket with fresh xauth for each new program launched; then, instead of opening new floating overlapping windows for them, embedding the display of whatever windows they create in your notebook, just below below the command that created them
a bytestream protocol has some real advantages, including being able to forward it over a network socket, including an ssh-forwarded socket, or providing a gui for whatever little embedded electronic gadget you build and connect to your terminal over spi or usb serial
i had previously rejected it as too inefficient for the localhost use case, but in https://news.ycombinator.com/item?id=35693474 https://news.ycombinator.com/item?id=35693474, and some later protocol-design ideas i haven't shared yet, i convinced myself that you can probably make it efficient enough for anything that doesn't use custom shaders
is this something you'd be interested in talking about in a less hostile environment
- hello_computer 4y agoIs the email on your site still good?
- kragen 4y agoyes, but sometimes i fail to notice email among the spam unless you ran across the pobox address, which has been dead for... a while the canonical.org address is the correct one comment if you've emailed me and not gotten a response