aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNicholas Johnson <nick@nicholasjohnson.ch>2023-07-12 00:00:00 +0000
committerNicholas Johnson <nick@nicholasjohnson.ch>2023-07-12 00:00:00 +0000
commit7a10f7779f5715cd3d005d3be33ec790f0d41d3a0937172d59983a672cc9663f (patch)
treeefb54c1c2e5e9d8380499630cbb3d8971115cb524d8170c4ba1eff212af1da02
parent384d19226f7539bc1e6dc18e8d218db6a381969a048b5027d7b1b584286241b5 (diff)
Clarify the privacy risk
-rw-r--r--README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.md b/README.md
index ef3f218..1cfcaf2 100644
--- a/README.md
+++ b/README.md
@@ -2,7 +2,7 @@
## ❌ Default Git Privacy ❌
-With only 3 commands *anyone* can find out the dates and exact times, down to the second, that a developer makes commits.
+With only 3 commands, *anyone* can find out the dates, time zones, and exact clock times a developer makes commits.
```sh
git clone <target-repo>
@@ -10,7 +10,7 @@ cd <target-repo>
git log --format=fuller
```
-Over a long enough timespan, exact commit times can be used to deduce private information about a developers life. For instance, their likely timezone and sleep patterns.
+This can leak personal information about a developer's life. The time zones reveal the developer's approximate location in the world at that time and exact commit times recorded over a sufficient timespan may be used to deduce a developer's sleep patterns for example.
## 📅 Git Timestamps 📅