commit a0c418658ad8f25c98e90307b8be358d033b6857
from: Omar Polo <op@omarpolo.com>
date: Tue Jul 20 20:07:48 2021 UTC

use raw 127.0.0.1 instead of `localhost' in the example

Gnuserland reports that on his machine `proxy http via
"gemini://localhost:1965" doesn't work, but with the raw ip works.
I've seen a similar note on the duckling-proxy readme.  Must be some
weird stuff going on on linux, anyway...

commit - 436a7ff69306d7649b88d0591fcd72f22a15818a
commit + a0c418658ad8f25c98e90307b8be358d033b6857
blob - e0e9beeddd6a9ed79ec843a37f3827c61317cfc4
blob + 4d0c2c8b823f2cf5a15beca3e205aa3f53494dc1
--- telescope.1
+++ telescope.1
@@ -777,8 +777,8 @@ It's possible to browse
 by using programs like the duckling-proxy by defining a proxy in
 .Pa ~/.telescope/config :
 .Bd -literal -offset indent
-proxy http via "gemini://localhost:1965"
-proxy https via "gemini://localhost:1965"
+proxy http via "gemini://127.0.0.1:1965"
+proxy https via "gemini://127.0.0.1:1965"
 .Ed
 .Pp
 To load