cat /etc/machine-id

Well, maybe my hardware sucks or I have skill issues, but all of these are major hurdles. In the case of android/flashing, many things will reset the connection, which breaks the first qubes sharing command, and I can’t share the “new” device (same device now in a different mode) b/c either I’m too slow or it only works for the first connection (and it’s not in the right state after trying to re-share the device a second time due to a bus reset, or the like)…

Stuff like games, video conferencing, screen sharing, android development, flashing ROMs, 3D CAD/slicing… if you care about dropped frames I would even put video playback on that list.

Yeah, Qubes is cool, but then you need a second system/os to do “normal” stuff…

“Your” dashboard?

A subnet mask mask!

Initiate docking procedure!

You’ve got the right idea with the permission change… the key is that you can have code executing on the remote side with different permissions. So the writer process has permission to write in one directory, and the turnsyle procees (often the root super-user) rotates the files or directories at a different time (or on a signal, sometimes).

I’ve been eyeing the ratrig kits for the open-sourceness, but they might be out of your target price range.