<p>14:05 <hypercubus> i guarantee that on PDforge your project will be confirmed virtually immediately ;-)</p>
<p>14:05 <jrandomi2p> 2) On deck for 0.3.4.1</p>
<p>14:05 <jrandomi2p> 3) New web console / I2PTunnel controller</p>
<p>14:05 <jrandomi2p> 4) 0.4 stuff</p>
<p>14:05 <jrandomi2p> 5) Other development activities</p>
<p>14:05 <jrandomi2p> 6) ???</p>
<p>14:05 <jrandomi2p> 0) hi</p>
<p>14:05 * jrandomi2p waves</p>
<p>14:05 < mihi> lla ih</p>
<p>14:05 * oOo goof</p>
<p>14:06 <mihi> hi all</p>
<p>14:06 <jrandomi2p> weekly status notes posted up to http://dev.i2p.net/pipermail/i2p/2004-August/000388.html</p>
<p>14:06 <jrandomi2p> jumping right in to 1) 0.3.4 status</p>
<p>14:07 <jrandomi2p> the net seems generally functional, both for irc and eepsites</p>
<p>14:07 <jrandomi2p> what kind of eepsite reliability / failures are y'all seeing?</p>
<p>14:07 * jrandomi2p can see the irc failures here, as i see when people disconnect / etc</p>
<p>14:08 <mule2p> in general good, got out-of-memory after approx 25MBytes</p>
<p>14:08 <mule2p> but that should be fixed in cvs, as you mentioned</p>
<p>14:08 <jrandomi2p> ah ok thats on a single 25MB download right?</p>
<p>14:09 <mule2p> yes</p>
<p>14:09 <jrandomi2p> right</p>
<p>14:10 <jrandomi2p> large file transfers do still seem to have problems (disconnect over time, not corruption though). i think that may be fixed with the mod mentioned, but i'm not sure</p>
<p>14:11 * jrandomi2p forgot to mention that oOo's roundtrip/connections_reliability.php includes both irc servers here, not just i2p, so doesnt really have the right data atm</p>
<p>14:11 <jrandomi2p> oOo - any thoughts on what it'd take to get the bogobot code to ignore @irc.metropipe.net?</p>
<p>14:12 < duck> kicking hypercubus</p>
<p>14:12 < duck> and me to upgrade</p>
<p>14:12 <oOo> Very few coding, a peer review by hypercubus and the update of bogobot by duke</p>
<p>14:13 <jrandomi2p> ok cool</p>
<p>14:13 <hypercubus> duke?</p>
<p>14:13 <oOo> duck, sorry :p</p>
<p>14:13 * jrandomi2p thinks that sort of statistical summary would be very helpful</p>
<p>14:13 <jrandomi2p> duke duck</p>
<p>14:14 <oOo> The stats are made on PHP, could be given to duck, too</p>
<p>14:14 <jrandomi2p> ok, anyone have anything to bring up wrt 0.3.4?</p>
<p>14:14 <jrandomi2p> w3rd</p>
<p>14:15 <jrandomi2p> ok, moving on to 2) 0.3.4.1</p>
<p>14:15 <jrandomi2p> i dont know what else to mention beyond whats mentioned in the mail</p>
<p>14:16 <jrandomi2p> the StreamSinkServer and StreamSinkClient apps are compact demo apps for ministreaming (for any java devs who want to write streaming over i2p)</p>
<p>14:16 <jrandomi2p> oh, and StreamSinkServer is kind of like aum's dropbox python app (it takes any data anyone sends it and writes it to a file)</p>
<p>14:17 <jrandomi2p> (StreamSinkClient sends a fixed size of random data, so not too useful ;)</p>
<p>14:17 <jrandomi2p> any thoughts / concerns / questions wrt 0.3.4.1?</p>
<p>14:18 * jrandomi2p estimates it'll be out in a day or two</p>
<p>14:19 <jrandomi2p> ok, moving on at a good clip to 3) New web console / I2PTunnel controller</p>
<p>14:20 <jrandomi2p> as mentioned in the mail, we've got the new web console pretty much functional, and a simple web interface to control / edit / create i2ptunnel instances</p>
<p>14:21 < protok0l> where can the protok0l get it</p>
<p>14:22 < protok0l> and what do i do with jetty</p>
<p>14:22 <jrandomi2p> its all in cvs now, but i need to put up some docs on how to set it up</p>
<p>14:22 < protok0l> ok</p>
<p>14:23 * jrandomi2p wrote up and posted a ~5 step process to the channel a few days ago, but we need a simpler proc (or at least a more clear one)</p>
<p>14:23 < protok0l> i heard that CVS sucks</p>
<p>14:23 <mule2p> ok, can tell you once i have the docs :)</p>
<p>14:23 < protok0l> and there was some better CVS thingy</p>
<p>14:23 * oOo logged only the first 2 steps before getting disconnected :p</p>
<p>14:24 < protok0l> same thing with Vi</p>
<p>14:24 < protok0l> lol</p>
<p>14:24 <jrandomi2p> we'll eventually moving to have this new console be the 'standard', but that'll probably wait until we've got everything integrated with hypercubus' new installer</p>
<p>14:26 <jrandomi2p> actually</p>
<p>14:26 <jrandomi2p> for the brave, here's the ugly steps from before:</p>
<p>14:26 <jrandomi2p> 20:19 < jrandom> w3rd hyper - could you pull latest from cvs, 'ant dist', grab build/*jar and toss them into your lib dir, mkdir $instDir/webapps/ ; cp build/routerconsole.war $instDir/webapps/ ; edit your router.config to uncomment the clientApp.3.* lines and update your classpath</p>
<p>14:26 <jrandomi2p> 20:19 < jrandom> (in the classpath, set it to: lib/i2p.jar:lib/router.jar:lib/mstreaming.jar:lib/heartbeat.jar:lib/i2ptunnel.jar:lib/netmonitor.jar:lib/sam.jar:lib/timestamper.jar:lib/ant.jar:lib/jasper-compiler.jar:lib/jasper-runtime.jar:\</p>
<p>14:27 <jrandomi2p> in addition to that, there's a new i2ptunnel.war - take that and drop it into $instDir/webapps/ and go to http://localhost:7657/i2ptunnel/</p>
<p>14:27 <jrandomi2p> yeah, as i said, its a pain</p>
<p>14:27 <jrandomi2p> *but* its functional, and I dont really have either the time or the expertise to make it much better</p>
<p>14:27 <oOo> That's all it needs to be done ?</p>
<p>14:28 <jrandomi2p> yup</p>
<p>14:28 <oOo> Ok, thanks</p>
<p>14:28 <jrandomi2p> (you'll get something looking like http://dev.i2p.net/~jrandom/config.png when you go to http://localhost:7657/config.jsp</p>
<p>14:57 <jrandomi2p> there are some further optimizations that can be done to the tunnel pool, but i'm not sure how useful it'd be atm</p>
<p>14:57 <jrandomi2p> ok, jumping back on track - anyone else have anything wrt 4) 0.4. stuff?</p>
<p>14:57 <oOo> About 'large scale simulations' for 0.4, any way to prepare thus ? Need 'new' specifics applications/tools ? (transition to point 5 ? ;) )</p>
<p>14:58 <jrandomi2p> actually, for the sim it would be great if someone could help mod the heartbeat (or a sam-powered app) to be kind of a scriptable client / server</p>
<p>14:59 -!- Bladenight is now known as Nightblade</p>
<p>14:59 <jrandomi2p> (e.g. rather than the current "every 30s, send 20KB to peer X", a "for 10 minutes, ask peer X for a 1MB file, and then pause for 60m, then ask peer Y for 1KB files" etc)</p>
<p>15:00 <jrandomi2p> but if someone is interested in helping out with that, please let me know and we can chan</p>
<p>15:00 <jrandomi2p> er, chat</p>
<p>15:00 <jrandomi2p> taking that lead in, lets jump to 5) stuff y'all are doing :)</p>
<p>15:01 <jrandomi2p> not sure how to go about covering this, lets just go down in the (arbitrary) order listed in the mail for updates?</p>
<p>15:01 <jrandomi2p> i dont see sunshine here, and aum probably isn't up yet ;)</p>
<p>15:02 <jrandomi2p> nightblade - how goes the battle? </p>
<p>15:02 < Nightblade> i have some plans for making the libsam interface like bsd sockets</p>
<p>15:02 < Nightblade> but i haven't done any coding on that part yet</p>
<p>15:02 < duck> changed to tunnels.numInbound=3</p>
<p>15:03 <jrandomi2p> cool duck (hopefully wait until after the meeting to restart your tunnel ;)</p>
<p>15:03 < duck> oh, it doesnt detect the changes?</p>
<p>15:03 <jrandomi2p> word nightblade - is there a problem w/ the way things are now?</p>
<p>15:03 <hypercubus> not until you code it to ;-)</p>
<p>15:03 <jrandomi2p> naw duck, the clientApp lines are only read on startup</p>
<p>15:04 <jrandomi2p> (clientApp is really outside the control of the router - thats what the i2ptunnel web app is for)</p>
<p>15:04 < Nightblade> no there is no problem with it the way it is now.... what i would be doing is in addition to the interface that is already there (developers could choose what they want to use)</p>
<p>15:04 <jrandomi2p> wikked</p>
<p>15:05 <jrandomi2p> ok, you're the boss. having variety is good, though variety means more code to maintain / etc, but its a balance</p>
<p>15:06 <jrandomi2p> ok, moving on down the list - mule2p - how goes the outproxy stuff?</p>
<p>15:07 <mule> nothing done beyond the patch you have</p>
<p>15:07 <jrandomi2p> ah ok i thought you were working on a further mod</p>
<p>15:07 <mule> need to find some spare time for real load balancing</p>
<p>15:07 <jrandomi2p> w3rd</p>
<p>15:08 <jrandomi2p> i'll get that patch applied then</p>
<p>15:08 <mule> thanks. and include my outproxy in the client app :) seems to be faster</p>
<p>15:08 <jrandomi2p> heh, well, of course your proxy will be faster for you, its local :)</p>
<p>15:09 <oOo> And no one else use it ^^</p>
<p>15:09 <mule> no, it isn't</p>
<p>15:09 <jrandomi2p> ooh, its on a different router? cool</p>
<p>15:09 <mule> yep, on a root server at an isp</p>
<p>15:10 <jrandomi2p> the i2ptunnel web interface has a field for people to specify the list of outproxies, so it should be easy enough for people to tweak, but we'll get it out in the next rev & release notes</p>
<p>15:10 <jrandomi2p> nice</p>
<p>15:11 <jrandomi2p> ok, nickster seems to be offline atm</p>
<p>15:12 <jrandomi2p> are there any other active client development efforts going on?</p>
<p>15:12 <jrandomi2p> (or are any of the paused ones active, etc?)</p>
<p>15:13 <jrandomi2p> ok, if someone wants to mention anything else on that front, we've got the list and the channel, as always :)</p>
<p>15:13 <jrandomi2p> moving on to 6) ???</p>
<p>15:13 <jrandomi2p> anyone else have anything they want to bring up?</p>
<p>15:14 < Nightblade> nope</p>
<p>15:15 <mihi> duck has anything to bring down ;)</p>
<p>15:15 <mihi> s/any/some/</p>
<p>15:15 * jrandomi2p pingfloods mihi</p>
<p>15:15 <jrandomi2p> ok, on that note</p>
<p>15:15 * jrandomi2p winds up</p>
<p>15:15 * jrandomi2p *baf*s the meeting closed</p>
