From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Attila Lendvai <attila@lendvai.name>
Cc: Ian Eure <ian@retrospec.tv>, guix-devel <guix-devel@gnu.org>
Subject: Re: rewriting history; Was: Concerns/questions around Software Heritage Archive
Date: Mon, 18 Mar 2024 11:51:45 +0100 [thread overview]
Message-ID: <87r0g73j9a.fsf@pelzflorian.de> (raw)
In-Reply-To: <iytrYuvr9BcPdWG17PDP5SXyjrZzwBGx1sbh0BVcDZ8PAifSIMdPXPbuhhDu-2woPlaWmEWnSt09h4OravmRRBrMB5uDlXYtKtI0egEQX_k=@lendvai.name> (Attila Lendvai's message of "Mon, 18 Mar 2024 00:10:52 +0000")
The guix-daemon does the hashing, so guix-daemon would have to be fixed
to override integrity checks (and it would have to be patched
retroactively in every time-travel). Noone likes touching guix-daemon
(until it is rewritten in Guile), so I can imagine it would be
frustrating.
Now ftfy is not in Guix, but if Software Heritage deleted the data,
their customers might be equally frustrated. It is SWH’s obligation to
delete the data, but looking at how rare GDPR action is and how
frequently Icecat’s TPRB add-on lays bare GDPR violations, if they do
not follow the obligation, there likely will not be legal action or the
legal action can be dismissed somehow.
The problem is, such inaction by SWH may be relevant for Guix’ Code of
Conduct, as pointed out by MSavoritias.
Regards,
Florian
prev parent reply other threads:[~2024-03-18 10:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 0:10 rewriting history; Was: Concerns/questions around Software Heritage Archive Attila Lendvai
2024-03-18 10:10 ` MSavoritias
2024-03-18 11:26 ` Simon Tournier
2024-03-18 12:08 ` Daniel Littlewood
2024-03-18 21:14 ` Tomas Volf
2024-03-19 10:04 ` Attila Lendvai
2024-03-18 13:35 ` Andreas Enge
2024-03-18 14:03 ` MSavoritias
2024-03-18 14:19 ` Andreas Enge
2024-03-18 14:33 ` MSavoritias
2024-03-18 15:14 ` Andreas Enge
2024-03-18 15:34 ` MSavoritias
2024-03-22 22:48 ` indieterminacy
2024-03-18 10:51 ` pelzflorian (Florian Pelz) [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0g73j9a.fsf@pelzflorian.de \
--to=pelzflorian@pelzflorian.de \
--cc=attila@lendvai.name \
--cc=guix-devel@gnu.org \
--cc=ian@retrospec.tv \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).