about summary refs log tree commit diff stats
path: root/doc
diff options
context:
space:
mode:
authorbptato <nincsnevem662@gmail.com>2024-10-12 17:14:01 +0200
committerbptato <nincsnevem662@gmail.com>2024-10-12 17:19:44 +0200
commitc4a75720959a968004fec1996d6870d0874c953d (patch)
tree428407444b6aa0199060629047f5393f3b590218 /doc
parent828716e78b5b1a9fea93c2839d89e189c1fcb252 (diff)
downloadchawan-c4a75720959a968004fec1996d6870d0874c953d.tar.gz
Add `nc' tool & adjust finger/spartan to use it
Simple netcat clone, useful for portable scripts. Especially because
some netcats will close the connection as soon as I close stdin... this
one only quits when either stdout or the socket refuses new data.

Also, it uses our standard TCP connection routine, meaning it respects
ALL_PROXY. (i.e. now spartan works with socks5 too)
Diffstat (limited to 'doc')
-rw-r--r--doc/protocols.md14
1 files changed, 6 insertions, 8 deletions
diff --git a/doc/protocols.md b/doc/protocols.md
index 9fa07f06..dbf271bf 100644
--- a/doc/protocols.md
+++ b/doc/protocols.md
@@ -94,19 +94,17 @@ HTML.
 
 ## Finger
 
-Finger is supported through the `adapter/protocol/cha-finger` shell script.
-It is implemented as a shell script because of the protocol's simplicity.
-cha-finger uses the `curl` program's telnet:// protocol to make requests.
-As such, it will not work if `curl` is not installed.
+Finger is supported through the `finger` shell script. It is implemented
+as a shell script because of the protocol's simplicity.
 
-Aspiring protocol adapter writers are encouraged to study cha-finger for
-a simple example of how a custom protocol handler could be written.
+For portability, `finger` uses Chawan's `nc` tool (a very limited netcat
+clone) to make requests.
 
 ## Spartan
 
 Spartan is a protocol similar to Gemini, but without TLS. It is supported
-through the `adapter/protocol/spartan` shell script, which uses `nc` to make
-requests.
+through the `spartan` shell script, and like Finger, it uses Chawan's `nc` to
+make requests.
 
 Spartan has the very strange property of extending gemtext with a
 protocol-specific line type. This is sort of supported through a sed filter