Github messages for voidlinux
 help / color / mirror / Atom feed
From: abenson <abenson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] fortune-mod: Consider entire or partial patching out of "offensive jokes" module
Date: Wed, 30 Mar 2022 23:40:47 +0200	[thread overview]
Message-ID: <20220330214047.rlynuPzGIZnwbrCaNN005NQwkiCmAkcg8a0438GlZCg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36417@inbox.vuxu.org>

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

Closed issue by Sigma-One on void-packages repository

https://github.com/void-linux/void-packages/issues/36417

Description:
`fortune-mod` by default includes the so-called "offensive jokes" module, installed in `/usr/share/fortunes/off`. This includes quite literal databases of racist, misogynist, homophobic, and more quotes, which probably are not a good idea to include in this day and age and I would suggest patching them out for both PR and ethical reasons.

Potential solutions are either to remove the entire "offensive jokes" module, or modify it to remove the worst offenders as it does also include regular dark humour which is not intended to discriminate against a specific already discriminated against group (albeit is, obviously, dark humour, and could possibly be worth splitting into a separate optional package?).

Other distributions such as Debian include this module in it's own package, however I do not think this would be necessary, as those who for whatever reason desire to have these highly discriminatory "jokes" can trivially write a template and build a module package for their own use.


      parent reply	other threads:[~2022-03-30 21:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30 11:01 [ISSUE] " Sigma-One
2022-03-30 14:06 ` paper42
2022-03-30 14:59 ` leahneukirchen
2022-03-30 21:40 ` abenson [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=20220330214047.rlynuPzGIZnwbrCaNN005NQwkiCmAkcg8a0438GlZCg@z \
    --to=abenson@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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).