Since the earliest date functions as a version number,
this will force the floodfill to flood each new version;
otherwise it won't if the earliest time hasn't changed.

dont log a RI DSM down a client tunnel as an error, just silently drop, as probably the result of a FVSJ

      - Do LS stores and verifies through client tunnels
        to prevent correlation by the OBEP or FF
      - Encrypt LS stores to prevent snooping by the OBEP
      - Encrypt LS and RI verifies to prevent snooping by the OBEP
      - Extend verify delay and timeout
      - Reenable RI verifies
      - Disallow simultaneous verifies for the same key
      - Don't resend on verify timeout; try a different peer instead
      - Adjust ff selection criteria

            to branch 'i2p.i2p.zzz.test' (head 9eee20312852c80ca6c8e079174578a335edbe6d)

     and 'd548b2a3c95f98dd3296cdd891e03e7c2936e61e'

as the newer ones place a check for 1.7.1. We require 1.7.0

deletes backup files and add a few extra types that should be commonly 
needed... atleast by me.

      "don't give me floodfills"
    * PeerSelector: Downgrade floodfills with high fail rate