-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow access to common xdg directories #277
Conversation
Started test build 95877 |
Build 95877 successful
|
Hi @Feinzer given it was a small comment you might missed it, when reading through: #33 (comment) When you give read-only access to a directory, it still shows up in the saving dialogue and while you can select it and press save, it'll neither show an error, nor save the file. This is terrible from a UX perspective. While the absence of directories is also not ideal, users can at least ask the question "why is it missing? How can I add them?" There is an indication what works and what doesn't. For the read-only variant, it's not transparent at all, because saving a file, opens a dialogue which will close as if it would have saved the file, but if you delete the file from matrix, it's gone for good, not saved into your documents directory as you might expected. |
You're right, I missed it. Could we maybe have them as read-write then since nothing important from a security standpoint lives there? Of course, the best solution would be for flatpak to prompt the user for permission when accessing their Documents, for example like an Android phone does. However since this functionality does not currently exist and these are basic directories a user would have files saved which they'd want to share, I believe the default should be to allow using them. |
Started test build 95992 |
Build 95992 successful
|
I believe by giving read-write access to these xdg directories we would improve on usability and would not cause any issues when saving files on the client. Security wise, this should be fine as a Chat application should have access to directories such as Documents, Pictures and so on. No config or sensitive information should be living there |
Partially fixes #33 and #68
Following the discussions on #33 I can see why we can't allow access to the entire user's home so this would at least help by allowing read-only access to more common directories.