onedrive VS Flatseal

here's a hunch assuming you tried the below client:

https://github.com/abraunegg/onedrive/blob/1a88d33be3e2c6747...

try changing that to e.g. the android (or windows) onedrive client's id.

this trick works for exchange (allowing third-party mail clients).

Syncthing might fit the bill, or just keep using Onedrive: https://github.com/abraunegg/onedrive

I first started with this onedrive client https://github.com/abraunegg/onedrive (+ the GUI package) and got it working fine, but it seems like a sync all-or-nothing deal.

Source: https://github.com/abraunegg/onedrive

You could check out https://abraunegg.github.io/, I use that for syncing with my OneDrive.

* Via the OneDrive Client for Linux - https://github.com/abraunegg/onedrive - this 'syncs' your data, bi-directional operation, open source and free. Supports Personal, Business & SharePoint account types and Shared Folders. A Docker container is also available for all major architectures (x86_64, ARMHF, AARCH64). If you need a GUI for onedrive client management use: https://github.com/bpozdena/OneDriveGUI

I have used an app called, appropriately, onedrive. The git repository and info is here. Once you connect to OneDrive (not hard to do at all) you can do anything in the folder and when you start the command from the CLI it will sync the files to your account and update the files on the server. There are a few custom options you can set to streamline. I used it for a long time syncing with Windows and it works great.

The client itself is 100% stable and functional enough for your use-case. To read up on the client, please visit: https://github.com/abraunegg/onedrive

And not only that, the idea of portals is, IMO, misguided. See this view/bugreport when a flatseal user understands that even though they restricted permissions to access a certain area, the flatpak, itself, can ask to open files there and if OK'd that will be allowed. Their expectation is that with the overrides say "no access" it means "no access even if the flatpak asks very nicely". https://github.com/tchx84/Flatseal/issues/196

Since you installed the programme via Flatpak, you should simply lack the necessary rights (https://docs.flatpak.org/en/latest/sandbox-permissions.html). You can extend the rights quite easily with https://github.com/tchx84/flatseal.

Yes, filed https://github.com/tchx84/Flatseal/issues/196 a while ago, got no joy.

One design feature than can turn into an issue in some scenarios (usually dev tools) is the permissions of a flatpak. In case I need to tweak things, I use Flatseal. I know you can manually do this from the command line but I don’t change permissions that often so I don’t bother learning how to do that.

Does the Flatpak Permissions Settings replace a tool like Flatseal?

What about flatseal then ? https://github.com/tchx84/Flatseal

https://github.com/tchx84/Flatseal (Also on Discover. For security reasons, the Discover store installs apps as sandboxed "flatpak" apps. This one is used to view what each up can do and change the permissions of apps. May be required if the sandboxing breaks something, though usually not required.)

I believe it does. As an example if I try running Godot from the Steam flatpak, it won't be able to see any of the contents of my ~/Projects folder unless I explicitly allow the steam flatpak access to that directory that via flatpak's CLI options or using Flatseal