help: Drop outdated "Zulip in a terminal" help page.

help/include/sidebar_index.md

@@ -130,7 +130,6 @@
 
 ## Apps
 * [Desktop installation guides](/help/desktop-app-install-guide)
-* [Zulip in a Terminal](/help/zulip-in-a-terminal)
 * [Supported browsers](/help/supported-browsers)
 * [Connect through a proxy](/help/connect-through-a-proxy)
 * [Use a custom certificate](/help/custom-certificates)

help/supported-browsers.md

@@ -26,4 +26,3 @@ Zulip is supported by most browser-based multi protocol desktop chat apps like
 ## Related articles
 
 * [Desktop installation guides](/help/desktop-app-install-guide)
-* [Zulip in a Terminal](/help/zulip-in-a-terminal)

help/zulip-in-a-terminal.md

@@ -1,25 +0,0 @@
-# Zulip in a terminal
-
-At present, there are a few alpha-quality implementations of a terminal
-client for Zulip:
-
-* [Zulip Terminal](https://github.com/zulip/zulip-terminal) provides a
-terminal interface for Zulip using [Urwid](http://urwid.org). It is
-written in python and is being very actively developed; feedback and
-bug reports are very welcome!
-
-* [BarnOwl](https://github.com/aglasgall/barnowl/tree/zulip) is a
-multi-protocol terminal client for various chat systems, written in
-Perl.  [BarnOwl itself](https://barnowl.mit.edu/) is very mature
-software, and the Zulip integration has been used for a few years, but
-it isn't integrated into the mainline branch and needs work on
-documentation.
-
-* [Snipe](https://github.com/kcr/snipe) is relatively new
-multi-protocol client for various chat systems, built on Python 3 and
-asyncio.
-
-Zulip's web and mobile apps use the same REST API that we publish in
-our [API documentation](/api), as do all three of these terminal
-clients, so it should require only client-side work to build a
-high quality terminal-based app for Zulip.