Other backends can be disabled in the Settings. KNHS cannot.
What's the use case?
Created attachment 177089 [details] attachment-3257188-0.html On January 4, 2025 4:19:40 AM GMT+10:30, Nate Graham <bugzilla_noreply@kde.org> wrote: >https://bugs.kde.org/show_bug.cgi?id=498197 > >Nate Graham <nate@kde.org> changed: > > What |Removed |Added >---------------------------------------------------------------------------- > Summary|Make KNHS a backend that |Allow disabling the GNS > |can be disabled. |backend without > | |uninstalling its package > CC| |nate@kde.org > >--- Comment #1 from Nate Graham <nate@kde.org> --- >What's the use case? > >-- >You are receiving this mail because: >You reported the bug. Similar functionality to other backends and faster load times.
> Similar functionality to other backends and faster load times. The functionality is definitely not similar; the KNS backend provides content not available in any other backends. Faster load times I'm not sure about. Have you benchmarked this? Try running `plasma-discover --backends packagekit,flatpak,fwupd` and compare it to `plasma-discover --backends packagekit,flatpak,fwupd,kns` For me they feel identical in speed.
It's a backend and I think it should be able to be disabled like others. It would also be good to be able to disable it for corporate and business environments. I haven't benchmarked it but it makes it "feel" slower.
The institutional use case makes sense, yeah.