# Bigger scheme - sam's station - TinyLog

           /       \       /
    k --- a         b --- f
   /       \       /       \
           me --- l         i
   \       /       \       /
    j --- c         d --- e
           \       /
            g --- h

## 2026.08.23 16:42 +0200
I wonder why it doesn't seem to be a thing in the Nex universe to have
an integrated feed as server's core functionality. As the protocol
lacks any headers it's difficult to say when a file was changed for
the last time (unless you're the server sitting on top of it and
having an access to all file stat information.  I think having Google
everywhere for the last two decades created a blind spot for an
important aspect of any system: discoverability. The average person is
more likely to give up before they even start looking.

Then there's the Catch 22-esque "need to check if I can write before I
send a new post, but at the same time my checking can cause 'too many
requests' and effectively block me from writing to a file". Damned if
I do, damned if I don't.

## 2026.08.23 01:20 +0200
The first weekend in a while with weather in a comfortable temperature
and humidity bracket.
I think I should eventually add an 'About me' page, as no standard way
of communication between citizens here is known to me, and my RTC
address isn't routeable anymore.

I read m15o's blog (I guess it's a blog), they mentioned a lot of
things close to my nerd heart: ed, acme, K&R and Forth book, writing
their own editors and languages -- kind of stuff I expect to see often
in the valleys and hollers of smolnet, but sadly stumble upon
extremely rarely.

## 2026.08.21 21:57 +0200
Goodish weather, an okay workday aside from going to the office.
In other news:
Proof of concept for chess-over-nex is out (so far tested only between
two URLs at my station)
=> /shore/samhunter/code/nex-chess  Chess-over-Nex
=> /shore/samhunter/blog/2026/08/21.txt More about

Also - my litte page editor for shore, with r/o check:
=> /shore/samhunter/code/nexedit  Nex page editor

## 2026.08.19 15:31 +0200
Spent 15 minutes frantically looking up the documentation, to get
parsed log dates into the correct TZ, only to find out the system (not
my system) never actually stated what timezone it uses.
In the end it was just invoking it with `TZ=CEST ./script`...

## 2026.08.18 23:32 +0200
15-character limit for filenames makes the nice idea of having a
header and a list of files under it less attractive.
It becomes tricky to keep the "links" under the header
readable/searchable.  I guess getting deeper than 1, maybe 2 levels of
subdirectiories is a questionable idea here.
Well, when in Rome, do as the Romans do.

## 2026.08.18 21:39 +0200
Got the "retrieve-edit-send" loop working in a script.
Next "station" - transparent editing of currently displayed Nex page
in the browser

## 2026.08.18 15:45 +0200
So far it's a smooth ride. The protocol itself is (and I rest my
case, until I die on this hill) a bit simplistic and far from
anything anyone sane would call "secure", but I understand its
charm - updates over NPS and .header files are really neat.

## 2026.08.18 12:03 +0200
My Nex experiment went pretty well, so far.
Let's see what will it take to run a small station here.

=> /shore/samhunter/  Back