<p>14:05 < jrandom> 1) Network status and 0.3.4.3</p>
<p>14:05 < jrandom> 2) Stasher</p>
<p>14:06 < jrandom> 3) ???</p>
<p>14:06 < jrandom> 0) hi</p>
<p>14:06 * jrandom waves to all the i[2i]p & freenode gang</p>
<p>14:06 * hypercubus waves</p>
<p>14:06 < jrandom> weekly status notes posted a few seconds ago to http://dev.i2p.net/pipermail/i2p/2004-August/000409.html</p>
<p>14:06 < deer><oOo_itwop> It's Show Time !</p>
<p>14:07 < deer><mule> seems i2p irc doesn't love me. or it wants to keep me hot longer by regular interruptions</p>
<p>14:07 < jrandom> heh, yeah, that actually leads us in to 1) Network status and 0.3.4.3 :)</p>
<p>14:07 < jrandom> the network is pretty shitty right now</p>
<p>14:07 < kaji> yep</p>
<p>14:08 < jrandom> the problems are showing up largely from incompatabilities with the different releases that people are running, which has been injecting all sorts of neat ways to break things</p>
<p>14:09 < jrandom> if you check the links in the email, you can see the flooding and netDb DoS that has gone on, but it has largely subsided</p>
<p>14:09 < jrandom> we still do have a half dozen people running old releases (and probably 20-25 people running vanilla 0.3.4.2, with its own problems)</p>
<p>14:10 < jrandom> i appreciate your patience as we move forward on this. i dont want to rush a new release without first being able to effeciently route around bad nodes</p>
<p>14:10 < jrandom> in the past we have been able to route around bad nodes that merely perform poorly, but havent had to deal with nodes who do Bad Things</p>
<p>14:11 < deer><oOo_itwop> Guinea pigs bows to jrandom !</p>
<p>14:11 < duck> will the next release be backward compatible?</p>
<p>14:11 < jrandom> perhaps duck. if we can work around those old nodes, there's no reason to make it incompatible</p>
<p>14:12 < duck> cool</p>
<p>14:12 < jrandom> anyway, there's lots of activity going on, even though y'all aren't seeing any new releases yet</p>
<p>14:13 < jrandom> i dont know when 0.3.4.3 will be out. perhaps tomorrow, or perhaps later this week.</p>
<p>14:14 < jrandom> anyone have any questions / comments / concerns they'd like to bring up wrt network status?</p>
<p>14:14 < kaji> will *.3 have hyper's new gui install?</p>
<p>14:14 < jrandom> probably not</p>
<p>14:14 < deer><mule> the network looks good to me in the profiles of my boxes, just that i frequently drop</p>
<p>14:15 < jrandom> yeah, i understand mule. the irc con has been pretty bad for me too, but its been getting better lately</p>
<p>14:15 < deer><mule> but i missed most of your discussion, so i'll shut up for now</p>
<p>14:15 < jrandom> if you want to try pulling from CVS, that should have an improvement, but there are frequent updates so you may want to wait until the release</p>
<p>14:16 < jrandom> ok anything else? if not, moving briskly along to 2) Stasher</p>
<p>14:16 < kaji> woot stasher</p>
<p>14:17 < jrandom> stasher is looking pretty cool. still quite limited functionality, but its making progress</p>
<p>14:17 < jrandom> if aum were awake he could give us an update...</p>
<p>14:17 < jrandom> aum: ping? :)</p>
<p>14:17 < kaji> /kick aum</p>
<p>14:18 < jrandom> (its early for him though, so he is probably still sleeping)</p>
<p>14:18 < duck> how selfish</p>
<p>14:18 < hypercubus> i'm impressed by it so far</p>
<p>14:18 < jrandom> Anyway, installing and running stasher is pretty painless, so if you can help him test it out, that'd be great</p>
<p>14:18 < jrandom> yeah, mos' def'</p>
<p>14:18 < hypercubus> it has allowed me to pull off mass goatse'ing</p>
<p>14:19 < jrandom> and whats an app without a goatse, 'eh? </p>
<p>14:19 < hypercubus> you gotta love an app that lets you upload goatse to someone's drive ;-)</p>
<p>14:19 < aum> pong</p>
<p>14:19 < jrandom> w0ah </p>
<p>14:19 < jrandom> 'mornin aum</p>
<p>14:19 < deer><ardvark> quick question: do I get stasher via i2p CVS?</p>
<p>14:19 < aum> hi all</p>
<p>14:19 < jrandom> ardvark: in i2p/apps/stasher/</p>
<p>14:19 < aum> ardvark: hi!!!! :) long time!</p>
<p>14:20 < deer><ardvark> yes hi aum! good to see you mate!</p>
<p>14:20 < aum> ardvark: prolly easier via tarball - http://stasher.i2p or http://www.freenet.org.nz/python/stasher</p>
<p>14:21 < deer><ardvark> ok aum, I got the tarball but needs other stuff it says? I'll not hold back the meeting, maybe I can contact you?</p>
<p>14:21 < aum> sure thing</p>
<p>14:22 < hypercubus> so, any update on stasher aum? ;-)</p>
<p>14:23 < aum> small update, i've added a '-l' option which allows local-only get/put</p>
<p>14:23 < aum> also, thinking of implementing a 'put' option which returns immediately </p>
<p>14:24 < aum> last night, was thinking thru issues of implementing freenet keytypes</p>
<p>14:24 < hypercubus> i'd like to request that successful put operations return a status... scp and many other command line net apps do this</p>
<p>14:24 < jrandom> SSK would quite kick ass</p>
<p>14:25 < jrandom> (while CHK is of course what imho is most essential)</p>
<p>14:25 < MikeW> One thing I always found interesting about freenet was: It would tell you why there could be high CPU usage. Sometimes (usually at startup for a minute or two) and randomly, CPU usage spikes to 100%, perhaps a estimation why it thinks java is eating my cpu?</p>
<p>14:26 < jrandom> MikeW: if i2p is eating your CPU there is most certainly something broken going on</p>
<p>14:26 < aum> i've tentatively implemented splitfiles already, but haven't enabled it - want to test locally first</p>
<p>14:26 < jrandom> MikeW: you can tell exactly whats going on in your router by looking at the 'current job' in the router console, which is (almost always) where the CPU crunch is</p>
<p>14:26 < jrandom> ah cool aum</p>
<p>14:27 < aum> due to a recursive algo, the splitfiles thing should allow unlimited file sizes when it's done</p>
<p>14:27 < deer><oOo> Great, splitfiles are mandatory for serious goatse and pr0n stuff...</p>
<p>14:27 < deer><identiguy> aum: does that include FEC?</p>
<p>14:27 < aum> fec not needed</p>
<p>14:27 < aum> fec is only required on flaky networks</p>
<p>14:27 < deer><identiguy> Ah, I see.</p>
<p>14:27 < aum> i'm using kademlia, which has far better retrievability guarantee</p>
<p>14:27 < duck> unless nodes go down</p>
<p>14:28 < aum> plus, i can't be fscked doing fec anyway, it's a pain</p>
<p>14:28 < aum> duck: there's redundancy - refer the 'k' value in kademlia</p>
<p>14:28 < jrandom> duck: with a k of 20, even without any republishing it'd be ok ;)</p>
<p>14:28 < duck> heh, okay</p>
<p>14:28 < deer><mule> aum: fec might help in case a number of nodes are removed</p>
<p>14:28 < jrandom> (and with republishing, it'd only hurt if all k died at the same time)</p>
<p>14:28 < aum> naah, i'll just increase k</p>
<p>14:28 < jrandom> k of 20 imho is pretty substantial</p>
<p>14:29 < jrandom> (since that means you have 20 full replicas of the file)</p>
<p>14:29 < hypercubus> users can always use standalone fec tools</p>
<p>14:29 < MikeW> jrandom: Under JobQueue, runners:1, active jobs:0, just finished:1, ready/waiting: 0, timed: 28</p>
<p>14:29 < aum> that means 20 goatses, guys :P</p>
<p>14:29 < hypercubus> and publish the results</p>
<p>14:29 < duck> what about the britneyspears effect?</p>
<p>14:29 < duck> of very popular keys ending up on 1 node</p>
<p>14:29 < jrandom> (aka insert a 740MB file and you get 14.8GB of data you need to send)</p>
<p>14:30 < aum> duck: popularity is not a concept in kademlia</p>
<p>14:30 < duck> (ofcourse with 32KB keys that might not be terrible)</p>
<p>14:30 < jrandom> ok cool MikeW, but is i2p eating your CPU now?</p>
<p>14:30 < deer><ardvark> all these kademlia messages I see on i2p are stasher related?</p>
<p>14:30 < MikeW> jrandom: yes</p>
<p>14:30 < aum> duck: and kademlia has no relaying</p>
<p>14:30 < hypercubus> ardvark: the stuff in the router console is the netdb kad implementation</p>
<p>14:31 < aum> the ideas of 'relaying', 'popularity', 'caching' etc are for freenet, which has to expose itself naked to the world, without the cloaking of I2P</p>
<p>14:31 < deer><ardvark> runnin i2p and tor here and my cpu usage is at 3% now so :/ *shrug*</p>
<p>14:31 < jrandom> MikeW: then your router is unable to maintain connections and is gobbling CPU doing lots of concurrent connection establishment</p>
<p>14:31 < duck> ok, my brain is rotten by freenet</p>
<p>14:31 < duck> please have mercy :)</p>
<p>14:31 < deer> * shendaras comforts.</p>
<p>14:31 < jrandom> MikeW: if you can hang around after the meeting to debug, that'd be great</p>
<p>14:32 < MikeW> will do</p>
<p>14:32 < jrandom> ok cool aum, anything people can do to help?</p>
<p>14:32 < jrandom> or should we just kick the tires and file bugs?</p>
<p>14:33 < duck> I am trying to get used to leo</p>
<p>14:33 < aum> yep, file bugs to the list, if that's ok people</p>
<p>14:33 < duck> already like it more than eclipse</p>
<p>14:33 < hypercubus> what's leo?</p>
<p>14:33 < jrandom> (uh oh, here comes the rant ;)</p>
<p>14:33 < aum> duck: i use nothing but leo these days - except emacs for quick hacks, and zile for even quicker hacks</p>
<p>14:34 < hypercubus> as long as you're not using vi or emacs ;-)</p>
<p>14:34 < aum> http://leo.sf.net - gives you an outline view of your code</p>
<p>14:34 < hypercubus> but i'll have to try this leo myself</p>
<p>14:34 < aum> leo even integrates with emacs if you want</p>
<p>14:34 < hypercubus> it's not an editor?</p>
<p>14:35 < aum><bile></p>
<p>14:35 < aum> fucking msvc - it allows __int64 for 64-bit ints, but doesn't allow 'LL' or 'ULL' for 64-bit int literals</p>
<p>14:35 < aum> !!</p>
<p>14:35 < aum></bile></p>
<p>14:35 < hypercubus> ah i see</p>
<p>14:37 < jrandom> ok, if thats that, then we've got nothing left and can move to 3) ???</p>
<p>14:37 < jrandom> anyone have anything else they want to bring up?</p>
<p>14:37 < hypercubus> yeah i guess i'll say a bit about the new direction of the installer</p>
<p>14:37 < jrandom> ok word</p>
<p>14:38 < hypercubus> from 0.4 onward, command line users will merely grab the i2p tarball and unpack it, then run a script to start the router and pop open the router console in lynx or whatever</p>
<p>14:39 < hypercubus> so not much has changed, except you don't have to go through a silly Q/A session with an installer</p>
<p>14:39 < hypercubus> you do all the configuration in the router console</p>
<p>14:39 < hypercubus> for GUI users, we have something spiffy</p>
<p>14:39 < jrandom> (w00t)</p>
<p>14:40 < hypercubus> which you can preview at http://files.hypercubus.i2p/install.jar</p>
<p>14:40 < jrandom> or from cvs (ant pkg ; java -jar install.jar) right?</p>
<p>14:40 < aum> hypercubus: how are you going with the winstaller? does it autodetect/autodownload/autoinstall java ?</p>
<p>14:41 < hypercubus> menu shortcuts are forthcoming, as well as systray integration and a way to install the router as a daemon</p>
<p>14:41 < aum> daemon? as in windows 'service' ?</p>
<p>14:41 < hypercubus> no, at least not for the forseeable future, they will need to click on a link on the i2p site that takes them to the official java download page</p>
<p>14:42 < hypercubus> the installer requires java, but that's ok since i2p does as well</p>
<p>14:42 < aum> hypercubus: sorry, but that'll lose 80% of users</p>
<p>14:42 < hypercubus> name one java project that doesn't do that</p>
<p>14:42 < jrandom> we'll have it eventually.</p>
<p>14:42 < jrandom> just not now.</p>
<p>14:42 < aum> freenet did it well - their winstaller takes you through the download</p>
<p>14:43 < jrandom> (we have so many other more important fish to fry. we dont *want* thousands upon thousands of users now)</p>
<p>14:43 < hypercubus> that's a consideration for 1.0</p>
<p>14:43 < hypercubus> i have most of the code to pull it off done already</p>
<p>14:43 < aum> jrandom: i thought you said it would be for 0.4</p>
<p>14:43 < deer><mule> so you should require that java is built from source :)</p>
<p>14:44 < jrandom> the new installer will be for 0.4</p>
<p>14:44 < hypercubus> we have scrapped all the code i have written thus far</p>
<p>14:44 < hypercubus> in favor of IzPack</p>
<p>14:44 < jrandom> we can offer a 15MB download bundling the two as one, but most users who will use i2p prior to 1.0 will know what "java" is</p>
<p>14:45 < hypercubus> this gives me time to perfect a fully public domain java installer framework which i eventually hope to move i2p back to</p>
<p>14:45 < hypercubus> but the priority right now is to get rid of the awful current installer ;-)</p>
<p>14:46 < hypercubus> (no offense to whoever hacked it together)</p>
<p>14:46 < deer><shendaras> Got a 404....</p>
