My accomplishments 2004.September:
<ul>
  <li>Sep.01-09: Overhauled my system for keeping track of Yahoo! Mail
account names and passwords, so when I'm running my spider I don't have
to manually copy&paste the login information every time the spider switches
accounts. Using this new capability, and writing more code to automate more
of the junctures between the various tools, I had my spider automatically
scan several thousand collected spam (UBE = Unsolicited Bulk E-mail), or
if you want the precise figures, 7360 messages totaling 47.6 megabytes, to
collect the most recent Received: line (presumably showing the last-relay
IP number) and save to a local file, so that
later I can use my Received-line parser to collect the corresponding IP
numbers to see if I have CTW data for each, so that eventually I can use
that info to file complaints about all that immense amount of spam.</li>
  <li>Sep.13-22: Wrote software to set up an enumeration (in the Java sense)
of all the Received: lines in all the files of archived e-mail on my
Unix shell account, whereby it returns successively each Received: line
in the current file then automatically switches to the next file when the
next request is made. Wrote mostly-one-pass rule-driven parser,
and wrote a set of rules
for parsing Received: lines from e-mail headers. Used the enumeration of
Received: lines to develop and test the new parser. Wrote software to make
enumeration of the several files containing Received: lines which my spider
had collected Sep.01-09, from several thousand Yahoo! Mail spam I've received
on Yahoo! Mail since June when Yahoo increased the storage limit from 6MB
to 100MB allowing me to keep the immense volume of spam long enough to
perhaps fully process it, then tested the new parser on those as well.
Note: This parser matches parts of a rule
against parts of the string being parsed, making sure exactly one rule
matches each parsed string, but doesn't yet produce output copying
key parts of the string to a formal standard structure.</li>
  <li>Sep.23: Revamped my main WAP (Wireless Access Protocol, for tiny-screen
devices such as cellphones) page to be top level of information about
my search for employment, the start of an ongoing project ...</li>
  <li>Sep.24: Designed HTML forms for small screens, for flashcard drill,
specifically for <a href="../formrol.html">reading out loud</a> (with tutor)
and <a href="../formmw.html">fill in the missing word</a> (student alone),
and had other people look at them on-screen to verify they are acceptable
(key text large enough to read easily, layout not too complicated).
Hey, what do <strong>you</strong> think of those sample HTML forms?
Take a look and <a href="ContactMe.html">tell me</a> your opinion.</li>
  <li>Sep.25-26: Set up master deck of the 1494 most-common English words
of more than one letter for students learning how to read out loud.
Wrote new CGI software to allow logged-in tutors to create accounts for
their students. Ported my "all but one" flashcard-drill algorithm for reading
out loud, formerly implemented only on my Macintosh Plus, to run under CGI
with this new login method, using the <a href="../formrol.html">first</a>
of the HTML forms from Sep.24.</li>
  <li>Sep.28: Demonstrated my "all but one" flashcard-drill program for
several people, both the read-out-loud part with the new easy-to-read
form and the missing-word part still as it was before. Later that day
after I returned home, modified the missing-word part of the program to
use the 
<a href="../formmw.html">second</a> of the new forms from last Friday,
in preparation for the next demo.</li>
  <li>Sep.30: Demonstrated missing-word part of program with large text.
Upgraded English-to-Spanish part of program to likewise have large text.</li>
</ul>