16:01 < jrandom> 0) hi
16:01 < jrandom> 1) Net status
16:01 < jrandom> 2) Syndie dev status
16:01 < jrandom> 3) ???
16:01 < jrandom> 0) hi
16:01  * jrandom waves
16:01 < jrandom> weekly status notes posted up at http://dev.i2p.net/pipermail/i2p/2006-October/001314.html
16:02 <+fox> * dm waves
16:02 < jrandom> w3wt, ok, while y'all read that oh-so-fun missive, lets jump on to 1) net status
16:03 < jrandom> the net seems to be maintaining the steady state right now, though with a slight growth trend
16:04 < jrandom> there are some discussions on the big cpu-related issue on the forum, though no big win yet, afaics
16:04 < jrandom> anyone have anything to bring up re: 1) net status?
16:05 < jrandom> (the last full week w/ 0.6.1.26 seems to have gone well [yay])
16:06 <+fox> <dm> well, I better say something
16:06 <+fox> <dm> is there a consistent metric that is being used to monitor net status
16:06 <+fox> <dm> or is it just ad-hoc experiences?
16:07 <+fox> <dm> like is there an application out there that tries to connect to random places every day while measuring response times and failures.
16:07 < jrandom> i'm going largely by irc behavior, as well as the stats and activity on the routers i run (stats.i2p is down for a week or two, but it usually is a solid enchmark to run against)
16:08 <+fox> <dm> cool, I'll check that site out.
16:08 < jrandom> there are several people running stat monitoring apps - orion.i2p, tino.i2p, eepsites.i2p, as well as stats.i2p
16:09 <+fox> <dm> thank you!
16:09 < jrandom> np :)
16:09 < jrandom> ok, if there's nothing else on 1), lets jump on over to 2) syndie dev status
16:10 < jrandom> lots going on, as mentioned in the status notes (and you can finally see a non-hideous-looking website at syndie.i2p.net :)
16:11 <+fox> <dm> down at the moment?
16:11 <+fox> <dm> scratch that
16:11 <+fox> * dm shuts up
16:11 < jrandom> :)
16:12 < marlowe> jrandom, the diagram on the front page is very helpful
16:12 < marlowe> i know understand the concept behind syndie
16:12 <+fox> <dm> it's pretty as well
16:13 <+fox> <dm> but how do you access syndie without download/installing it? I remember you could do this before?
16:13 < jrandom> great, glad its clear marlowe - it can be a confusing concept in just text :)
16:13 < jrandom> dm: the old syndie (syndiemedia.i2p.net/) was web based, but this new one is, well, brand new, completely redesigned
16:14 <+fox> <dm> it's not web-based?
16:14 < jrandom> (and thanks to cervantes for turning my ugly ms-paint-style image into the slick pic you see there :)
16:14 < jrandom> no, its not web based - current release is actually text only, but work continues on a gui
16:14 < jrandom> http://syndie.i2p.net/roadmap.html
16:14 <+fox> <dm> text-only! wow. ok. downloading.
16:14 < jrandom> w3wt
16:15 < jrandom> one important thing you need to know to effectively use it is the location of a syndie archive that you can push posts to and pull posts from
16:15 <+fox> <dm> wow.. this is hardcore stuff. (Next Command:) hehhehe
16:15 < jrandom> there's currently one at http://syndie.i2p.net/archive - you can sync up with that via "menu syndicate" "getindex --archive http://syndie.i2p.net/archive" and "fetch" :)
16:16 < jrandom> its a fairly simple system, though with very specific design features
16:16 < jrandom> (and incredibly robust - it can run on anything :)
16:17 <+fox> <dm> there's something cool abouHTTP/1.1 200 OK
Connection: close
Content-Disposition: inline; filename="185.log"; filename*=UTF-8''185.log
Set-Cookie: i_like_gitea=c07ed55b61b97457; Path=/; HttpOnly; Secure; SameSite=Lax
Set-Cookie: _csrf=wVdlHEo0FRMT-Fb75-ypuEg6Fj06MTc1MzI4MzQ4MTk0MjA1MDY0Mg; Path=/; Max-Age=86400; HttpOnly; Secure; SameSite=Lax
Etag: "eb79fabe83c649fea434977788a35216e4f35a8e"
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Access-Control-Expose-Headers: Content-Disposition
Last-Modified: Wed, 19 Dec 2012 06:58:07 GMT
Date: Wed, 23 Jul 2025 15:11:21 GMT
Cache-Control: public, max-age=21600, no-transform
Content-Length: 5683
Content-Type: text/plain; charset=utf-8
X-Cache-Status: HIT
X-Cache-Age: 0

16:01 < jrandom> 0) hi
16:01 < jrandom> 1) Net status
16:01 < jrandom> 2) Syndie dev status
16:01 < jrandom> 3) ???
16:01 < jrandom> 0) hi
16:01  * jrandom waves
16:01 < jrandom> weekly status notes posted up at http://dev.i2p.net/pipermail/i2p/2006-October/001314.html
16:02 <+fox> * dm waves
16:02 < jrandom> w3wt, ok, while y'all read that oh-so-fun missive, lets jump on to 1) net status
16:03 < jrandom> the net seems to be maintaining the steady state right now, though with a slight growth trend
16:04 < jrandom> there are some discussions on the big cpu-related issue on the forum, though no big win yet, afaics
16:04 < jrandom> anyone have anything to bring up re: 1) net status?
16:05 < jrandom> (the last full week w/ 0.6.1.26 seems to have gone well [yay])
16:06 <+fox> <dm> well, I better say something
16:06 <+fox> <dm> is there a consistent metric that is being used to monitor net status
16:06 <+fox> <dm> or is it just ad-hoc experiences?
16:07 <+fox> <dm> like is there an application out there that tries to connect to random places every day while measuring response times and failures.
16:07 < jrandom> i'm going largely by irc behavior, as well as the stats and activity on the routers i run (stats.i2p is down for a week or two, but it usually is a solid enchmark to run against)
16:08 <+fox> <dm> cool, I'll check that site out.
16:08 < jrandom> there are several people running stat monitoring apps - orion.i2p, tino.i2p, eepsites.i2p, as well as stats.i2p
16:09 <+fox> <dm> thank you!
16:09 < jrandom> np :)
16:09 < jrandom>