Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Nevin Liber <>
Subject: [COFF] Re: Anyone still using USENET?
Date: Sat, 28 Jan 2023 15:24:07 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

[moved to COFF]

On Sat, Jan 28, 2023 at 4:16 AM Andy Kosela <> wrote:

> Great initiative and idea! While I am personally not interested in reading
> USENET that much nowadays, the concept of providing free, public access to
> classic Internet services (public USENET, FTP, IRC, finger, etc.) gets all
> my praise. What happened to free, public services these days?

First off, what is stopping you from providing free, public access to those

I don't know where you are, but I have orders of magnitude more access to
freely available content and services than I ever did in the heyday of
Usenet, etc.  And for most of it, one doesn't have to be highly technical
to use it.

> Everything appears to to be subscriber pay-as-you-go based. The
> commercialization killed the free spirit of Internet we all loved in the
> 90s.

"Free" was never really true, as it required massive subsidies of
equipment, power, bandwidth and employee time, usually w/o the direct
knowledge or consent of the entities paying for it.

It reminds me of the lemonade stands I'd occasionally run as a kid, which
were "profitable" to me because mom and dad, with their knowledge and
consent, let me pretend that the costs were $0.
 Nevin ":-)" Liber  <>  +1-847-691-1404

[-- Attachment #2: Type: text/html, Size: 2165 bytes --]

      parent reply	other threads:[~2023-01-28 21:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
     [not found]   ` <086b01d93276$c3982c80$4ac88580$>
     [not found]     ` <>
2023-01-27 19:31       ` [COFF] Re: [TUHS] Re: [off-topic] " Stuff Received
     [not found] ` <>
     [not found]   ` <>
2023-01-28 21:24     ` Nevin Liber [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \

* 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).