16:18 < jrandom> 0) hi
16:18 < jrandom> 1) 0.6.0.6
16:18 < jrandom> 2) I2Phex 0.1.1.27
16:18 < jrandom> 3) migration
16:18 < jrandom> 4) ???
16:18 < jrandom> 0) hi
16:18  * jrandom waves
16:18 < jrandom> weekly status notes posted up @ http://dev.i2p.net/pipermail/i2p/2005-September/000929.html
16:18 <+postman> hello
16:18 < forest> hi
16:18 < jrandom> lets jump on in to 1) 0.6.0.6
16:19 < jrandom> the status notes cover pretty much what i've got on my mind for 0.6.0.6.  anyone have any questions/concerns/comments to bring up?
16:19 <+postman> jrandom: observation:
16:19 <+postman> jrandom: much higher bandwidth consumption
16:20 <+postman> jrandom: all within the limits and running fine - but my routers really getting warm now
16:20  * nickless_head makes similar observation
16:20 < jrandom> aye, me too, i think its likely due to an increase in bt and i2phex traffic
16:20 <+postman> what increase, with just 80 active torrents on the tracker? :)
16:20 < jrandom> heh
16:21 <+postman> but its good to see, that the network does not crumble
16:21 <+postman> irc is pretty stable altho the router does 50k/s atm
16:21 < jrandom> mos' def'.  i'm not even logged into freenode anymore, as irc here is stable enough
16:22  * postman hands the mike back
16:22 < jrandom> cool, thanks.  i think there's definitely still room to go for bandwidth efficiency, but it seems reasonable atm
16:22 < jrandom> (hopefully the thing i'm working on will help, but more on that when its ready)
16:22 < fox> <mihi> you should definitely distinguish between OK (Nat) and Err (Nat)...
16:23 < fox> <mihi> or is your hole punching almighty?
16:23 < jrandom> heh
16:23 < jrandom> well, ERR-SymmetricNAT is and will continue to be an ERR
16:23 < fox> <mihi> or is it impossible to check whether it was successful?
16:24 < fox> <mihi> ok
16:24 < jrandom> but ERR-Reject is due to restricted cone, while full cone nats work fine
16:24 < jrandom> (since i2p uses only one source port for everyone, as long as you're on i2p you'll have a hole punched for the full cone)
16:25 < jrandom> still, it is better when people forward their ports so they don't need introducers, as that lets them also become introducers themselves
16:25 < fox> <mihi> as long as there are no nasty iptables rules (like drop UDP to 8887 from IP addresses divisable by 7 :) )
16:25 < jrandom> heh
16:26 < jrandom> and unfortunately, some people do have b0rked configurations like that (*cough*peerguardian*cough*)
16:26 < jrandom> someone the other day was wondering why i2p didn't work, even though they had their firewall dropping packets from all .edu peers
16:27 <+Ragnarok> .edu?  That's pretty random
16:27 < jrandom> yeah, made no sense to me, in so many ways
16:27 < jrandom> but, c'est la vie
16:27  * nickless_head sings: We don't need no education...
16:28 < jrandom> heh
16:28 < jrandom> ok, anyone else have anything on 1) 0.6.0.6?
16:29 < jrandom> if not, moving on to 2) i2phex 0.1.1.27
16:29 < jrandom> not much to say here beyond whats in the mail either...
16:30 <+postman> jrandom: there was no positive response in the mentioned forums either :(
16:31 <+postman> jrandom: i will forward your statusnotes and links - maybe the readers get the point
16:31 < jrandom> postman: people are of course able to use whatever they want, but I don't recommend the binary release from legion as the source doesn't match the binary, and the lauHTTP/1.1 200 OK
Connection: close
Cache-Control: public, max-age=21600, no-transform
Etag: "57296ccf44a5ebafa4b3b3e35e51a52964110416"
X-Frame-Options: SAMEORIGIN
Content-Disposition: inline; filename="148.log"; filename*=UTF-8''148.log
Content-Type: text/plain; charset=utf-8
Access-Control-Expose-Headers: Content-Disposition
Content-Length: 6393
Last-Modified: Wed, 19 Dec 2012 06:58:07 GMT
Set-Cookie: i_like_gitea=eb402ba31acf27ca; Path=/; HttpOnly; Secure; SameSite=Lax
Set-Cookie: _csrf=vImES8MOyfa3UPkadgQSfAR8H3Y6MTc1MzI1NDkxNjQwMzU1NjY0NA; Path=/; Max-Age=86400; HttpOnly; Secure; SameSite=Lax
X-Content-Type-Options: nosniff
Date: Wed, 23 Jul 2025 07:15:16 GMT
X-Cache-Status: HIT
X-Cache-Age: 0

16:18 < jrandom> 0) hi
16:18 < jrandom> 1) 0.6.0.6
16:18 < jrandom> 2) I2Phex 0.1.1.27
16:18 < jrandom> 3) migration
16:18 < jrandom> 4) ???
16:18 < jrandom> 0) hi
16:18  * jrandom waves
16:18 < jrandom> weekly status notes posted up @ http://dev.i2p.net/pipermail/i2p/2005-September/000929.html
16:18 <+postman> hello
16:18 < forest> hi
16:18 < jrandom> lets jump on in to 1) 0.6.0.6
16:19 < jrandom> the status notes cover pretty much what i've got on my mind for 0.6.0.6.  anyone have any questions/concerns/comments to bring up?
16:19 <+postman> jrandom: observation:
16:19 <+postman> jrandom: much higher bandwidth consumption
16:20 <+postman> jrandom: all within the limits and running fine - but my routers really getting warm now
16:20  * nickless_head makes similar observation
16:20 < jrandom> aye, me too, i think its likely due to an increase in bt and i2phex traffic
16:20 <+postman> what increase, with just 80 active torrents on the tracker? :)
16:20 < jrandom> heh
16:21 <+postman> but its good to see, that the network does not crumble
16:21 <+postman> irc is pretty stable altho the router does 50k/s atm
16:21 < jrandom> mos' def'.  i'm not even logged into freenode anymore, as irc here is stable enough
16:22  * postman hands the mike back
16:22 < jrandom> cool, thanks.  i think there's definitely still room to go for bandwidth efficiency, but it seems reasonable atm
16:22 < jrandom> (hopefully the thing i'm working on will help, but more on that when its ready)
16:22 < fox> <mihi> you should definitely distinguish between OK (Nat) and Err (Nat)...
16:23 < fox> <mihi> or is your hole punching almighty?
16:23 < jrandom> heh
16:23 < jrandom> well, ERR-SymmetricNAT is and will continue to be an ERR
16:23 < fox> <mihi> or is it impossible to check whether it was successful?
16:24 < fox> <mihi> ok
16:24 < jrandom> but ERR-Reject is due to restricted cone, while full cone nats work fine
16:24 < jrandom> (since i2p uses only one source port for everyone, as long as you're on i2p you'll have a hole punched for the full cone)
16:25 < jrandom> still, it is better when people forward their ports so they don't need introducers, as that lets them also become introducers themselves
16:25 < fox> <mihi> as long as there are no nasty ip