The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Alexis <flexibeast@gmail.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: SunOS 4 in 2024
Date: Thu, 14 Mar 2024 11:44:45 +1100	[thread overview]
Message-ID: <87zfv11w1u.fsf@gmail.com> (raw)
In-Reply-To: <CAEdTPBfYXHYX_PuL1Zq3Fz28b0JRY8ZmS-81zbEa_a-wB6PM+g@mail.gmail.com> (Henry Bent's message of "Wed, 13 Mar 2024 19:39:33 -0400")

Henry Bent <henry.r.bent@gmail.com> writes:

> Now, I find that there is a fragmentation happening. There are 
> those
> of us
> who still cling to mailing lists - like this one! - and those 
> who
> are
> willing to navigate the realms of increasingly compartmentalized
> other
> forms of community, Discord included. The fact that there is not 
> a
> recognized central repository of unpaid support for a product, 
> like
> sun-managers, I find to be frustrating.

i basically agree. i won't dwell on this too much further because 
i
recognise that i'm going off-topic, list-wise, but:

i think part of the problem is related to different people having
different preferences around the interfaces they want/need for
discussions. What's happened is that - for reasons i feel are
typically due to a lock-in-oriented business model - many 
discussion
systems don't provide different interfaces/'views' to the same
underlying discussions. Which results in one community on platform 
X,
another community on platform Y, another community on platform Z
.... Whereas, for example, the 'Rocksolid Light' BBS/forum 
software
provides a Web-based interface to an underlying NNTP-based system,
such that people can use their NNTP clients to engage in forum
discussions. i wish this sort of approach was more common.


Alexis.

  reply	other threads:[~2024-03-14  0:45 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
2024-03-13 23:39       ` Henry Bent
2024-03-14  0:44         ` Alexis [this message]
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=87zfv11w1u.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).