xdg-desktop-portal requires integration with the sandbox tool for certain portal interfaces to function properly (e.g. org.freedesktop.portal.FileChooser.) The way flatpak does this (and probably the easiest way to emulate..) is to introduce a /.flatpak-info file in the mount namespace of xdg-dbus-proxy as well as a bwrapinfo.json at $XDG_RUNTIME_DIR/.flatpak/$INSTANCEID. I was considering attempting this myself but I was curious if there were any plans the maintainers had for this functionality.
`xdg-desktop-portal` requires integration with the sandbox tool for certain portal interfaces to function properly (e.g. `org.freedesktop.portal.FileChooser`.) The way `flatpak` does this (and probably the easiest way to emulate..) is to introduce a `/.flatpak-info` file in the mount namespace of `xdg-dbus-proxy` as well as a `bwrapinfo.json` at `$XDG_RUNTIME_DIR/.flatpak/$INSTANCEID`. I was considering attempting this myself but I was curious if there were any plans the maintainers had for this functionality.
I have experimented with the document portal in the past, all implementations I've seen does not work across uids. I'm still looking into what I can do about that.
For now I implemented file sharing in my setup somewhat like android's /sdcard, where a permissionless filesystem is optionally exposed to apps, and most xdg user dirs are pointed at that directory for apps and the priv-user, so stuff like downloads still work.
I have experimented with the document portal in the past, all implementations I've seen does not work across uids. I'm still looking into what I can do about that.
For now I implemented file sharing in my setup somewhat like android's /sdcard, where a permissionless filesystem is optionally exposed to apps, and most xdg user dirs are pointed at that directory for apps and the priv-user, so stuff like downloads still work.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
xdg-desktop-portalrequires integration with the sandbox tool for certain portal interfaces to function properly (e.g.org.freedesktop.portal.FileChooser.) The wayflatpakdoes this (and probably the easiest way to emulate..) is to introduce a/.flatpak-infofile in the mount namespace ofxdg-dbus-proxyas well as abwrapinfo.jsonat$XDG_RUNTIME_DIR/.flatpak/$INSTANCEID. I was considering attempting this myself but I was curious if there were any plans the maintainers had for this functionality.I have experimented with the document portal in the past, all implementations I've seen does not work across uids. I'm still looking into what I can do about that.
For now I implemented file sharing in my setup somewhat like android's /sdcard, where a permissionless filesystem is optionally exposed to apps, and most xdg user dirs are pointed at that directory for apps and the priv-user, so stuff like downloads still work.
This requires more experimentation and most likely will not break api if it's possible to implement. Removing from v0.2.0 milestone.
Superseded by #21.