[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev] recognition in the 'New York Times'

From: Thorsten Glaser
Subject: Re: [Lynx-dev] recognition in the 'New York Times'
Date: Fri, 27 Jul 2018 23:17:03 +0000 (UTC)

Karen Lewellen dixit:


> Thomas this is a press moment that should not be missed.  if the reporter is
> contacted and given an education on how much Lynx can do,  imagine the
> possibilities?

There’s one very great thing they missed, though.

For example, the Groundspeak geocaching website used to have a page
load size of over 1 MiB (HTML alone), I believe they cut a hundred
or two off it by now but this is still ridiculous, yet most of the
pages renders well by lynx.

A traffic-saving use case would be to ssh to a Unix system on the
’net (for example with vx.connectbot from F-Droid on an Android
system) and use lynx remotely. That way, only the tty I/O of lynx
forwarded over ssh would be cost in mobile traffic.

Not considering protocol overhead, compression, ncurses overhead
and colours, a typical geocaching website as mentioned above is
perhaps four to five screen pages at 113x35 (my normal xterm size),
which means about 20 kB (actually way less due to borders, empty
pages, etc).

That’s a traffic saving of at least factor 10'000, if not more,
and it’s something I’ve done (I do have an Android device nowadays,
which a friend of a friend gave me out of pity, although my main
mobile phone is an 1998’s Nokia 6150 cell phone, and the Android
thingy (built 2008) has a separate SIM with an 100 MiB/month plan,
which was the lowest I could get, used only for toying around some,
so this saving is something I could use).

Perhaps someone can forward this data point, perhaps the entire
lynx-dev discussion, to that article author? (Maybe Russel, since
you found it?)

> Wish I had pine to hand :-( I'll give lynx a try, thanks.

Michael Schmitz on nntp://
a.k.a. {}#news.gmane.linux.debian.ports.68k in pine

reply via email to

[Prev in Thread] Current Thread [Next in Thread]