* No more shilling
  I am removing the horrible javascript bank-adjacent web services
  that I briefly entertained. I was induced to try being a shill
  e-celeb by a few people who insincerely wanted to be lent
  my credibility, or wanted to relate to me through zombie-like
  web service middlemen. Participating was a mistake for which I
  am sorry.
** Positive experiences
   I have to say talking to Leonardo (bluuee) has been great. He
   makes me hopeful for new generations of people of sincere
   passions to flourish. He is obviously an sdf native you already
   read.
   In my forays into the scummy web businesses, I did email two
   people. Jon Beckett
   https://jonbeckett.blog
   who is an intermittent technology writer who has graduated from
   awful subscription js services to that point in everyone's lives
   where they think Wordpress will scratch their itches. I hope to
   talk to him more about independent internet writing. (He did say
   that he will give sdf.org another look, which sounds hopeful).
   I also got a few friendly emails back from the substack author of
   https://loleen.substack.com
   ; who perfectly jovially regretted that her busy academic workload
   of the moment meant she wouldn't be able to give a collaboration
   the attention it would deserve. She substacks on the opposite
   direction of tertiary pedagogy and is a refreshingly candid
   Saskatoon humanities academy member.
** Veteran phloggers
   I feel like I should also mention the sdf phloggers who link through
   to their own/the world's larger gopher underground. I am going to
   expand my gopher onto some home turf like they do; that will also
   help me get a feeling for how and where people are digging into my
   burrow (since I don't think that's basically available through sdf).
   jns is very worth attention. I hope he can review some architecture
   for me later.
** Some programs
   This week I got a lisp shell gopher server into action I shall
   present presently. Strictly within RFC1436, I realized the notion of
   item specifiers as being a lisp-READable collection of keywords.
   This important piece of indirection obviates deviations from RFC1436
   that people sometimes want, where they feel like not enough info is
   being exchanged with a server (forbidden by RFC1436). The practice
   and simple-minded notion is normally that item specifiers refer to a
   file to be dug up and served by the server, leading to the "security
   problems common in gopher protocol" (bad implementations of gopher
   servers). Teeeechnically RFC1436 says the item specifier is not to have
   any significance to the client and hence my tags should redundantly
   occupy the the item description as well, but I am not requiring any
   action by a browser relative to the item specifier; it is just that you
   can infer an item specifier by arbitrarily collecting keywords you are
   interested in-- interestingly, obviating gopher item type 7 which is
   basically a worse way of doing this.
   Okay of the two of us I appreciate that you have not been using my
   server yet (foma.lisp). Getting that up over here is slated for this
   week's dwindling days.
** Future programs
   In my opinion, my ecl libsndfile usage is pretty handy, with a distant
   second place in my controversial SDL2 [libpng] ecl. On the other hand,
   my email client handler is useful and wonderful constantly, so I should
   probably post reflecting its trivial usefulness. Oh, granfalloon is still
   awesome, though I will add some plugins or a v1.0 of it with more
   integrated controls. I say this by way of preamble to
   Actually starting to share a little bit of what I actually do. The fact
   that there is no shared context of that hitherto is probably confusing
   for both of us. I am neither a user interface designer nor a media
   engineer; it's just that the absence of useable tools in those spaces
   draws me in to boarding over the gringo traps of its 'businesses'.