9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Lucas Francesco <lucas.francesco93@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] proposal: raze fortunes
Date: Fri, 26 Jul 2024 12:28:24 -0300	[thread overview]
Message-ID: <CAF=5iUXUrRZny21L0yZ89EtOpG=SB93aVOZq2C0Jrnm4e5zGaA@mail.gmail.com> (raw)
In-Reply-To: <ZqG9HNAIAyBgopWQ@wopr>

the patch looks good to me, i'm also in favour of removing/merging
/lib/troll and fortune.

maybe we should have an fortune tarball with the extra stuff like the
suggested ngate fortunes?
thanks!

On Wed, 24 Jul 2024 at 23:51, Kurt H Maier <khm@sciops.net> wrote:
>
> Our fortunes file is too big, most of it is boring, some of it (the
> parts that predate 9front) include bad things like joking about sex &
> abuse (there's a line that basically repurposes an old joke to accuse
> Jim McKie of sheepfucking, for instance), other parts of it (both pre-
> and post-9front) contain hitler jokes that once were edgy and now are
> stark reminders of an existential threat to modern society, and a lot of
> quotes from an ircnet which is ostensibly no-logging and can't bring
> receipts for people being quoted as being ok with being quoted.
>
> In addition, a LOT of stuff isn't even formatted correctly (lines are
> hard-wrapped at a specific line length) with the result that the
> fortunes file as it sits *doesn't even work with fortune(1)*.
>
> I started by deleting all the detritus from the Before 9front Days and
> then went through and deleted anything that didn't meet my arbitrarily
> high bar for comedy and/or poignancy.
>
> The remaining few things that DID meet my bar, but were quotes from
> ircnets, I removed anyway, because no logging!
>
> Anyway, here's my proposed replacement for /sys/games/lib/fortunes
>
> xoxo
> khm

      parent reply	other threads:[~2024-07-26 15:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25  2:49 Kurt H Maier
2024-07-25  3:03 ` sl
2024-07-25  4:47 ` qwx
2024-07-25 10:36   ` Steve Simon
2024-07-25 17:10     ` Kurt H Maier
2024-07-26  1:48   ` nepeta
2024-07-26  1:53     ` sl
2024-07-26  2:01       ` nepeta
2024-07-26  2:06         ` sl
2024-07-26  2:52     ` nepeta
2024-07-26  3:24 ` [9front] " Anthony Martin
2024-07-26  4:27   ` Kurt H Maier
2024-07-26  7:45     ` hiro
2024-07-26  8:13       ` Dave Woodman
2024-07-26 10:50 ` [9front] " Özgür Kesim
2024-07-26 15:32   ` Jacob Moody
2024-07-26 15:48     ` Stanley Lieber
2024-07-26 16:56       ` Steve Simon
2024-07-26 17:02         ` Stanley Lieber
2024-07-26 17:33         ` Dave Woodman
2024-07-26 18:04         ` Romano
2024-07-26 18:26           ` Stanley Lieber
2024-07-26 18:39             ` Steve Simon
2024-07-26 20:16               ` hiro
2024-07-26 21:19               ` Kurt H Maier
2024-07-26 23:42                 ` ori
2024-07-27 19:55                   ` [9front] proposal: raze fortunes v2 Kurt H Maier
2024-07-27 21:08                     ` sl
2024-07-27 21:29                     ` Steve Simon
2024-07-26 15:28 ` Lucas Francesco [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='CAF=5iUXUrRZny21L0yZ89EtOpG=SB93aVOZq2C0Jrnm4e5zGaA@mail.gmail.com' \
    --to=lucas.francesco93@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).