From: telecomdigestsubmissions@remove-this.telecom-digest.org   
      
   I got an email from Garrett WOllman at csail: he did me a big favor,   
   and installed the Apache2 web server and PHP software needed for our day-to-day   
   operations on the new "telecom digest" server.   
      
   Thanks you, sir: you're a professional, and I'm not, so kudos to you   
   and your team.   
      
   I've been using our "backup" server for the last few days, and in the   
   process, I've realized that the Telecom Digest's internal work-flow   
   and software are in need of a major overhaul: I've been doing things   
   by hand that were automated on the old server, but thinking about the   
   scripts and lisp that I've put together - and am now doing without -   
   has made it obvious that I need to go back to the drawing board and   
   redesign a process which grew willy-nilly over decades.   
      
   So, I'm going to stay on the backup machine for another few days,   
   while I make notes and plans.   
      
   I've just turned 70, and although I still feel my mind is sharp, I   
   must be realistic: the system has to be simplified and must have much   
   better documentation if it's going to work when I'm much further along   
   the road. I welcome help and suggestions, especially with the tasks   
   shown in the following list:   
      
   1. I have to take the daily "Digest" email (the one most subscribers   
      get) and turn it into a web page so that those with only web-based   
      access can read the digest on the web.  Currently, that is a semi-automated   
      process, but I'm going to try to automate it completely: the rules and   
      procedure steps can be defined, and the scripts written, by anyone   
      experienced in awk or sed or (insert your favorite tool here).   
      
   2. The old server has procmail rules which detected posts that didn't   
      have complete headers, and put them in separate mailboxes where I   
      would work on them by hand. There needs to be an automatic process   
      for those changes, too.   
      
   3. I'd like to learn how to either   
      
      a. Adapt the regular web page for better visibility on mobile   
         devices with small screens, or ...   
      
      b. Learn how to detect a browser's screen resolution and/or size,   
         and deliver the content specific to that device.   
      
   4. Construct, code, test, and implement a moderation process which   
      doesn't require specialized knowlege, so that "Guest" moderators   
      aren't left flailing around in Linux-land just to do me a favor. It   
      would have to include:   
      
      a. Methods to modify posts before publication if needed.   
      
      b. Provision for moderation via email, without need for modifying   
         the headers of a post that requires repair. That will mean an   
         automated pre-moderation process which will benefit me as well   
         as those whom help if I'm sick or on vacation.   
      
   5. Other improvements that I don't yet know I need. Suggestions   
      welcome.   
      
   Bill Horne   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)