luxferre/BFG
1
0
Fork 0
Code Actions Activity

updated readme about gophers://

Browse Source
This commit is contained in:
Luxferre
2024-10-06 19:18:59 +03:00
parent 4c12afe47e
commit 2c70083bf7
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.gmi
+6 -1
View File
@@ -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. 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. 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 ## Credits