xdp-hook-rs

trigger user-configured actions when other apps use xdg-desktop-portal ( https://github.com/flatpak/xdg-desktop-portal )

what?

xdg-desktop-portals are a mechanism built on top of dbus and pipewire, used by Linux apps when direct access to sensitive system capabilities is unavailable (or when explicit user consent is desirable)
we can use dbus-monitor to observe the negotiation and usage of such portals, but it doesn't make it convenient to create a bird's-eye view of active sessions, and might not be the easiest way to trigger portal-related automation, etc
xdp-hook's purpose is not to offer privacy indicators like those on Android, but rather to make it easier for others to offer such features, by reacting to portal usage and performing user-configured tasks e.g. executing scripts

[x] connect to user's dbus session
[x] identify and log out general messages relating to portal requests
[x] track open/close for prolonged portal sessions (e.g. Location, ScreenCast, RemoteDesktop)
[ ] track open/close for prolonged portal sessions (e.g. Inhibit)
[x] read configuration file ~/.config/xdp-hook/config.toml
[x] perform user-configured tasks upon portal request/session event e.g. executing scripts
[ ] user-scope systemd unit file for convenient startup
[ ] properly differentiate between concurrent clients for portals (e.g. both Chrome and Firefox using jitsi)
[ ] identify app/process that is initiating the portal request (impossible?)
[ ] identify the portal implementation that handles the portal request (impossible?)