From 195353bd1f9762b3b9c9846bac1f51c53ce5b2bcbb13db3a1aa6c1dc4e828122 Mon Sep 17 00:00:00 2001 From: Nicholas Johnson Date: Fri, 4 Aug 2023 00:00:00 +0000 Subject: Mention correspondence with Git developers --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a0f176f..a3ebe76 100644 --- a/README.md +++ b/README.md @@ -71,7 +71,7 @@ The last step is to set the script as executable with `chmod +x /path/to/custom- Github is known to record [when commits are pushed](https://api.github.com/repos/cirosantilli/china-dictatorship/events). See the ticket about [Github contribution activity](https://github.com/isaacs/github/issues/142). To obfuscate push times, one could push code with cron at regular time intervals. -It's possible to use Git hooks to accomplish timestamp obfuscation, but it's still necessary to manually override the date for some Git commands, making it very inconvenient. The developers of Git should make timestamp obfuscation a feature in order to make doing all this unnecessary. +It's possible to use Git hooks to accomplish timestamp obfuscation, but it's still necessary to manually override the date for some Git commands, making it very inconvenient. I asked Git developers to implement a timestamp privacy feature, but it was decided against. If you're curious why, here's [the relevant thread](https://lore.kernel.org/git/CTZ9RD9RQ5UO.3OIJX50PKMIR0@anonymous/t/#u) on Git's public mailing list. ## License -- cgit v1.2.3