Gemini* and Gopher

• Personal/Opinions

  • 🔤SpellBinding: ACILOQU Wordo: ENVOI

  • hanging by a thread

• Technology and Free Software

  • RFC on e-ink readers

    I used httrack and Calibre’s ebook-convert for what I thought was the best results.

  • The in and out of it all

    Of *course* seeking without for what can only be found within leaves one without!

    Did you catch that?

    If not, feel free to do the prerequisite work that makes it obvious.

  • Internet/Gemini

    • Perhaps pure text is the best walled garden of all?

    • Perhaps we need to make knowledge difficult again

      it hit me that while people have become wisely concerned with the effect of "infinite scroll" on our psyche, their faith in what is arguably the cornerstone of "the web" prevents them from seeing that hypertext links aren't too different than infinite scroll: they're infinite click.

      Mr. Berners-Lee no doubt had the best of intentions, but simply clicking to travel between collections of thoughts is, well, *too* simple for animals whose growth is in large part dependent on making efforts.

    • Why Not Just Improve Gemini? Scroll's Approach in Diverging From Gemini

      The criticism of improving Gemini or using Markdown instead of creating your own stuff are some of the same criticisms that Gemini had early on, many of which are answered well in its FAQ. Everything in Gemini's FAQ regarding the creation of a new protocol applies here as well, but instead of not just using HTML, it's Gemini.

  • Programming

    • 👻 Who Needs a Whole-Ass Git Forge, Anyway?

      GitHub remains the defacto king of open-source project hosting. But leaving my open-source projects, which I dump a lot of time into, at the mercy of Microsoft's quarterly earnings report has struck me as unwise for a long time. There are a few other less-used hosting providers, but switching to one would just be kicking the can down the road; those quarterly earnings reports will always have their day. In the long run the most stable home for my open-source projects is under my own domain name.

      [...]

      Since I don't expose SSH publicly from my machines, and instead use a VPN between them all, this is the most secure option anyway. Adding in some monster of a codebase with its own authentication system and public SSH server would just be an increase in attack surface in exchange for probably less fine-grained access control than I have now. Overall this is much preferred.