From: Alexis <flexibeast@gmail.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: SunOS 4 in 2024
Date: Thu, 14 Mar 2024 10:28:53 +1100 [thread overview]
Message-ID: <87h6h93e4q.fsf@gmail.com> (raw)
In-Reply-To: <CAEdTPBcNU8tm7OFubw_CjHGfN5RF5X+sQP4JHDSwa-hTEE1gkg@mail.gmail.com> (Henry Bent's message of "Wed, 13 Mar 2024 16:59:02 -0400")
Henry Bent <henry.r.bent@gmail.com> writes:
> Thank you, I just subscribed to sun-rescue. I have greybeard
> syndrome
> about Discord - I just don't trust that it's going to be a
> useful resource.
i'm dismayed by the extent to which so many IT communities have
moved to Discord[a] for documentation and tribal knowledge:
"Discord, or the Death of Lore"
-- http://ascii.textfiles.com/archives/5509
"Why you shouldn't trust Discord"
--
https://cadence.moe/blog/2020-06-06-why-you-shouldnt-trust-discord
Alexis.
[a] As distinct from _Discourse_, which i generally like as a
discussion/forum platform, and which i wish more IT communities
were using instead of Discord.
next prev parent reply other threads:[~2024-03-13 23:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 20:12 [TUHS] " Henry Bent
2024-03-13 20:23 ` [TUHS] " Erik E. Fair
2024-03-13 20:49 ` Kevin Bowling
2024-03-13 20:59 ` Henry Bent
2024-03-13 23:28 ` Alexis [this message]
2024-03-13 23:39 ` Henry Bent
2024-03-14 0:44 ` Alexis
2024-03-14 13:49 ` Theodore Ts'o
2024-03-13 21:27 ` Will Senn
2024-03-13 21:31 ` Henry Bent
[not found] ` <E4752C7E-2799-4978-B221-9DB86F872C6A@baugh.org>
2024-03-13 21:56 ` Henry Bent
[not found] ` <F3E036CF-277C-4B2B-9335-D42F5ABAFD6B@baugh.org>
2024-03-13 22:09 ` Henry Bent
[not found] ` <54A3AD3C-1296-41EB-8D7B-E940AF2740CD@baugh.org>
2024-03-13 22:23 ` Henry Bent
2024-03-14 0:40 ` Alan Coopersmith
2024-03-14 0:51 ` segaloco via TUHS
2024-03-14 20:23 ` Earl Baugh
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=87h6h93e4q.fsf@gmail.com \
--to=flexibeast@gmail.com \
--cc=tuhs@tuhs.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).