From: "nick" <nick@nicholasjohnson.ch>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"René Scharfe" <l.s.r@web.de>,
git@vger.kernel.org
Subject: Re: Git Privacy
Date: Mon, 17 Jul 2023 22:49:42 +0000 [thread overview]
Message-ID: <CU4TBVU6DREW.ZZDV1JX2BNGV@anonymous> (raw)
In-Reply-To: <20230717205750.GA3901704@mit.edu>
Theodore Ts'o wrote:
> It might also be worth pointing out that someone still might be able
> to figure out information from when a branch gets pushed to a git
> repo.
Github and other forges are actually known to track this information.
> [...]
>
> Which is why, quite frankly, I'm a bit dubious about the whole "I must
> obfuscate the time zone from which I am operating", as something
> that's really worth the effort, since it has a lot of downsides, and
> if the user is not careful, they may end up leaking information about
> when they are active anyway....
I'm fine with the argument against that it causes breakage, but I
disagree with the idea that it shouldn't be implemented because "they
may end up leaking information about when they are active anyway".
That is a defeatist argument that applies to many privacy technologies
that exist. Taken to its logical conclusion, it says "Let's not try to
improve privacy ever because the same information may be obtainable in
other ways." One has to start somewhere.
next prev parent reply other threads:[~2023-07-17 22:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 16:27 Git Privacy nick
2023-07-13 17:11 ` Junio C Hamano
2023-07-14 9:22 ` nick
2023-07-14 16:45 ` Junio C Hamano
2023-07-15 4:32 ` nick
2023-07-16 11:47 ` René Scharfe
2023-07-16 22:52 ` nick
2023-07-17 2:36 ` Junio C Hamano
2023-07-17 2:57 ` Junio C Hamano
2023-07-17 5:36 ` nick
2023-07-17 20:57 ` Theodore Ts'o
2023-07-17 22:49 ` nick [this message]
2023-07-17 16:37 ` Junio C Hamano
2023-07-16 23:07 ` nick
2023-07-16 23:27 ` Jason Pyeron
2023-07-17 4:20 ` nick
2023-07-18 21:59 ` brian m. carlson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CU4TBVU6DREW.ZZDV1JX2BNGV@anonymous \
--to=nick@nicholasjohnson.ch \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=l.s.r@web.de \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).