<qyliss>
it would be a very nice story for us for sharing files with VMs on the fly
<qyliss>
(for applications that support it)
<Shell>
which is, at the least, all GTK3 and Qt5 apps that use those toolkits' file dialog widgets, iirc.
<IdleBot_5e50c57d>
It actually sends the file through the bus?
<Shell>
nope, in flatpak it mounts the file into the container and returns its filename.
<IdleBot_5e50c57d>
I wonder how much data the application is allowed to pass to the dialog… (although of course it might be that exploiting does not need much)
<IdleBot_5e50c57d>
Hm, if one can live-mount, this does not need portals, it can be controlled from outside
<Shell>
indeed, but from a UX point of view having a working "open file" button like people expect is wonderful.
<IdleBot_5e50c57d>
Kind of, and of course for me the best UX is on the fly command-line management of the shared file set, and open working on the files inside the VM
<IdleBot_5e50c57d>
(GUIs are not a convenient way of navigating stuff)
* Shell
shrugs.
<Shell>
there's nothing that says that the file dialog side of the portal has to be implemented as a GUI. it could be ranger or something else.
<IdleBot_5e50c57d>
I guess it should be easy to choose whether to export the request outside the VM or run inside
<IdleBot_5e50c57d>
Ranger does not really help, it is more of a question of probably having a directory near the nevessary stuff open in some screen
<Shell>
I really don't get how people use computers, apparently. *shrug*
<IdleBot_5e50c57d>
You probably understand how normal people use computers! Too bad they are using the computers wrong
<Shell>
my hope is that Spectrum is accessible to e.g. activists with non-technical focuses, so supporting standard usage patterns where they're not obviously security risks is really important.
<IdleBot_5e50c57d>
That surely requires
<IdleBot_5e50c57d>
someone who can compare the probable risks of implementations of some usage patterns
<Shell>
you have to do that anyway.
<IdleBot_5e50c57d>
Checking for known risks in scenarios is a bit easier than comparing risks, though
<Shell>
Everything has some known risks. The primary one being that the user doesn’t understand what they’re doing.
andi- has quit [Remote host closed the connection]
andi- has joined #spectrum
<IdleBot_5e50c57d>
Some users do; and if we initially target them we could actually get some users who can help to compare the risks
MichaelRaskin has joined #spectrum
<Shell>
The point is that using standard UX patterns allows users to understand what they’re doing better, since they’ve probably used a computer with those patterns before.
<MichaelRaskin>
Usually this allows to continue misunderstanding in the same way…
<Shell>
I don't think there is a significant misunderstanding in "ordinary" use of computers.
<MichaelRaskin>
I think there is often a misunderstanding about the implications of some actions
<qyliss>
Ah wonderful, looks like I'd need to sign a CLA to fix Google's code for them.
<qyliss>
So I suppose I shall keep it to myself
<MichaelRaskin>
You built sommelier?
<qyliss>
I build it's singular in-tree dependency
<qyliss>
But I think now I should be able to build sommelier easily enough as well.
<MichaelRaskin>
Next step would be to build it while using less than 10GiB?
<qyliss>
What do you mean?
<qyliss>
Of disk?
<MichaelRaskin>
Yes, I think I tried to build something around Android and it was nontrivial to get the sources I need without getting a stupid amount of sources