My latest version of my harder.lisp board, 3harder is pretty neat. I
had the thought to use it for working with my phlog posts as well,
which I did not quite get to yet, but I am happy regardless
irregardlessly.
Motivations include that I don't want to go outside lisp, and me
breaking up with emacs and orgmode yet again*. And I am somewhat
happy hosting an eepsite. I haven't formed a technical view of i2p
vs tor yet.
I think my latest 3harder.lisp is starting to be usable enough that
I can live my dream of it being upstream of my phlog. It's not
sensible yet (in the inetd sense), but baby steps.
It changed quite a lot. It used to #|DANGER COMMON LISP STANDARD
JARGON AHEAD|# #'read-char, then #'read what-is-then-asserted-to-be-
an-alist, then #'read-line a newline terminated string, which was
more in line with the gopher rfc. Now however it finishes with a
#'read as well. I changed error handling (sure let's call this a
'change') in order to avoid the bizarre headaches I believe were
from #:usocket screwing with standard lisp condition checking.
I added a lisp #:usocket based tiny client as well, though it had
been a while since I used #'set-dispatch-macro-character and I have
failed to write a macro that can be used recursively, which is a
hassle. Feel free to send me commentary on that, or post it
publically on my eepsite lisp board, lisp gods.
On the topic of abandoning orgmode, basically I prefer
reverse-double-embedding C in ecl and just using common lisp as
compares to orgmode. Using orgmode + C is basically like saying
languages couldn't get better than C, which is not right. They
couldn't get better than lisp.
One exciting possibility is using talking to my item-type-7 lisp
idiom eepsite gopher as a network-lisp-file-er. Definitely I need to
somehow strongly consistently multihome it, and add a few things for
that to be a really good idea, but it is kinda a cool idea already.
Since my minor client can talk to it more or less good enough,
except for the horrible lack of read-time recursion, I am using it
already. I should really delete these mountains of garbage messages
I have sent to myself in anticipation of ANYONE EVER doing the
following:
```
proxychains4 lynx \
"
gopher://pqev3za2ehlmb4plp5tcrsa77655t5ymk3fng356qhlgcxersdma.b32.i2p/77nil"
```
Which can then be searched (nil = as a search filter matches everything
though you can also post to it) in the gopher item type 7 lynx sense.
Searching for nil just gets everything in the topic. a specific topic
((open . bsd) (is . great)) for example replaces nil in the 77nil part
of the lynx gopher item specifier. 77 is not a typo, lynx wants one and
I want one. You would have to navigate to a different topic in lynx.
I have worlds more of thoughts on this topic. I will get back to
eclcblas soon too, no fear. But I wanted to precipitously segue into
how great the gopher is always, but also now.
I think as of at least this post I've invalidated myself as an emacs
guru, but this weekend I may try looking at jynx's undo-tree-mode
elisp escapade, whom I am also mentioning because I look forward to
the reading of.
I want to explore non-double-g-ing the word phloging like Robert. It
somehow reminds me of the correct pronounciation of the standard's
#'macrolet. He also has an interesting sounding reading list.
And jns' radio silence (and ascii art), and the gopherhole in Japan.
There are many people phloging as you know if you are reading this.
My code is going up in 1common-lisp/ eventually, you are welcome to
it in the gnu agplv3 license.
