public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Anti-spam for goose
Date: Sat, 23 May 2020 07:20:22 +1200	[thread overview]
Message-ID: <20200523072022.5eb5e4e1@katipo2.lan> (raw)
In-Reply-To: <496f9d713dc1d890d8af717c77429faac20912e1.camel@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]

On Thu, 21 May 2020 10:47:07 +0200
Michał Górny <mgorny@gentoo.org> wrote:

> Other ideas
> ===========
> Do you have any other ideas on how we could resolve this?

And a question I'd like to revisit, because nobody responded to it:

- What are the incentives a would-be spammer has to spam this service.

Services that see spam *typically* have a definable objective.

*Typically* it revolves around the ability to submit /arbitrary text/,
which allows them to hawk something, and this becomes a profit motive.

If we implement data validation so that there's no way for them to
profit off what they spam, seems likely they'll be less motivated to
develop the necessary circumvention tools. ( as in, we shouldn't accept
arbitrary CAT/PN pairs as being valid until something can confirm those
pairs exist in reality )

There may be people trying to jack the data up, but ... it seems a less
worthy target.

So it seems the largest risk isn't so much "spam", but "denial of
service", or "data pollution".

Of course, we should still mitigate, but /how/ we mitigate seems to
pivot around this somewhat.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2020-05-22 19:20 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
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 [this message]
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=20200523072022.5eb5e4e1@katipo2.lan \
    --to=kentnl@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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