🚀 go-pugleaf

NNTP and article cancellation don't seem to work together; I don't
know if the problem is that the local "rn" and "vnews" are stupid and
don't understand how to tell when an article is yours, or the NNTP
software is stupid and doesn't understand this.  So....

>(Note that S5R3 shared memory can't be write-protected;
>this may have had something to do with their decision not to use
>it....)

Not true; it can be write-protected, so that probably wasn't what
made them decide not to use it.  There may have been other problems;
e.g., using S5 shared memory would require the C startup code to find
and map in the library, and they may not have wanted to do that, or
they may have decided it was too much work to arrange that the
library be mapped in at a particular address (which their shared
library implementation requires).