This project ended up winning, I'm overwhelmed! 😬

This is cool. A few years ago l, all my commits had a start of day timestamps but pgp signing yubikey and qubes proxy got in the way so I stopped.

Thanks for bringing up signing. That's indeed another source of privacy leak. I'll have to think about how to approach this :) I think what we need is unattended signing, or probably more likely, batch signing (sign once no matter how many commits) 🤔

This is really cool idea. A few years ago I experiemented with some shell aliases to mess with the commit dates. I gave up as a pgp signature comes with its own date so this needs to be manipulated too and I had an obsure signing setup.

@once_aphysicist gpg does take '--faked-system-time' so maybe there is someway align the pgp sig dates? I was using a yubikey through a qubeos proxy and gave up because of

GitHub

Allow "faked-system-time" option in qubes-gpg-client · Issue #5034 · QubesOS/qubes-issues

Qubes OS version 4.0 latest Affected component(s) or functionality Qubes split keys functionality Brief summary gpg2 supports "--faked-system-time"...

here were my shell aliases: ``` shellAliases = { git-today = '' env GIT_AUTHOR_DATE="`date -I`T00:00:00" env GIT_COMMITTER_DATE="`date -I`T00:00:00" git''; git-month = '' env GIT_AUTHOR_DATE="`date +%Y-%m-01`T00:00:00" env GIT_COMMITTER_DATE="`date +%Y-%m-01`T00:00:00" git''; git-last-month = '' env GIT_AUTHOR_DATE="`date +%Y-%m-01 -d '-1month'`T00:00:00" env GIT_COMMITTER_DATE="`date +%Y-%m-01 -d '-1month'`T00:00:00" git''; }; ```