m (Add clients and fixed link for RFC) |
m (Visual edit) |
||
| Line 1: | Line 1: | ||
The Gopher protocol is a communications protocol designed for distributing, searching, and retrieving documents in Internet Protocol networks. The design of the Gopher protocol and user interface is menu-driven, and presented an alternative to the World Wide Web in its early stages, but ultimately fell into disfavor, yielding to the HTTP.[https://en.wikipedia.org/wiki/Gopher_(protocol)] | The Gopher protocol is a communications protocol designed for distributing, searching, and retrieving documents in Internet Protocol networks. The design of the Gopher protocol and user interface is menu-driven, and presented an alternative to the World Wide Web in its early stages, but ultimately fell into disfavor, yielding to the HTTP.[https://en.wikipedia.org/wiki/Gopher_(protocol)] | ||
The Gopher protocol was first described in RFC | The Gopher protocol was first described in <nowiki>RFC 1436</nowiki>. | ||
=== Providers on [[tildeverse]] === | === Providers on [[tildeverse]] === | ||
| Line 12: | Line 12: | ||
* [[tilde.team]] | * [[tilde.team]] | ||
=== Gopher clients === | |||
* [https://bombadillo.colorfield.space/ bombadillo] | * [https://bombadillo.colorfield.space/ bombadillo] | ||
* [https://thelambdalab.xyz/elpher/ elpher] (emacs client) | * [https://thelambdalab.xyz/elpher/ elpher] (emacs client) | ||
* [https://invisible-island.net/lynx/ lynx] | * [https://invisible-island.net/lynx/ lynx] | ||
Revision as of 12:23, 3 June 2021
The Gopher protocol is a communications protocol designed for distributing, searching, and retrieving documents in Internet Protocol networks. The design of the Gopher protocol and user interface is menu-driven, and presented an alternative to the World Wide Web in its early stages, but ultimately fell into disfavor, yielding to the HTTP.[1]
The Gopher protocol was first described in RFC 1436.
Providers on tildeverse
Gopher clients
- bombadillo
- elpher (emacs client)
- lynx