Re: kpasswdserver cleanup

>It also still talks to KWallet directly instead of Qt Keychain.

kwallet should bridge into the same backend as QtKeychain. So whilst
it should be ported isn't a blocker.

>Is that still something that=E2=80=99s worthwhile or should we simplify th=
is and
track the app closing (

Probably.

> However, that probably won=E2=80=99t work with out of process workers and=
 is likely the reason this was
done on a per-window basis in the first place.

A worker POV doesn't know about windows either, so either that isn't
true (I don't think it's true) or the worker is just forwarding an
opaque string at which point it could be the connection name.

---

The idea of passing things around via KIO between apps isn't as
relevant anymore.

A sandboxed app cannot (and shouldn't!) talk to kpasswrd. At which
point it's fundamentally not something we should be using moving
forward. We can do some patchwork quick fixes but I strongly wouldn't
recommend doing a rewrite or new API.

> Or is this entire thing something we want to get rid of in favor of [inse=
rt portal API/qtkeychain/whatever]?

The one you're looking for is the "Document portal" :)
I'm not claiming it's perfect now, but that's where to invest the effort.

David