On 2025-01-12, Bozo User wrote:
[Cross-posting to
news:comp.infosystems.www.misc just in case, but
setting Followup-To: comp.misc so as to keep the thread there.]
> Once you get a Gopher/Gemini browser, among yt-dlp, the web can go away.
While I do appreciate the availability of yt-dlp, I feel like
a huge part of the reason Chromium is huge is so it can support
Youtube. Granted, there doesn't seem to be as many DSAs for
video software (codecs and players) [1], but it's still the
kind of software I'd rather keep at least in a container.
[1]
news:linux.debian.announce.security (Not that I see much reason to listen to a video blogger talk
for fifteen minutes to convey the same information I can get
from five minutes of reading in the first place. A relative
of mine watches most of videos at double speed, but I don't
have that kind of fast listening skill myself, alas.)
Perhaps more important is that the Web can be understood as
a bunch of interlinked resources identified by URIs. And even
though modern browsers might fail to handle some of them,
traditional ones (like Lynx and, reportedly, SeaMonkey) still
support things like news:, mailto:, gopher:, and even ftp:.
> Try these under lynx:
> gopher://magical.fish
> gopher://gopherddit.com
> gopher://sdf.org
> gopher://hngopher.com
> gemini://gemi.dev (head to news waffle)
By the by, what's the equivalent of wget(1) for gopher:?
I understand that a lot of website operators don't care about
making their sites easy to download (and some, like the
aforementioned Youtube, try their best to make downloading hard,
for reasons), but I still care about downloading them regardless.
Of course, I try to make my own webpages compatible with
"wget -p"; e. g.:
http://am-1.org/~ivan/qinp-2021/096.sys.en.xhtmlhttp://am-1.org/~ivan/qinp-2024/112.l-system.en.xhtml (I intend to implement Rsync access at some point as well,
though no concrete plan ATM.)
> Magical Fish it's a HUGE portal and even a 386 would be able to use
> the services.
I do, in fact, have a Am386 box on my LAN with Lynx on it, but
it won't work as I don't do NAT, preferring an application level
gateway, Polipo, instead. (Reasoning vaguely along the lines
that I'd rather have a proxy crash, than kernel.) Polipo, though,
only supports HTTP; as well as CONNECT, but Lynx can't use that
for accessing gopher:. (Squid provides HTTP access to ftp: and,
IIRC, gopher:, but it's been a decade since I've last ran it.)
> You have a news source, a translator, stock prices, weather,
> wikipedia over gopher, Gutenberg, torrent search...
Is Wikipedia over gopher any better in Lynx than Wikipedia over
HTTP? Same for Gutenberg.