* if you are offline, and you try to use the Fancy Browser Post version of the submit form, you might 
  be told that the browser cannot connect to 127.0.0.1... because you are not on the Internet.  I regard
  this as a bug in the understanding that MacOSX has of 'the Internet' (because the 127.* address range is
  most definitely local).  However, there are a few workarounds.  The first is, tell your Mac that it *is*
  connected to the internet by creating a Network->Location that has any ethernet adapter enabled, and have
  it use DHCP.  Though you still won't be really connected to the Internet, your Mac browsers should believe
  that you are, and your message will be queued when the guestpost.pl or the SocketServer realizes that they
  cannot connect to Blogger.  The second workaround is, use the non-fancy forms.
* the command parsers everywhere are vulnerable to segmentation faults where malformed urls are sent
* blogger.com blogs work unconditionally, but the blogger api uses a cdata message body, which some blogger API
  tools don't understand (movableType).  movableType works unconditionally with the metaweblog API, but, it uses
  a base64 tag allowed by the relevant RFCs.  blogger.com doesn't support this tag, but luckily it doesn't support
  the metaweblog API anyway.  However, other metaweblog API tools might also not support the base64 tag.  Those
  blogging tools won't work with BlogPost unless they support the blogger API instead, and understand cdata
  message bodies.
* plant.blogger.com changes its ip; I need to make the address resolution dynamic instead of coded in