Closed mttkay closed 2 years ago
Yeah pretty sure that's the problem; looking at permissions for Slack, for instance:
[Context]
shared=network;ipc;
...
same for Dropbox and other networked apps.
A workaround is to first download the remote format to a local file on your host machine, then use a file://
URL in the import dialog.
But I would still consider this a bug, since it breaks existing functionality.
You can use Flatseal to enable it in the mean time.
Thanks for pointing this out, I was not aware of it; this looks really useful :+1:
Sorry for being late to the party, I didn't watch the repository 🤦🏻
Anyway, it was an intentional decision to no provide network access, but I can see why it's useful. Therefore let's go with it, people can restrict network access down the line.
I am not familiar with flatpak internals, but I noticed that I cannot import new formats from a remote destination in the flatpak version of Twine; it fails with the following error:
The URL is taken from https://github.com/lazerwalker/twison, and I can curl it from my host machine successfully:
So I wondered whether this could be a permission error due to flatpaks running in containers (IIUC). I checked the app permissions:
According to https://docs.flatpak.org/en/latest/sandbox-permissions-reference.html, this is missing the
network
permission:I tried to experiment with this by doing
but this seems to have no effect.
Any ideas what's going on here?