From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Re: fqa: request for requests
Date: Sun, 17 Jan 2021 23:00:49 +0100 [thread overview]
Message-ID: <CAFSF3XMBQTJoeicEz0auHViE7m2yJuMLxwb2TO1H_3GabYccGA@mail.gmail.com> (raw)
In-Reply-To: <20210117201113.0a10783d@gmx.de>
eckart, what's the problem, we can all have a teambuilding event at
some gulag now!
and if you can't look over this superficial shit then you're wrong here anyway.
On 1/17/21, Eckard Brauer <eckard.brauer@gmx.de> wrote:
> as that discussion seems to suck here for a longer time, I'd throw in
> my 2 cents too.
>
> There are 2 very good reasons I read that list for (I'm not yet in a
> position to attend in the form of a writer, as I currently can't
> contribute much): The technical brilliance in a (for me) very
> interesting topic and it's humour, sometimes black and close to the
> borders, but usually far from politically correct-isms.
>
> First of that remains, but if the list is going to change to one of
> those softwashed and political-correct-dogmatic do-gooders lists, it
> starts to read more like a communist manifesto or the like, something I
> won't read for sure in my sparetime. That would degrade the before
> first level tech topics to 2nd level, and install or enforce a sort of
> wording check barrier at 1st level.
>
> Regarding the mentioned "shoah jokes" - it's not my sort of humour, but
> please keep in mind, that doing jokes with such topics is usually not
> really an expression of fun with that topics, but more one of shock or
> as a try to cope with the shock of something unbelievable, unthinkable
> or unimaginable. Nobody would usually expect people here to justify what
> happened in Shoah, even if we don't know personally, and as long as it
> doesn't take over the common language use here, I'd rather read even
> Shoah jokes (or other maybe inappropriate sentences) that way and keep
> discussions on political correctness of speech far outside.
>
> Up to just last week I was glad to learn from you all, since the start
> of exact this discussion it started to taste damned frowsty...
>
next prev parent reply other threads:[~2021-01-17 22:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 7:47 [9front] " Stanley Lieber
2021-01-15 8:52 ` Rodrigo G. López
2021-01-15 9:28 ` Daniel Morandini
2021-01-15 9:50 ` roy niang
2021-01-15 10:32 ` hiro
2021-01-15 11:18 ` roy niang
2021-01-15 10:49 ` Daniel Morandini
2021-01-15 10:56 ` hiro
2021-01-15 12:17 ` Thaddeus Woskowiak
2021-01-15 13:19 ` hiro
2021-01-15 15:39 ` Thaddeus Woskowiak
2021-01-15 15:35 ` Stanley Lieber
2021-01-15 11:33 ` Sigrid Solveig Haflínudóttir
2021-01-15 13:37 ` Juan Cuzmar
2021-01-15 16:13 ` rgl
2021-01-15 15:38 ` Calvin Morrison
2021-01-15 18:33 ` Stuart Morrow
2021-01-15 19:25 ` William Gunnells
2021-01-15 20:18 ` hiro
2021-01-16 0:41 ` qwx
2021-01-16 2:50 ` sl
2021-01-15 20:41 ` [9front] " Anthony Martin
2021-01-15 22:18 ` William Gunnells
2021-01-15 22:45 ` Sigrid Solveig Haflínudóttir
2021-01-16 2:49 ` sl
2021-01-15 22:57 ` Eli Cohen
2021-01-16 2:42 ` sl
2021-01-17 1:06 ` Anthony Martin
2021-01-17 13:23 ` hiro
2021-01-17 19:11 ` Eckard Brauer
2021-01-17 22:00 ` hiro [this message]
2021-01-18 9:24 ` Eckard Brauer
2021-01-18 10:36 ` Rodrigo G. López
2021-01-18 10:56 ` hiro
2021-01-18 12:57 ` Eckard Brauer
2021-01-18 2:57 ` sl
2021-01-16 10:05 ` [9front] " Kemal
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=CAFSF3XMBQTJoeicEz0auHViE7m2yJuMLxwb2TO1H_3GabYccGA@mail.gmail.com \
--to=23hiro@gmail.com \
--cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).