The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Steve Nickolas <usotsuki@buric.co>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] FYI: Internet Old Farts Club
Date: Mon, 31 Jan 2022 21:21:33 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.21.2201312117110.3821@sd-119843.dedibox.fr> (raw)
In-Reply-To: <685fd0dc-e959-c7c1-0110-c8f55021b752@spamtrap.tnetconsulting.net>

On Mon, 31 Jan 2022, Grant Taylor via TUHS wrote:

> On 1/29/22 1:48 AM, Andy Kosela wrote:
>> I can speak only for myself, but I love that TUHS/COFF mailing lists are 
>> still _the real_ mailing lists managed the old school way.
>
> Usenet is still a thing that I use daily.

As do I.

>
>> I hate all those modern web 2.0 technologies with extremely bloated js 
>> stacks which you can only use if you have the latest version of Chrome. 
> I too dislike what the Web 2.0 world has turned into.
>
> I believe that it's possible for web pages to by dynamic via AJAX without all 
> the bloat.  Sadly this isn't done.

The solution to bloat has, sadly, tended to be "throw more CPU/RAM/hard 
drive at it".  That's one big reason WordPerfect 5.0 on a 486 is faster 
than a modern word processor on a recent i7.

<snip>

>> This is probably one of the last places on the Internet that is still 
>> preserving one of its core ideas in the 80s/90s -- plain text 
>> communication.  It has been slowly dying in the last 15 years. Text based 
>> Internet of the 80s and 90s has slowly been replaced by binary protocols 
>> and image based interaction with a computer.
>
> Usenet.

IRC. ;)

<snip>

> I'm not planing on discontinuing using mailing lists or Usenet any time soon. 
> Despite the fact that they have migrated from unencrypted to encrypted 
> communications.  Even my MUA / NUA is using encrypted connections to the 
> servers.  But /my/ /personal/ /interaction/ with my MUA / NUA hasn't changed.

I still use the same software, in many cases, I've used since the 1990s.

-uso.

  reply	other threads:[~2022-02-01  2:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27  0:36 Rich Morin
2022-01-27  1:55 ` Jan Schaumann via TUHS
2022-01-29  1:59   ` Charles Anthony
2022-01-29  2:24     ` Theodore Y. Ts'o
2022-01-29  2:36       ` Larry McVoy
2022-01-29  8:48         ` Andy Kosela
2022-01-29 17:15           ` Jon Steinhart
2022-01-29 17:20           ` Seth J. Morabito
2022-02-01  2:12           ` Grant Taylor via TUHS
2022-02-01  2:21             ` Steve Nickolas [this message]
2022-02-01  2:23             ` Larry McVoy
2022-02-01  2:31               ` Steve Nickolas
2022-02-01  2:51               ` Grant Taylor via TUHS
2022-02-01 18:19               ` Clem Cole
2022-02-01 18:24                 ` Steffen Nurpmeso
2022-02-01 12:45             ` Blake McBride
2022-01-29 17:20         ` Blake McBride
2022-01-30  1:20         ` Adam Thornton
2022-01-30  2:10           ` Will Senn
2022-01-27  2:07 ` Grant Taylor via TUHS
2022-01-27  2:40   ` Larry McVoy
2022-01-27 21:11 ` Tomasz Rola
2022-01-27  2:52 Norman Wilson
2022-01-27 23:20 ` Nemo Nusquam

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=alpine.DEB.2.21.2201312117110.3821@sd-119843.dedibox.fr \
    --to=usotsuki@buric.co \
    --cc=tuhs@minnie.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).