From 2c70083bf71bf058c07892d6224a174d5100e5f7 Mon Sep 17 00:00:00 2001 From: Luxferre Date: Sun, 6 Oct 2024 19:18:59 +0300 Subject: [PATCH] updated readme about gophers:// --- README.gmi | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/README.gmi b/README.gmi index c7f8473..23424bc 100644 --- a/README.gmi +++ b/README.gmi @@ -178,7 +178,12 @@ Alternatively, you can do a proposal in the "Issues" section or even create a pa However, one of the BFG's goals is to stay under 1000 SLOC no matter what. If you want feature creep, feel free to switch to more suitable clients like Lagrange. -### +### Why does a Gopher-over-TLS (gophers:// URL) resource still show plain gopher:// links? + +Due to a limitation of the Gopher-over-TLS protocol itself, we cannot determine if the Gophermap entry points +to a plain Gopher or a Gopher-over-TLS resource. Hence, only the links belonging to the same host/port pair +that was already opened with a gophers:// link are displayed as gophers:// links. Everything else needs to be +adjusted manually for now. Sorry for the inconvenience. ## Credits