qyliss changed the topic of #spectrum to: A compartmentalized operating system | https://spectrum-os.org/ | Logs: https://logs.spectrum-os.org/spectrum/
<pie_> MichaelRaskin: oh yeah, implicit notion of reconnection was assumed
<pie_> MichaelRaskin: so yeah
cole-h has quit [Quit: Goodbye]
<MichaelRaskin> Well, it is a strong assumption to make, as neither plain X11 nor plain Wayland support it.
<ehmry> there was a talk on preserving state at fosdem, too extreme to be used here, but interesting https://fosdem.org/2020/schedule/event/uk_phantom/
<MichaelRaskin> In a sense, even antithetical to SpectrumOS goals, as in «application instances should have bounds on what they do, including the time bounds on their lifetime»
<ashkitten> it would be pretty cool to be able to freeze/resume apps, tbh
<MichaelRaskin> Across reboots? Yeah, but then one needs to drop «almost normal Wayland»
<pie_> even within a reboot tbh given that i have average uptimes somewhere around a month probably
<MichaelRaskin> Within a reboot I think Graham has experimented with just SIGSTOP/SIGCONT and it is closer to working than not
<MichaelRaskin> (where experimenting included auto-stop on focus loss)
<puck> MichaelRaskin: i've been designing a wayland thing that supports this :3
<puck> network transparent wayland proxy
lejonet has joined #spectrum
Profpatsch has quit [Quit: WeeChat 2.8]
Profpatsch has joined #spectrum
spacekookie has quit [Quit: **aggressive swooshing**]
spacekookie has joined #spectrum
cole-h has joined #spectrum
<ashkitten> MichaelRaskin: i was thinking potentially even saving apps to get back to later, putting them away entirely
<MichaelRaskin> Get a swap
<MichaelRaskin> (Or across-reboots with VNC, sure)
<hyperfekt> MichaelRaskin: i was gonna say the same but it could be useful to prevent unneccessary wakeups and conserve battery power i guess?
<MichaelRaskin> I was assuming that SIGSTOP is the baseline
tilpner has quit [Remote host closed the connection]
tilpner has joined #spectrum
<MichaelRaskin> BTW, if you want to give CrosVM some networking cheaply, you could use ssh -D 1080 127.0.0.1 to create a SOCKS5 proxy, and then pass just that socket into CrosVM (with proper application of socat)