jrandom authored 19 years ago and zzz committed 19 years ago

    * Error handling for failed intro packets (thanks red.hand!)
    * More carefully verify intro addresses

jrandom authored 19 years ago and zzz committed 19 years ago

    * More careful error handling with introductions (thanks dust!)
    * Fix the forceIntroducers checkbox on config.jsp (thanks Complication!)
    * Hide the shitlist on the summary so it doesn't confuse new users.

comwiz authored 19 years ago and zzz committed 19 years ago

    * Migrated the router tests to junit

jrandom authored 19 years ago and zzz committed 19 years ago

    * Removed guaranteed delivery mode entirely (so existing i2phex clients
      using it can get the benefits of mode=best_effort).  Guaranteed delivery
      is offered at the streaming lib level.
    * Improve the peer selection code for peer testing, as everyone now
      supports tests.
    * Give the watchdog its fangs - if it detects obscene job lag or if
      clients have been unable to get a leaseSet for more than 5 minutes,
      restart the router.  This was disabled a year ago due to spurious
      restarts, and can be disabled by "watchdog.haltOnHang=false", but the
      cause of the spurious restarts should be gone.

jrandom authored 19 years ago and zzz committed 19 years ago

    * Bugfix for skewed store which could kill a UDP thread (causing complete
      comm failure and eventual OOM)

jrandom authored 19 years ago and zzz committed 19 years ago

    * More aggressively publish updated routerInfo.
    * Expose the flag to force SSU introductions on the router console
    * Don't give people the option to disable SNTP time sync, at least not
      through the router console, because there is no reason to disable it.
      No, not even if your OS is "ntp synced", because chances are, its not.

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.