Patrick

I have not looked at this in depth but the process management is not done by `flatpak-builder` or `flatpak`, so I think this should be reported elsewhere (`xdg-desktop-portal`?). `flatpak build`...

In order to do this we would have to copy all schemas to the build dir then compile.

Also off topic but: > to substitute the gettext-domain at build time Is that really needed? Most projects never change their domain name in the entire lifetime of the project.

> It's probably even possible to detect whether any targets look like a schema I'm not sure that is a good design, like what if a schema is added to...

I have one concern, this exposes system information directly to the web which adds information for fingerprinting. Browsers like Safari specifically filter and reduce this list to make it less...

Unfortunately `xdg-desktop-portal` depends on `gnome-keyring`. KWallet could in theory implement `org.freedesktop.impl.portal.Secret` but it doesn't currently.

> Using Flatseal I then try to give it talk permissions to org.freedesktop.secrets, but that seems to be depreciated(?) as the flatpak is not supposed to talk to anything outside...

> Not sure if Pithos is expecting something that doesn't exist, or if the keyring in seahorse is incompatible with pithos until it's recreated. FWIW Pithos isn't really doing anything...

> Up until recently, the distribution package could make a password, but now it can't create nor read the KDE wallet even if it's unlocked. AFAICT KDE 5.97.0 added `org.freedesktop.secrets`...

Sorry for bumping the old issue. But Cog itself will not use the WPEPlatform API. Instead your application would use it directly (it's provided by default in WPEWebKit 2.50+). The...