From: thetruthbeforeus@firemail.cc
To: Antony Stone <Antony.Stone@devuan.open.source.it>,
linux-kernel@vger.kernel.org, debian-user@lists.debian.org
Cc: dng@lists.dyne.org
Subject: Re: [DNG] Whitelisting?
Date: Mon, 26 Feb 2018 02:10:30 +0000 [thread overview]
Message-ID: <53257b3fde49a07ae913eb23fa0c88c5@firemail.cc> (raw)
In-Reply-To: <201802252324.51976.Antony.Stone@devuan.open.source.it>
How about you white folks stop trying to silence any that have something
other than your whitewashed opinions. Your culture sterile.
Truth:
https://www.liveleak.com/view?i=c34_1519605684
On 2018-02-25 22:24, Antony Stone wrote:
> On Sunday 25 February 2018 at 23:17:40, info at smallinnovations dot nl
> wrote:
>
>> Looking at the recent emails from throwaway mail addresses is it a
>> idea
>> to moderate all mail except the addresses that are whitelisted? It is
>> not that hard to recognize someones style of writing and ditch
>> unwanted
>> mail from the list.
>
> Good idea, I agree, but then again, how important is this particular
> list to
> people trying to peddle such opinions?
>
> I can't help feeling that the adminstrative effort in filtering out
> these
> undesirables is possibly greater than simply asking everyone to ignore
> the
> noise and wait until it goes away.
>
> Just remember "do not feed the trolls".
>
>
> Antony.
prev parent reply other threads:[~2018-02-26 2:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a9307af5b881b85c081b7aa6cd731762@firemail.cc>
[not found] ` <2673272c-189c-95a0-c2c1-02eaa763ec18@gnuinos.org>
[not found] ` <ec7d4e2f-51ac-f688-d792-2bd33df34240@smallinnovations.nl>
[not found] ` <201802252324.51976.Antony.Stone@devuan.open.source.it>
[not found] ` <20180226010014.1b9431f8@d44>
[not found] ` <CAK2MWOtVPY5HYLx+myFciGOf+fJPhS8n5rHmGJRLsULLM3J=8A@mail.gmail.com>
2018-02-26 2:04 ` thetruthbeforeus
2018-02-26 2:10 ` thetruthbeforeus [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53257b3fde49a07ae913eb23fa0c88c5@firemail.cc \
--to=thetruthbeforeus@firemail.cc \
--cc=Antony.Stone@devuan.open.source.it \
--cc=debian-user@lists.debian.org \
--cc=dng@lists.dyne.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®