Beginning of migration of status notes

i2p2www/blog/2004/11/02/status.html

@@ -0,0 +1,96 @@
+{% extends "_layout.html" %}
+{% block title %}I2P Status Notes for 2004-11-02{% endblock %}
+{% block content %}<h3>I2P Status Notes for 2004-11-02</h3>
+<pre>-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+Hi y'all, time for the weekly update
+
+* Index:
+1) Net status
+2) Core updates
+3) Streaming lib
+4) mail.i2p progress
+5) BT progress
+6) ???
+
+* 1) Net status
+
+Pretty much as before - a steady number of peers, eepsites fairly
+reachable, and irc for hours on end.  You can get a peek at the
+reachability of various eepsites through a few different pages:
+ - <a  rel="nofollow" href="http://gott.i2p/sites.html">http://gott.i2p/sites.html</a>
+ - <a  rel="nofollow" href="http://www.baffled.i2p/links.html">http://www.baffled.i2p/links.html</a>
+ - <a  rel="nofollow" href="http://thetower.i2p/pings.txt">http://thetower.i2p/pings.txt</a>
+
+* 2) Core updates
+
+For those hanging out in the channel (or reading the CVS logs),
+you've seen a lot of things going on, even though its been a while
+since the last release.  A full list of changes since the 0.4.1.3
+release can be found online [1], but there are two major
+modifications, one good and one bad:
+
+The good one is that we've dramatically cut down on the memory churn
+caused by all sorts of insane temporary object creation.  I finally
+got fed up with watching the GC go mad while debugging the new
+streaming lib, so after a few days of profiling, tweaking, and
+tuning, the ugliest parts are cleaned up.
+
+The bad one is a bugfix for how some tunnel routed messages are
+handled - there were some situations where a message was sent
+directly to the targeted router rather than tunnel routed prior to
+delivery, which could be exploited by an adversary who can do a
+little coding.  We now properly tunnel route when in doubt.
+
+That may sound good, but the 'bad' part is that it means that there's
+going to be some increased latency due to the additional hops, though
+these are hops that needed to be used anyway.
+
+There are other debugging activities going on in the core as well, so
+there hasn't been an official release yet - CVS HEAD is 0.4.1.3-8.
+In the next few days we'll probably have a 0.4.1.4 release, just to
+get all that stuff cleared up.  It won't contain the new streaming
+lib, of course.
+
+[1] <a  rel="nofollow" href="http://dev.i2p.net/cgi-bin/cvsweb.cgi/i2p/history.txt?rev=HEAD">http://dev.i2p.net/cgi-bin/cvsweb.cgi/i2p/history.txt?rev=HEAD</a>
+
+* 3) Streaming lib
+
+Speaking of the streaming lib, there has been a lot of progress here,
+and the side by side comparison of the old and new libs are looking
+good.  However, there is still work to be done, and as I said last
+time, we're not going to rush it out the door.  That does mean that
+the roadmap has slipped, likely in the range of 2-3 weeks.  More
+details when they're available.
+
+* 4) mail.i2p progress
+
+Lots of new stuff this week - working in and out proxies!  See
+www.postman.i2p for more information.
+
+* 5) BT progress
+
+There has been a flurry of activity regarding porting a BitTorrent
+client as of late, as well as updating some tracker settings.
+Perhaps we can get some updates from those involved during the
+meeting.
+
+* 6) ???
+
+Thats it for me.  Sorry for the delay, I forgot about that whole
+daylight savings thingamabob.  Anyway, see y'all in a few.
+
+=jr
+
+-----BEGIN PGP SIGNATURE-----
+Version: PGP 8.1
+
+iQA/AwUBQYf9PBpxS9rYd+OGEQIoGQCgvDKydGRT42tO9bwWutAwnoolpj0AoNyX
+Z1ThyrjEZjAttC/wChPN43aD
+=SJDa
+-----END PGP SIGNATURE-----
+
+
+</pre>
+{% endblock %}