From: Ulrich Mueller <ulm@gentoo.org>
To: Robert Bridge <robert@robbieab.com>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Anti-spam for goose
Date: Thu, 21 May 2020 13:57:37 +0200 [thread overview]
Message-ID: <uk1151owe@gentoo.org> (raw)
In-Reply-To: <CA+Uub+fHJ7SMfBRPqRZZ2TVuD-eKrgccRXy0-qUWAQYD6GUiMg@mail.gmail.com> (Robert Bridge's message of "Thu, 21 May 2020 12:33:48 +0100")
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
>>>>> On Thu, 21 May 2020, Robert Bridge wrote:
> On Thu, 21 May 2020 at 09:47, Michał Górny <mgorny@gentoo.org> wrote:
>>
>> Option 1: IP-based limiting
>> ===========================
>>
> Preface this with IANAL, check with your own legal counsel...
> While IP address based methods might be attractive technically, do
> remember that an IP address is considered Personally Identifiable in
> European Data Protection law.
> The fact submissions require an action by the user will probably be
> sufficient to be explicit consent, any system storing these details should
> allow for the use to revoke their consent: If you collect anything
> personally identifiable, you will need to provide a mechanism for users to
> request the removal of all their submissions.
> Tread carefully with this project. :)
You don't have to store any IP addresses, you can store a cryptographic
hash like their b2sum (salted if necessary).
Ulrich
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]
next prev parent reply other threads:[~2020-05-21 11:57 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 8:47 [gentoo-dev] [RFC] Anti-spam for goose Michał Górny
2020-05-21 9:17 ` Toralf Förster
2020-05-21 9:43 ` Michał Górny
2020-05-21 20:07 ` Toralf Förster
2020-05-22 4:39 ` Michał Górny
2020-05-21 9:48 ` Tomas Mozes
2020-05-21 10:10 ` Michał Górny
2020-05-21 10:37 ` Tomas Mozes
2020-05-21 10:45 ` Jaco Kroon
2020-05-21 11:02 ` Michał Górny
2020-05-21 14:27 ` Jaco Kroon
2020-05-21 20:13 ` Viktar Patotski
2020-05-22 0:38 ` Alec Warner
2020-05-22 4:42 ` Michał Górny
2020-05-22 6:03 ` Michał Górny
2020-05-22 6:17 ` waebbl
2020-05-22 13:39 ` Gordon Pettey
2020-05-22 15:19 ` waebbl
2020-05-21 11:03 ` Fabian Groffen
2020-05-21 11:33 ` Robert Bridge
2020-05-21 11:56 ` Michał Górny
2020-05-21 11:57 ` Ulrich Mueller [this message]
2020-05-21 12:08 ` Michał Górny
2020-05-21 12:15 ` Robert Bridge
2020-05-21 12:25 ` Ulrich Mueller
2020-05-21 13:09 ` Kent Fredric
2020-05-21 13:16 ` Michał Górny
2020-05-21 13:41 ` Kent Fredric
2020-05-21 13:53 ` Michał Górny
2020-05-21 13:22 ` Gordon Pettey
2020-05-21 13:38 ` Kent Fredric
2020-05-21 13:49 ` Kent Fredric
2020-05-22 19:20 ` Kent Fredric
2020-05-22 19:53 ` Brian Dolbec
2020-05-22 20:01 ` John Helmert III
2020-05-23 9:40 ` Kent Fredric
2020-05-22 19:58 ` Michał Górny
2020-05-23 7:54 ` Fabian Groffen
2020-05-23 8:15 ` Michał Górny
2020-05-23 10:00 ` Kent Fredric
2020-05-22 22:13 ` Peter Stuge
2020-05-23 9:49 ` Kent Fredric
2020-05-24 13:05 ` Peter Stuge
2020-05-24 15:21 ` Kent Fredric
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=uk1151owe@gentoo.org \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=robert@robbieab.com \
/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