II2II 1 hour ago

I love the idea of Gopher (even more so of Gemini), but the basic hurdle I run into is content. It feels like half of it is talking about how great gopher/gemini is, and the other half are deeply personal blogs. While the technology reflects the early days of the Internet, the content reflects the early days of blogging and social media (which came later). Rather than talking about things they are passionate about, they are talking about themselves.

  • warkdarrior 1 hour ago

    Maybe they are passionate about themselves??

  • anthk 12 minutes ago

    gopher://sdf.org and gopher://magical.fish have far more than retro-onanism.

vaporup 2 hours ago
  • anthk 2 hours ago

    Gemini it's good on legacy machines and some clients can be really barebones (awk+less), and for some security there are clients written in Go. For awk+less, do yourself a favour. Run

        unset LESSOPEN 
    

    or have it at ~/.profile.

    Reticulum it's unusable in 32 bit machines, it badly needs a Go port for nomadnet.

    On Gopher, well, lynx/sacc and maybe i2pd for some security and anonimity.

    As a start, there's:

         gopher://magical.fish
         gopher://sdf.org
    

    For gemini,

         gemini://gemi.dev it's nice.
    

    'Lagrange' covers both gemini and gopher as a client.

    You can set an HTTPS proxy for it and read news sites and blogs over Gemini.

    Just set

         stargate.gemi.dev:1994
    

    As the HTTP proxy in the settings for Lagrange.

    For the terminal guys, there's Telescope and it can use HTTP proxies as well. Read the man page.

jmclnx 1 hour ago

Why ? It is not owned and controlled by billionaires. Plus no AI slop being spammed to gopher sites.

FWIW, the same applies to gemini protocol.

  • cowlevel 53 minutes ago

    Same applies to HTTP too though