The Phlog, an introduction

Somehow I've decided to start this blog thing. Inspired by my journey into gopherspace, I've read words of people whom I don't know, and who don't know me. But I've somehow convinced myself that there is a connection, some shared idea, about what the Internet is, and I want very much to be a part of that, an active part. Since I'm not participating in the making of open-source software projects (except for my own), and I don't have any interest in user-groups or hacker-spaces, my modest contribution will be this directory of text, which I hope that I will remember to set aside time to make.

The disclaimer

What will be expressed here may be anything from mad delirious ramblings, to actual useful advice (likely mostly the former). It will be my opinion, and if something seems mean or discriminating, my intention is likely not to be mean or to discriminate. I have a tendency to use generalization and strong words to get my point across, and my point may be subtle and unfortunately drown in the bile that I spit. My opinions are my own, and they may be offensive to you, but if they are, please consider the possibility that you are may be understanding them in a way different from my intention, we may in fact be quite in agreement on most everything but the actual wording.

The method

I will write this these in vim, usually over SSH, that's not very relevant. Each entry will consist of a text-file (plaintext is beautiful) and it will be named by the ISO-8601 date (which I believe everyone should use, because it is unique enough to be recognized as such, sorts beautifully, and makes sense).


The entries of this blog (phlog, because gopher), are actually located under the www directory for my domain, hosted by nginx, so they are exposed via HTTP as well, but they are unlinked (except by http->gopher proxy) to the web. The entries are served by my Gopher server (a fun evening in node). 2017-02-04 The phlog is now served via HTTP as well, but I will continue writing in lovely plaintext and talk about the gopher-stuff I'm doing. Check out goper-lib and gopher-client on npm if you want to try out the node code I wrote for gopher.