jrandom authored 19 years ago and zzz committed 19 years ago

    * Test the router's reachability earlier and more aggressively
    * Use the low level bandwidth limiter's rates for the router console, and
      if the router has net.i2p.router.transport.FIFOBandwidthLimiter=INFO in
      the logger config, keep track of the 1 second transfer rates as the stat
      'bw.sendBps1s' and 'bw.recvBps1s', allowing closer monitoring of burst
      behavior.

jrandom authored 19 years ago and zzz committed 19 years ago

    * Added preliminary support for NAT hole punching through SSU introducers
    * Honor peer test results from peers that we have an SSU session with if
      those sessions are idle for 3 minutes or more.

cervantes authored 19 years ago and zzz committed 19 years ago

	* New build due to change in build number :P (thanks ugha!)

jrandom authored 19 years ago and zzz committed 19 years ago

    * HTML cleanup for the router console (thanks!)
2005-09-07  jrandom
    * Lay the foundation for 'client routers' - the ability for peers to opt
      out of participating in tunnels entirely due to firewall/NAT issues.
      Individual routers have control over where those peers are used in
      tunnels - in outbound or inbound, exploratory or client tunnels, or
      none at all.  The defaults with this build are to simply act as before -
      placing everyone as potential participants in any tunnel.
    * Another part of the foundation includes the option for netDb
      participants to refuse to answer queries regarding peers who are marked
      as unreachable, though this too is disabled by default (meaning the
      routerInfo is retrievable from the netDb).

jrandom authored 19 years ago and zzz committed 19 years ago

allow publishing to a remote archive automatically when posting (optionally) with 0 additional clicks
allow transparently attaching any 'public' pet names in your addressbook to a blog post (with a checkbox)

jrandom authored 19 years ago and zzz committed 19 years ago

    * Expose the HTTP headers to EepGet status listeners
    * Handle DSA key failures properly (if the signature is not invertable, it
      is obviously invalid)

jrandom authored 19 years ago and zzz committed 19 years ago

    * Expose the HTTP headers to EepGet status listeners
    * Handle DSA key failures properly (if the signature is not invertable, it
      is obviously invalid)
also, syndie now properly detects whether the remote archive can send a filtered export.zip
by examining the HTTP headers for X-Syndie-Export-Capable: true.  If the remote archive
does not set that header (and neither freesites, nor apache or anything other than the ArchiveServlet will),
it uses individual HTTP requests for individual blog posts and metadata fetches.

jrandom authored 19 years ago and zzz committed 19 years ago

rss.jsp can in turn receive all the filters that index.jsp can - e.g. ?blog=blah or ?selector=group://foo,
and by default returns the latest 10 values (overridden with ?wanted=15).  If you want it to pull
with a user's blog's preferences (filters, groups, etc), you can specify ?login=user&password=password

jrandom authored 19 years ago and zzz committed 19 years ago

ui improvements (per isamoor's suggestions)
more petname integration

jrandom authored 19 years ago and zzz committed 19 years ago

allow exporting eepsite destinations from the syndie database into userhosts.txt (so the eepproxy can get it)

jrandom authored 19 years ago and zzz committed 19 years ago

if the prop "syndie.remotePassword" is set, users can enter it while viewing their metadata

jrandom authored 19 years ago and zzz committed 19 years ago

    * Don't persist peer profiles until we are shutting down, as the
      persistence process gobbles RAM and wall time.
    * Bugfix to allow you to check/uncheck the sharedClient setting on the
      I2PTunnel web interface.
    * Be more careful when expiring a failed tunnel message fragment so we
      don't drop the data while attempting to read it.

jrandom authored 19 years ago and zzz committed 19 years ago

    * Don't refuse to send a netDb store if the targetted peer has failed a
      bit (the value was an arbitrary amount).
    * Logging changes

jrandom authored 19 years ago and zzz committed 19 years ago

    * Don't send out a netDb store of a router if it is more than a few hours
      old, even if someone asked us for it.

jrandom authored 19 years ago and zzz committed 19 years ago

    * Don't publish leaseSets to the netDb if they will never be looked for -
      namely, if they are for destinations that only establish outbound
      streams.  I2PTunnel's 'client' and 'httpclient' proxies have been
      modified to tell the router that it doesn't need to publish their
      leaseSet (by setting the I2CP config option 'i2cp.dontPublishLeaseSet'
      to 'true').
    * Don't publish the top 10 peer rankings of each router in the netdb, as
      it isn't being watched right now.

jrandom authored 19 years ago and zzz committed 19 years ago

    * Don't publish leaseSets to the netDb if they will never be looked for -
      namely, if they are for destinations that only establish outbound
      streams.  I2PTunnel's 'client' and 'httpclient' proxies have been
      modified to tell the router that it doesn't need to publish their
      leaseSet (by setting the I2CP config option 'i2cp.dontPublishLeaseSet'
      to 'true').
    * Don't publish the top 10 peer rankings of each router in the netdb, as
      it isn't being watched right now.

jrandom authored 19 years ago and zzz committed 19 years ago

    * Added the new test Floodfill netDb

jrandom authored 19 years ago and zzz committed 19 years ago

    * Added the new test Floodfill netDb