111 lines
4.8 KiB
HTML
111 lines
4.8 KiB
HTML
<pre>-----BEGIN PGP SIGNED MESSAGE-----
|
|
Hash: SHA1
|
|
|
|
Ev'nin folks, time for our status update
|
|
|
|
* Index
|
|
1) 0.4.2.4 & 0.4.2.5
|
|
2) 0.5 strategy
|
|
3) naming
|
|
4) eepsite roundup
|
|
5) ???
|
|
|
|
1) 0.4.2.4 & 0.4.2.5
|
|
|
|
With last week's 0.4.2.4 release, we saw the deployment of some new
|
|
load balancing algorithms to throttle tunnel participation based on
|
|
actual bandwidth usage, along side peer profiling updates to select
|
|
peers better through a wider sample of data. This has done pretty
|
|
well at both choking tunnel participation when necessary and finding
|
|
good peers when possible.
|
|
|
|
Another major update in that release was a change to how we verify
|
|
time synchronization - rather than just checking the time sync once
|
|
during connection establishment, peers now periodically send
|
|
messages to each other with their current time, and if the time
|
|
received is too far skewed, the connection is dropped. This has
|
|
helped kick a few routers who were skewing off the net until they
|
|
recovered (which is good), and the vast majority of peers have been
|
|
quite close to 'correct' (you can see the clock skew on the
|
|
/oldconsole.jsp page)
|
|
|
|
With that, the network has been performing pretty well, but we were
|
|
still seeing the occational bulk disconnect. After some debugging
|
|
we tracked down an unintentional and wholely unnecessary DNS lookup
|
|
that occurred whenever a router sent a message to a peer who has a
|
|
hostname specified. This not only wasted time, but it wasted time
|
|
within the jobqueue - essentially injecting a whole lot of lag for
|
|
no reason. With that lookup removed, the router handled much
|
|
better under heavily congested situations, but we were still seeing
|
|
those occational bulk disconnects. After digging around in the
|
|
stats and logging, we came up with a plausible theory that explains
|
|
why those disconnects have been occurring - blaming them almost
|
|
entirely on those DNS lookups. To test that theory (and to deploy
|
|
some other goodies), we pushed out the 0.4.2.5 release this
|
|
afternoon.
|
|
|
|
We'll see how it goes.
|
|
|
|
* 2) 0.5 strategy
|
|
|
|
As the roadmap [1] says, the next planned release is 0.5, including
|
|
a revised tunnel pool and encryption/id technique. Avoiding a
|
|
big explanation (see [2], [3], [4], and a tiny bit of [5]), we will
|
|
do this in two stages - first revamp the tunnel pooling and
|
|
push that out as an interim release, debugging what is necessary,
|
|
then revamp the encryption/id stuff, pushing that out as 0.5. Oh,
|
|
and of course, once the algorithms for the pooling and encryption
|
|
updates are in pretty good shape, they'll be posted up here and on
|
|
the website for review.
|
|
|
|
Along the way though, there will probably be small bugfix releases
|
|
unrelated to the 0.5 stuff, but I don't have any specifically
|
|
planned.
|
|
|
|
[1] <a rel="nofollow" href="http://www.i2p.net/roadmap">http://www.i2p.net/roadmap</a>
|
|
[2] <a rel="nofollow" href="http://www.i2p.net/todo#tunnelId">http://www.i2p.net/todo#tunnelId</a>
|
|
[3] <a rel="nofollow" href="http://www.i2p.net/todo#ordering">http://www.i2p.net/todo#ordering</a>
|
|
[4] <a rel="nofollow" href="http://www.i2p.net/todo#tunnelLength">http://www.i2p.net/todo#tunnelLength</a>
|
|
[5] <a rel="nofollow" href="http://www.i2p.net/todo#batching">http://www.i2p.net/todo#batching</a>
|
|
|
|
* 3) naming
|
|
|
|
Yikes, now that I think about it, I really don't want to talk
|
|
about naming yet - just download Ragnarok's latest addressbook
|
|
app (2.0.1) from <a rel="nofollow" href="http://ragnarok.i2p/">http://ragnarok.i2p/</a>, check out susi's web
|
|
based manager at <a rel="nofollow" href="http://susi.i2p/susidns/manager">http://susi.i2p/susidns/manager</a>, and dig
|
|
through the stats at <a rel="nofollow" href="http://orion.i2p/">http://orion.i2p/</a> and
|
|
<a rel="nofollow" href="http://susi.i2p/susisworld.html">http://susi.i2p/susisworld.html</a>
|
|
|
|
* 4) eepsite roundup
|
|
|
|
There have been some notable developments on various eepsites worth
|
|
mentioning:
|
|
|
|
= <a rel="nofollow" href="http://frosk.i2p/">http://frosk.i2p/</a> - I2PContent doc updates
|
|
= <a rel="nofollow" href="http://orion.i2p/">http://orion.i2p/</a> - new form to submit your keys to
|
|
= <a rel="nofollow" href="http://piespy.i2p/">http://piespy.i2p/</a> - neat graphs of the irc channels
|
|
= <a rel="nofollow" href="http://forum.fr.i2p/">http://forum.fr.i2p/</a> - french language forum
|
|
= <a rel="nofollow" href="http://pastebin.i2p/">http://pastebin.i2p/</a> - stop flooding the channels!
|
|
|
|
Of course, there have also been updates to other sites as well,
|
|
plus some other new sites - check orion.i2p and sort the list by
|
|
'last updated' to review (or just go to 'em all ;)
|
|
|
|
5) ???
|
|
|
|
I know there's lots more going on, so please, swing on by the
|
|
meeting in a few minutes and we can chat 'bout stuff.
|
|
|
|
=jr
|
|
-----BEGIN PGP SIGNATURE-----
|
|
Version: GnuPG v1.2.4 (GNU/Linux)
|
|
|
|
iD8DBQFByItjGnFL2th344YRAmmOAKD+HxEAK+dqseq8ZCO5pjvW4EKImQCgkfwX
|
|
1KM+uQo7D6BjHAA99DwVyS0=
|
|
=/T/b
|
|
-----END PGP SIGNATURE-----
|
|
|
|
|
|
</pre>
|