widgets boxmodel: disable input history

[samuelallan72]

I'd like to be able to disable the input history altogether. Some use cases result in entering sensitive information into the search, which would be better not stored to disk.

I'm thinking a new boolean config option (checkbox) like [ ] disable input history. Would this be an accepted feature?

[ManuelSchneid3r]

The problem is that currently the queries are not only stored in the input history file.

This idea is not that easy to accomplish given that, if implemented, users really expect the app to be safe. This means (debug) log messages, input history (activations+unactivated past queries, in frontends), activation database (used for item scoring, the reason why the exact query is there as well is because I planned to use them as input to machine learing algos to better suit your habits of query->item matches) and plugins! have to be controlled, which is probably an impossible task. Especially since the queries are broadcasted to the plugins which are basically out of the core apps control. they may store queries or not. (triggered queryhandling extensions are run exclusively though).

then theres still the problem of completeness due to the architecture of the app: frontends are plugins as well. even if the app decides to be incognito the frontend has to do so as well. this is going to be a UX nightmare. I'll have to think about this a bit.

[ManuelSchneid3r]

In the long run the widgets box model frontend will probably move into the core and will not be modularized anymore. That'd at least give a foundation to have something like a incognito mode. But probably this is not going to happen soon. Closing this since its far away. Ping me again if theres no frontend modularization anymore.