For privacy, I’d like to be able to set the klipper history to expire and automattically clear after 3 hours or similar.
You can add a cron job to run qdbus6 org.kde.klipper /klipper clearClipboardHistory
2 Likes
You could also add this to kalarm 
Hmmm it’s a workaround… but I feel like each entry should have its own expiry, as in the expiry should be relative to the creation time for each item.
So I suppose if I can query when each item was added to the history I could run a job every X interval to do that.
Though I don’t know if that amount of data is accessable.
Also in the workaround department, then, perhaps you could possible to periodically insert new entries into the clipboard to force older ones to expire out (there’s also a setClipboardContents DBus method for Klipper)?
Ex. if you have a new arbitrary entry inserted once an hour, and if the max history is 3, then you know that something more than 3 hours old will be pushed out of the history by the script-inserted items?