From: Dan Cross <email@example.com>
To: Grant Taylor <firstname.lastname@example.org>
Subject: [COFF] Re: [TUHS] Re: the wheel of reincarnation goes sideways
Date: Wed, 2 Aug 2023 12:07:13 -0400 [thread overview]
Message-ID: <CAEoi9W7RUfsoGXZQjZOq5MwRi4RzQTKdxuatFDek2NFE31W33Q@mail.gmail.com> (raw)
On Tue, Aug 1, 2023 at 12:28 PM Grant Taylor via COFF <email@example.com> wrote:
> On 8/1/23 10:55 AM, Dan Cross wrote:
> > Interesting. I don't really get the point of the Gopher revival, to be
> > honest;
> Retro? Reminiscence?
> > sure, I get that people want non-graphical, non-ad-laden content,
> > but it sure seems like you could get something like that with the
> > web just using a text-mode browser like `lynx` or even `links` and
> > something like `gomarkdown`.
> Presumably people are creating new content to use in the newer Gopher
> sphere, etc.
> So if people are creating new content, why can't they create the same
> content in simple no-add HTML.
Exactly. There are even pre-baked things one could put together that
would serve much the same purpose. Going back to gopher et al seem
like throwing out the baby with the bathwater. A small HTTP server
that serves a little subtree of files on some random port and
automatically renders markdown or something into trivial HTML is
really all one needs.
> > It's like the people who want to use Fidonet as an "alternative"
> > to email. I mean, one can use the same protocols in parallel with
> > the mainstream services.
> I was pawing at FidoNet (or other FTNs) as an alternative to SMTP
> specifically because it was not SMTP.
Tell that to the Fidonet people. :-)
> Not that anything's wrong with SMTP to prevent it's use. My interest is
> in the form of avoiding a single protocol failure.
I don't see what the protocol has to do with it, but sure.
- Dan C.
next prev parent reply other threads:[~2023-08-02 16:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP6exY+05fStBtpZGd2HeeNf21fNXeKUTwBV0h5-1YczwFfirstname.lastname@example.org>
2023-03-08 19:52 ` [COFF] Re: [TUHS] " Dan Cross
2023-03-08 20:18 ` [COFF] " Tom Ivar Helbekkmo via COFF
2023-03-09 1:22 ` [COFF] Re: [TUHS] " John Cowan
2023-03-09 19:55 ` Dan Cross
2023-03-09 20:09 ` Larry McVoy
2023-03-11 20:32 ` Dan Cross
2023-03-11 23:28 ` Bakul Shah
[not found] ` <ZA+gxAePDMWK6StD@straylight.ringlet.net>
2023-03-13 22:34 ` Dan Cross
2023-07-05 21:48 ` Dan Cross
2023-07-05 23:58 ` Grant Taylor via COFF
2023-07-06 1:02 ` Dave Horsfall
2023-07-06 16:47 ` Grant Taylor via COFF
2023-07-06 2:35 ` Dan Cross
2023-07-06 4:18 ` Robert Stanford via COFF
2023-07-06 16:53 ` Grant Taylor via COFF
2023-07-06 17:54 ` Adam Thornton
2023-07-09 14:55 ` Michael Parson
2023-08-01 9:52 ` Michael Cardell Widerkrantz
2023-08-01 9:49 ` Michael Cardell Widerkrantz
2023-08-01 15:55 ` Dan Cross
2023-08-01 16:27 ` Grant Taylor via COFF
2023-08-02 16:07 ` Dan Cross [this message]
2023-08-02 20:58 ` Grant Taylor via COFF
2023-08-02 21:16 ` Dan Cross
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 \
* 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).