|Original author(s)||Lou Montulli, Michael Grobe, Charles Rezac|
|2.8.9rel.1 (8 July 2018 )|
|2.9.0dev.6 (5 September 2020)|
|Written in||ISO C|
|Engine||fork of libwww|
|Operating system||Unix-like,DOS, Windows|
|Type||Text-based web browser|
Lynx is a customizable text-based web browser for use on cursor-addressable character cell terminals. As of 2020[update], it is the oldest web browser still being maintained, having started in 1992.
Lynx was a product of the Distributed Computing Group within Academic Computing Services of the University of Kansas, and was initially developed in 1992 by a team of students and staff at the university (Lou Montulli, Michael Grobe and Charles Rezac) as a hypertext browser used solely to distribute campus information as part of a Campus-Wide Information Server and for browsing the Gopher space. Beta availability was announced to Usenet on 22 July 1992. In 1993, Montulli added an Internet interface and released a new version (2.0) of the browser.
As of July 2007[update] the support of communication protocols in Lynx is implemented using a version of libwww,forked from the library's code base in 1996. The supported protocols include Gopher, HTTP, HTTPS, FTP, NNTP and WAIS. Support for NNTP was added to libwww from ongoing Lynx development in 1994. Support for HTTPS was added to Lynx's fork of libwww later, initially as patches due to concerns about encryption.
Garrett Blythe created DosLynx in April 1994 and later joined the Lynx effort as well. Foteos Macrides ported much of Lynx to VMS and maintained it for a time. In 1995, Lynx was released under the GNU General Public License, and is now maintained by a group of volunteers led by Thomas Dickey .
Browsing in Lynx consists of highlighting the chosen link using cursor keys, or having all links on a page numbered and entering the chosen link's number. Current versions support SSL and many HTML features. Tables are formatted using spaces, while frames are identified by name and can be explored as if they were separate pages. Lynx is not inherently able to display various types of non-text content on the web, such as images and video, but it can launch external programs to handle it, such as an image viewer or a video player.
The speed benefits of text-only browsing are most apparent when using low bandwidth internet connections, or older computer hardware that may be slow to render image-heavy content.
Because Lynx does not support graphics, web bugs that track user information are not fetched, meaning that web pages can be read without the privacy concerns of graphic web browsers. However, Lynx does support HTTP cookies, which can also be used to track user information. Lynx therefore supports cookie whitelisting and blacklisting, or alternatively cookie support can be disabled permanently.
Lynx accepts configuration options from either command-line options or configuration files. There are 142 command line options according to its help message. The template configuration file
lynx.cfg lists 233 configurable features. There is some overlap between the two, although there are command-line options such as
-restrict which are not matched in
lynx.cfg. In addition to pre-set options by command-line and configuration file, Lynx's behavior can be adjusted at runtime using its options menu. Again, there is some overlap between the settings. Lynx implements many of these runtime optional features, optionally (controlled through a setting in the configuration file) allowing the choices to be saved to a separate writable configuration file. The reason for restricting the options which can be saved originated in a usage of Lynx which was more common in the mid-1990s, i.e., using Lynx itself as a front-end application to the Internet accessed by dial-in connections.
Because of its refreshable braille display and text-to-speech–friendly interface, Lynx can be used for internet access by visually impaired users. As Lynx substitutes images, frames and other non-textual content with the text from
title HTML attributes and allows hiding the user interface elements, the browser becomes specifically suitable for use with cost-effective general purpose screen reading software. A version of Lynx specifically enhanced for use with screen readers on Windows was developed at Indian Institute of Technology Madras.
Lynx is also useful for accessing websites from a remotely connected system in which no graphical display is available. Despite its text-only nature and age, it can still be used to effectively browse much of the modern web, including performing interactive tasks such as editing Wikipedia.
Since Lynx will take keystrokes from a text file, it is still very useful for automated data entry, web page navigation, and web scraping. Consequently, Lynx is used in some web crawlers. Web designers may use Lynx to determine the way in which search engines and web crawlers see the sites that they develop. Online services that provide Lynx's view of a given web page are available.
Lynx is also used to test websites' performance. As one can run the browser from different locations over remote access technologies like telnet and ssh, one can use Lynx to test the web site's connection performance from different geographical locations simultaneously. Another possible web design application of the browser is quick checking of the site's links.
Lynx was originally designed for Unix-like operating systems, though it was ported to VMS soon after its public release and to other systems, including DOS, Microsoft Windows, Classic Mac OS and OS/2. It was included in the default OpenBSD installation from OpenBSD 2.3 (May 1998) to 5.5 (May 2014), being in the main tree prior to July 2014, subsequently being made available through the ports tree, and can also be found in the repositories of most Linux distributions, as well as in the Homebrew and Fink repositories for macOS. Ports to BeOS, MINIX, QNX, AmigaOS and OS/2 are also available.
The sources can be built on many platforms, e.g., mention is made of Google's Android operating system.
Edited: 2021-06-18 12:38:55