++++++++++++++++++++++++++++++++++++++++++++++++++
+ Gutenborg v0.2 released
++++++++++++++++++++++++++++++++++++++++++++++++++
+- Support for plain text entries
| Now I'm back into phlogging it became apparent how
| imperative it was to Gutenborg to support its protocol
| also in plain text entries (type 0). And now it does!


+- Want a new name for "phlogging"
| I don't mean to disrespect Gopher in any way, quite
| the contrary: I choose it for supporting Gutenborg
| because I really appreciate it, but I'm experimenting
| with this thing of releasing new software and new
| technologies and I believe **naming** is a very
| important aspect of it. See *Tcl*, for instance, and
| compare to much more catchy names like Python, Ruby
| or even **Go** (at least this last name is an imperative,
| right?).
|
|
| I'm already calling the client simply *Gutenborg*, the
| protocol *Gutenborg Protocol* (it's going to be
| more than simply markup language, I hope), the Gutenborg
| enabled "Gopherholes" *GutenSites* (I like that *guten*
| means "good" in Deutsch), but "phlog" is missing its
| proper equivalent.
|
| Should I use "glog"? Man, it sounds terrible...


+- Gemini
| Recently I wrote to some people that, about **Gemini**,
| *I "dislike" it using HTTP as transport protocol*. I
| absolutelly don't mean I don't find Gemini itself a
| very neat project. The opposite: I see Gemini as a
| wonderful addition to the internet in general. It's
| just that I, personally, am still trying to find a
| better way (than HTTP). But about the decision to use
| HTTP, it's  a quite smart one, since it's nice to have
| all the tools already built, like downloaders and proxies
| and libraries in general for almost every conceivable
| language (even assembly).
|
|
| (After I feel Gutenborg is "finished enough" my next
| goal is to build my own Gemini client over Blipt!.)