Sebastian Wick

If the system component that is supposed to have permissions by default runs on the host you can give all host apps that permission by checking for `XDP_APP_INFO_KIND_HOST`. They *do*...

> In the case of kde connect I'm seeing "" as an app_id because it's launched by the dbus daemon. I guess we should extend the app_id-detection capabilities? Please, yes....

How would the issues raised here be dealt with? https://bugzilla.mozilla.org/show_bug.cgi?id=1621763#c2

> This proposal seems like it's intended to solve the "Interaction" point in that comment, but not the "Discovery" point: if the browser wants to enumerate all the native messaging...

That would work but it's far from ideal. Taking a step back, what we really want is for applications to communicate with each other freely through dbus. The application providing...

IMO the suggested prompt is exactly what we try to avoid: there isn't any way for a normal user to judge if it should be allowed or not. If we...

If the connector is a flatpak we could get reliable names *but* what does accessing KeePassXC mean? How can I judge that Firefox is not doing anything horrible with KeePass?...

Is the app flatpak, snap or host? Which portal backend do you use?

This is very likely an issue with a specific backend + compositor. Which ones do you use? I suspect xdg-desktop-portal-gtk and not gnoms-shell? https://github.com/flatpak/xdg-desktop-portal-gtk/blob/366d3349041c2e06658c7c5a8b5bfd5f345d8157/src/fdonotification.c#L348

`ps ax| grep xdg-desktop-portal` might be sufficient, otherwise check which component supports the notification interface in `/usr/share/xdg-desktop-portal/portals/` or use `dbus-monitor` to figure out what gets called.