74 lines
5.8 KiB
HTML
74 lines
5.8 KiB
HTML
{% extends "_layout.html" %}
|
|
{% block title %}I2P Development Meeting 168{% endblock %}
|
|
{% block content %}<h3>I2P dev meeting, February 14, 2006</h3>
|
|
<div class="irclog">
|
|
<p>15:39 < jrandom> 0) hi</p>
|
|
<p>15:39 < jrandom> 1) Net status</p>
|
|
<p>15:39 < jrandom> 2) 0.6.1.10</p>
|
|
<p>15:39 < jrandom> 3) Syndie activity</p>
|
|
<p>15:39 < jrandom> 4) ???</p>
|
|
<p>15:39 < jrandom> 0) hi</p>
|
|
<p>15:39 * jrandom waves</p>
|
|
<p>15:39 < jrandom> weekly status notes posted up at http://dev.i2p.net/pipermail/i2p/2006-February/001260.html</p>
|
|
<p>15:39 < jrandom> (I'm a lil late with that, so I'll give y'all a minute to skim through those brief notes)</p>
|
|
<p>15:40 <+Complication> hello</p>
|
|
<p>15:40 <@cervantes> 'lo</p>
|
|
<p>15:41 < jrandom> well, its brief enough, so lets just jump on in to 1) Net status</p>
|
|
<p>15:41 < jrandom> I don't have anything to add to this one, anyone have something on it to discuss?</p>
|
|
<p>15:41 <@cervantes> <jrandom> (damn flakey net connection)</p>
|
|
<p>15:41 <+Complication> A bit congested occasionally, but graphs suggest it's nothing new</p>
|
|
<p>15:42 < jrandom> heh cervantes, well, thats due to one of my roommates using limewire, not i2p ;)</p>
|
|
<p>15:43 <@cervantes> we've had various server problems too with irc and postman's tracker over the past couple of weeks - postman has done a lot of migrations, so things should be more stable for folk</p>
|
|
<p>15:43 <+Complication> It must be hard letting them do that, but I guess... such is life :O</p>
|
|
<p>15:43 <+Complication> do that=use limewire</p>
|
|
<p>15:44 <+Complication> This morning, tracker.postman.i2p was refusing connections, though</p>
|
|
<p>15:44 < jrandom> Complication: disk was full, fixed now</p>
|
|
<p>15:44 < jrandom> (new machines have their new quirks)</p>
|
|
<p>15:46 < jrandom> ok, anyone have anything else on 1) Net status?</p>
|
|
<p>15:46 < jrandom> otherwise, lets shimmy on over to 2) 0.6.1.10</p>
|
|
<p>15:47 < jrandom> As mentioned, we're going to have a new backwards incompatible release in a few days</p>
|
|
<p>15:48 < jrandom> while it alone won't revolutionize our performance, it will improve a few key metrics to get us on our way</p>
|
|
<p>15:48 < jrandom> there are also a whole bunch of bug fixes in there too</p>
|
|
<p>15:49 <@cervantes> will zzz's server tunnel improvements make the fold?</p>
|
|
<p>15:49 < jrandom> oh, and there's that whole improved anonymity thing... ya know, sine qua non</p>
|
|
<p>15:50 < jrandom> cervantes: probably not, haven't heard much since that post to zzz.i2p last week. i did do some minor bugfixes in cvs though (to should support lighttpd, etc), but we won't have zzz's persistent connections</p>
|
|
<p>15:50 < jrandom> (yet)</p>
|
|
<p>15:51 <@frosk> what DH key size/etc did you land on?</p>
|
|
<p>15:51 <@cervantes> yeah, I saw those newline issues a few weeks ago, but I held off changing them because of zzz's impending improvements</p>
|
|
<p>15:51 < jrandom> ah, for the moment we'll be sticking with 2048bit crypto with small exponents</p>
|
|
<p>15:52 <@frosk> so some lower cpu consumption can be expected?</p>
|
|
<p>15:52 < jrandom> aye</p>
|
|
<p>15:53 <@frosk> excellente</p>
|
|
<p>15:53 < jrandom> switching to 1024bit would cut another order of magnitude to the CPU load, but would require some reworking of the tunnel creation structures (1024bit asym isn't large enough to convey the data we need to convey). </p>
|
|
<p>15:54 < jrandom> we may explore that in the future though, but this next release should substantially cut down cpu overhead</p>
|
|
<p>15:54 < jrandom> I've also disabled the TCP transport, because I'm a mean and vicious person</p>
|
|
<p>15:55 <@frosk> do you expect any more incompatible upgrades before 1.0?</p>
|
|
<p>15:55 < jrandom> hope not</p>
|
|
<p>15:55 * cervantes must be a danish cartoonist</p>
|
|
<p>15:55 <@frosk> i don't think we'll miss tcp :)</p>
|
|
<p>15:55 <@cervantes> I mean jrandom must be</p>
|
|
<p>15:55 <@cervantes> ;-)</p>
|
|
<p>15:55 * jrandom watches the embassy burn</p>
|
|
<p>15:56 < jrandom> ok, anyone have anything else on 2) 0.6.1.10?</p>
|
|
<p>15:56 < void> why wouldn't it support lighttpd earlier?</p>
|
|
<p>15:56 < jrandom> (ah, as an aside, there have also been some interesting improvements to the streaming lib for 0.6.1.10, such as tcp-style fast retransmit, etc, so we'll see how that helps)</p>
|
|
<p>15:57 <@cervantes> void: malformed headers</p>
|
|
<p>15:57 < jrandom> void: bug where we weren't standards compliant</p>
|
|
<p>15:57 < void> ah, are these inconsistent newline bugs also fixed?</p>
|
|
<p>15:58 < void> and what about the null character one? are you waiting for zzz's persistent connection patch?</p>
|
|
<p>15:58 < jrandom> the newline bug is the malformed header, and is fixed</p>
|
|
<p>15:58 < jrandom> no news on the null character one</p>
|
|
<p>15:59 < void> ok</p>
|
|
<p>16:00 < jrandom> ok, if there's nothing else on 2, lets swing on by 3) Syndie activity briefly</p>
|
|
<p>16:00 < jrandom> well, I don't really have much to add...</p>
|
|
<p>16:01 < jrandom> (I /did/ say briefly)</p>
|
|
<p>16:01 < jrandom> so lets jump on to 4) ???</p>
|
|
<p>16:01 < jrandom> anyone have anything else they want to bring up for the meeting?</p>
|
|
<p>16:01 <+fox> <duck> too busy reading Syndie to comment</p>
|
|
<p>16:01 < jrandom> ;)</p>
|
|
<p>16:02 * Complication is too busy issuing meaningless signatures to comment :D</p>
|
|
<p>16:05 < jrandom> ok cool. just another reminder for people to stay away from CVS for the next day or two until the release, as CVS HEAD is going to get the _PRE branch's changes, and the _PRE branch is going to be retired</p>
|
|
<p>16:05 * jrandom winds up</p>
|
|
<p>16:05 * jrandom *baf*s the meeting closed</p>
|
|
</div>
|
|
{% endblock %} |