16:00 < jrandom> 0) hi
16:00 < jrandom> 1) Net status
16:00 < jrandom> 2) Peer filtering
16:00 < jrandom> 3) Syndie status
16:00 < jrandom> 4) ???
16:00 < jrandom> 0) hi
16:00  * jrandom waves
16:01 < jrandom> weekly status notes posted up @ http://dev.i2p.net/pipermail/i2p/2006-May/001291.html
16:01 < jrandom> (up an hour early, even [or a few weeks late, if you want to pick on me ;])
16:02 < jrandom> ok, lets jump on in to 1) Net status
16:02 < jrandom> things arent in the shape they should be in.  they're better than they were during the congestion collapse, but it should be better than it is now
16:03 < jrandom> i don't have much more to add on that though, unless anyone has any questions/concerns on 1)?
16:03 <@frosk> i get days of irc connection with .19, so no complaints here
16:04 < jrandom> nice
16:04 < jrandom> yeah, its good for some, just not good enough or consistent enough.  stats in the db aren't looking that great either
16:06 < jrandom> ok, anyone have anything else on 1) Net status, or shall we move on over to 2)Peer filtering?
16:07 < jrandom> [insert moving sounds here]
16:09 < jrandom> as mentioned in the mail, the gist of things is to give our peer selection a bit of a boost.  at first, it'll be a bit dangerous, allowing some active partitioning attacks, but if it works as I hope, we can avoid those
16:10 < jrandom> (but avoiding it requires essentially killing all router identities, which would essentially serve as a network reset, so i'd like to avoid that unless its worthwhile)
16:11 < bar> reset them once or repeatedly?
16:11 < bar> s/reset/killing
16:11 < jrandom> at least once, but also on all subsequent drastic config changes
16:12 < jrandom> (aka putting some criteria into the router identity's certificate, which in turn means changing the ident hash, so they can't pretend to push one setting to some people and others to others)
16:13 < bar> gotcha
16:14 < jrandom> ok, i dont think i have anything else on that topic atm, unless anyone has any questions/comments/concerns?
16:15 < jrandom> (hopefully there'll be a build out in the next day or two, release after it stabilizes)
16:17 < jrandom> ok, hitting 3) briefly..
16:18 < jrandom> syndie is coming along, and although the amd64/amd32/x86/swt/gcj battle hasn't always been pretty, we'll have a build ready in june
16:19 < jrandom> (but still don't talk to me about mingw/gcj ;)
16:19 < jrandom> i don't have much more to add on there at the moment though, unless anyone has any questions/concerns re: the syndie revamp?
16:21 <@cervantes> how's mingw/gcj support coming along?
16:21 <@cervantes> *duck*
16:22 <@cervantes> do we get some screenies before the june release? :)
16:23 < jrandom> i'm sure i'll try to rope some eager volunteers into pre-release testing ;)
16:23 < tethrar> count me in ;)
16:23 < jrandom> w3wt
16:24 < jrandom> ok, lets swing over to the bullet point i know y'all have been waiting for: 4) ???
16:24 < jrandom> wazaaaap?
16:24 < green> Is there any plan to have to have a "real" working I2P router with Via C7 ? jbigi give only 30% better than full java
16:25 < jrandom> is 30% still too cpu intensive?  what makes it not "real"?
16:25 < jrandom> but no, i do not have the math or c7 asm skill to make a better libGMP for C7.
16:25 < green> sure too cpu intensive with 100% cpu load :P
16:26 < jrandom> 100% cpu load suggests that the problem isn't jbigi, but theHTTP/1.1 200 OK
Set-Cookie: i_like_gitea=7eec691810ee3789; Path=/; HttpOnly; Secure; SameSite=Lax
Set-Cookie: _csrf=273OtnQFUdZyoUn_ncaWdohtv0M6MTc1MzI1NDkwNDY5OTM5NjkyOQ; Path=/; Max-Age=86400; HttpOnly; Secure; SameSite=Lax
X-Content-Type-Options: nosniff
Cache-Control: public, max-age=21600, no-transform
Connection: close
Access-Control-Expose-Headers: Content-Disposition
Content-Type: text/plain; charset=utf-8
Etag: "14d99618c68d33a09266007babf27348553f6962"
Date: Wed, 23 Jul 2025 07:15:04 GMT
Content-Disposition: inline; filename="181.log"; filename*=UTF-8''181.log
Content-Length: 4078
X-Frame-Options: SAMEORIGIN
Last-Modified: Wed, 19 Dec 201