Gopher over TLS (gophers://)

[orgcontrib]

Here is my related Grok Q&A: chat.
Use case (my own setup): fedornicus.

[orgcontrib]

@skyjake, you rock. Kudos for the quick reaction.
I'm so excited and can't wait for the next release.

[orgcontrib]

🤔 Lagrange 1.21.2

dacbarbos@vivobook:~$ tail -15 /var/gopher/NEWS.dir/2026.txt
2026-09-01

    - I just tested the newly released Lagrange 1.21.2.
    - I hereby confirm that my issue (#798) was resolved, yay!
    - Lagrange implemented support for the "gophers://" URL scheme.
    - Gopher over TLS is no longer limited to the ncgopher client.
    - The catch: it's all very new and further (re)thinking might be needed.
    - One obvious issue is the lack of auto-switching between plain/secure.
    - Current implementation assumes constant use of TLS schema for all links.
    - That breaks the normal navigation, where some/most links are insecure...
    - I am no longer sure that my analogy with HTTP/S was "well-chosen".

YYYY-MM-DD

    - Next news article/post goes here
dacbarbos@vivobook:~$ 

[orgcontrib]

BTW, I used the AppImage release b/c FlatHub need some time.

dacbarbos@vivobook:~$ flatpak info fi.skyjake.Lagrange

Lagrange - A Beautiful Gemini Client

            ID: fi.skyjake.Lagrange
           Ref: app/fi.skyjake.Lagrange/x86_64/stable
          Arch: x86_64
        Branch: stable
       Version: 1.21.1
       License: BSD-2-Clause
        Origin: flathub
    Collection: org.flathub.Stable
  Installation: system
Installed Size: 7.7 MB
       Runtime: org.freedesktop.Platform/x86_64/25.08
           Sdk: org.freedesktop.Sdk/x86_64/25.08

        Commit: a91e0e42c8962a154f147b1b1a83f4f7f0473ddf4cc11e6ca51bcd8cdd2d302f
        Parent: 6bda1b15c8eac4d0282e6a755e0212d486ff001fe61f43a7f582da3ded6387d0
       Subject: lagrange: Update lagrange to 1.21.1 (79c96693c819)
          Date: 2026-09-03 17:24:23 +0000
dacbarbos@vivobook:~$