forked from I2P_Developers/i2p.www
134 lines
12 KiB
HTML
134 lines
12 KiB
HTML
{% extends "_layout.html" %}
|
|
{% block title %}Pages/meeting145.html{% endblock %}
|
|
{% block content %}<h3>I2P dev meeting, August 30, 2005</h2>
|
|
<div class="irclog">
|
|
<p>13:03 <+bla> Is there a meeting today?</p>
|
|
<p>13:04 < jrandom> 0) hi</p>
|
|
<p>13:04 < jrandom> 1) Net status</p>
|
|
<p>13:04 < jrandom> 2) floodfill netDb</p>
|
|
<p>13:04 < jrandom> 3) Syndie</p>
|
|
<p>13:04 < jrandom> 4) ???</p>
|
|
<p>13:04 < jrandom> 0) hi</p>
|
|
<p>13:04 <+bla> ;)</p>
|
|
<p>13:04 * jrandom waves</p>
|
|
<p>13:04 < jrandom> weekly status notes posted up at http://dev.i2p.net/pipermail/i2p/2005-August/000871.html</p>
|
|
<p>13:04 < jrandom> (yeah, i'm a few minutes late ;)</p>
|
|
<p>13:05 < jrandom> anyway, jumping into 1) net status</p>
|
|
<p>13:06 < jrandom> restricted routes suck, and we finally have some data as to how common they are (boo hiss)</p>
|
|
<p>13:06 < jrandom> but stil, the net seems fairly healthy, if you ignore all the worried reports of "omg it says status: Unknown!" ;)</p>
|
|
<p>13:07 < gloin> hmm.. where should be the document root for the i2p included webserver?</p>
|
|
<p>13:07 < jrandom> $i2pInstallDir/eepsite/docroot/</p>
|
|
<p>13:07 < gloin> i2p/eepsite/docroot ?</p>
|
|
<p>13:07 < jrandom> anyone have any questions/comments/concerns regarding the net status outside of whats posted in the status notes?</p>
|
|
<p>13:08 < gloin> found it. it seems that the webserver won't deliver index.html automatically.</p>
|
|
<p>13:08 <+bla> jrandom: I have been doing some tests to check which nodes are selected in tunnels.</p>
|
|
<p>13:09 <+bla> jrandom: Mainly, as I've now implemented node-localization in the RouterInfo struct, I can see graphically (country flags) were tunnel participants are located.</p>
|
|
<p>13:09 <+bla> I am in Europe (no secret), and most of my tunnel participants are in Europe</p>
|
|
<p>13:09 < jrandom> gloin: it should serve up the index.html (thats what renders "Welcome to your Eepsite")</p>
|
|
<p>13:10 < jrandom> ooh nice1 bla!</p>
|
|
<p>13:10 < redzara> as some people have reported some low perf with UDP, maybe we could had a little perfmeter like iperf in I2P ?</p>
|
|
<p>13:11 < redzara> s/had/add</p>
|
|
<p>13:11 < jrandom> bla: so thats not just on the profiles.jsp page, but also on tunnels.jsp? v.cool... screenshots, screenshots! :)</p>
|
|
<p>13:11 < gloin> jrandom: now it works. strange.</p>
|
|
<p>13:11 <+bla> jrandom: I'll post some screenshots, but I first have to black out my own router-ID in the screenshots ;)</p>
|
|
<p>13:11 < jrandom> redzara: hmm, a command line utility to let people check their link quality, or a monitor for SSU performance?</p>
|
|
<p>13:11 < jrandom> heh bla</p>
|
|
<p>13:12 < jrandom> odd gloin </p>
|
|
<p>13:13 < gloin> jrandom: btw, since I updated my pppoe i2p seems to be more stable.</p>
|
|
<p>13:13 < jrandom> nice, what was the problem with your net connection? firmware update?</p>
|
|
<p>13:14 < gloin> jrandom: I lost all peers. But the internet connection was ok, but every peer failed. </p>
|
|
<p>13:16 < jrandom> right, but what did you update about your pppoe settings?</p>
|
|
<p>13:17 < gloin> jrandom: I mean the linux ppppoe deamon.</p>
|
|
<p>13:18 < jrandom> ah ok</p>
|
|
<p>13:18 < jrandom> ok, anyone else have anything for 1) net status, or shall we move on to 2) floodfill netdb?</p>
|
|
<p>13:18 <+bla> http://theland.i2p/parttunnels.jpg</p>
|
|
<p>13:19 <+bla> http://theland.i2p/servertunnels.jpg</p>
|
|
<p>13:21 <+bar> (umm.. inaccessible?)</p>
|
|
<p>13:21 < jrandom> yeah, i'm having trouble reaching it too</p>
|
|
<p>13:21 < fox> <godmode0> i use pppoe never be at problem i2p</p>
|
|
<p>13:22 * jrandom will try later though</p>
|
|
<p>13:22 <+bla> jrandom: Well.. There's new network problem just there ;)</p>
|
|
<p>13:22 < jrandom> hehe</p>
|
|
<p>13:22 < jrandom> bla: are you on -4 or an earlier build?</p>
|
|
<p>13:23 <+bla> jrandom: I'm on -4</p>
|
|
<p>13:23 < jrandom> hmm, ok cool</p>
|
|
<p>13:23 < jrandom> ok, anyway, we can dig through that later</p>
|
|
<p>13:24 < jrandom> (if you could send me the netDb stats from /oldstats.jsp, that'd be great :)</p>
|
|
<p>13:25 < jrandom> ok, moving on to 2) floodfill netdb</p>
|
|
<p>13:26 < jrandom> there's lots of info posted to my blog on this topic</p>
|
|
<p>13:26 < jrandom> we've begun deploying a first pass, though there's still some work to be done</p>
|
|
<p>13:26 < jrandom> does anyone have any questions/comments/concerns on the plan?</p>
|
|
<p>13:27 <+bla> jrandom: Will the floodfill scale as log(N) (N=number of peers in the net), or linearly?</p>
|
|
<p>13:27 < jrandom> linearly with M (M= number of peers participating in the floodfill netdb)</p>
|
|
<p>13:28 < jrandom> well, M may be small enough that N is the dominant term</p>
|
|
<p>13:29 < jrandom> (in which case it'll be linearly with N)</p>
|
|
<p>13:29 < jrandom> which is not great, but until we have > 10K eepsites, it doesnt matter</p>
|
|
<p>13:30 < jrandom> once we do, then we can go into more advanced algorithms for sharing the load between the floodfill participants</p>
|
|
<p>13:31 < jrandom> (note thats 10k eepsites, not users, since we don't really need to publish client leaseSets in the netdb)</p>
|
|
<p>13:32 <+bla> jrandom: Is there a reason why we still do publish the client destinations in the netDb?</p>
|
|
<p>13:32 <+bla> jrandom: Or, for that matter, why we still show off who our fast peers are in the netDb?</p>
|
|
<p>13:33 <+bla> jrandom: Removing both would slash the netDb data by a big factor</p>
|
|
<p>13:33 < jrandom> bla: to the former, no. to the later, for me to debug (though i havent looked at that particular field recently)</p>
|
|
<p>13:33 < jrandom> aye, worth trying, perhaps in -5</p>
|
|
<p>13:36 < jrandom> ok coo', well, we'll see and hopefully get -5 out in the next few days</p>
|
|
<p>13:37 < jrandom> (maybe tomorrow)</p>
|
|
<p>13:37 < jrandom> ok, if there's nothing else on 2) floodfill netdb, lets move on to 3) syndie</p>
|
|
<p>13:38 < jrandom> i posted a bunch of info in the mail and on my blog, so rather than rehash them, does anyone have any questions / comments / concerns?</p>
|
|
<p>13:40 * jrandom really digs the remote syndication functionality, though its far from what we're hoping for with feedspace integration</p>
|
|
<p>13:41 < jrandom> (i havent been bothered to do freenet posting integration, though it would be quite easy to fire up a CLI and post all the entries in)</p>
|
|
<p>13:42 < jrandom> ok, if there's nothing else on 3) syndie, lets open 'er up to 4) ???</p>
|
|
<p>13:42 < jrandom> anyone have anything else i2p related to bring up?</p>
|
|
<p>13:42 < redzara> sure, where is the doc ;)</p>
|
|
<p>13:43 < laberhorst> just that my node under 0.6.x sonsumes up to 100% cpu load, but have to crosscheck it with linux on that line here</p>
|
|
<p>13:43 <+nickless_head> I think the i2pProxy.pac script should be in the jetty web folder by default.</p>
|
|
<p>13:43 < jrandom> nickless_head: i dont recommend i2pproxy.pac, as its a huge security risk</p>
|
|
<p>13:44 < redzara> 2 - could be have the latest build of jetty included in I2P ?</p>
|
|
<p>13:44 < jrandom> we've got 5.2.1 in i2p right now</p>
|
|
<p>13:44 < jrandom> er, 5.1.2</p>
|
|
<p>13:44 <+nickless_head> jrandom: it's the only thing available for separating between eepsites and websites in one browser without having to switch by hand afaik</p>
|
|
<p>13:45 < jrandom> i use switchproxy</p>
|
|
<p>13:45 < jrandom> (and i dont switch to non-anonymous browsing)</p>
|
|
<p>13:45 < jrandom> ((squid.i2p is fast enough for me))</p>
|
|
<p>13:45 <+nickless_head> Think of the slashdotters! :p</p>
|
|
<p>13:46 < jrandom> as i've said before, i have reservations about the viability of eepsites. the security risks are tremendous</p>
|
|
<p>13:46 < jrandom> but, for those who don't care about those risks, perhaps an i2pproxy.pac makes sense.</p>
|
|
<p>13:47 <+bla> I strongly think that something that isn't secure by _default_, shouldn't be in I2P, as to not give new users a false sense of secutiry</p>
|
|
<p>13:48 < jrandom> agreed (though we do push i2pproxy.pac, we just dont tell people about it until we scare 'em enough ;)</p>
|
|
<p>13:49 <+nickless_head> I somehow can't believe that within the configuration of Mozilla there isn't a way to make sites only access resources from the same domain .. </p>
|
|
<p>13:50 < redzara> sorry but IRC connection lost :( about jetty there is a fix about common logging and maybe this help me running my mvnforum in the same instance of I2P</p>
|
|
<p>13:50 < redzara> Jetty-5.1.5rc1 - 23 August 2005</p>
|
|
<p>13:52 < jrandom> ah cool, whats the problem exactly redzara?</p>
|
|
<p>13:52 < jrandom> nickless_head: if you find a way, let us know</p>
|
|
<p>13:52 < redzara> or maybe i could even only build my own I2P with the latest version of jetty</p>
|
|
<p>13:52 < jrandom> redzara: that you certainly can do - just drop in the jetty jar files into your i2p lib directory</p>
|
|
<p>13:53 < redzara> jrandom : everythime i try to start mvnforum in I2P, jetty failed to find apache common logging</p>
|
|
<p>13:53 <+nickless_head> Oh! I just noticed that the default i2pproxy.pac uses a mode which allows sites to switch proxy'ing to i2p on and off at runtime, which is protected by the TOTALLY SECURE AND UNBREAKABLE </sarcasm> default password "passw0rd". Please, someone who knows about cvs change this.</p>
|
|
<p>13:54 < jrandom> redzara: thats in commons-logging.jar and commons-el.jar iirc, which should be in your lib dir and in your wrapper.config's classpath</p>
|
|
<p>13:54 < jrandom> nickless_head: yet another reason why i dont recommend anyone use it ;)</p>
|
|
<p>13:55 < redzara> yes i know, i'm not so n00b :)) i've to dig into again with this new version of jetty</p>
|
|
<p>13:56 < jrandom> cool, keep us updated</p>
|
|
<p>13:56 < redzara> np</p>
|
|
<p>13:57 < fox> * mihi guesses most i2p users will reveal their "real ip" to a java applet anyway :)</p>
|
|
<p>13:57 < fox> <mihi> try http://www.stilllistener.com/checkpoint1/Java/ (and scroll down)</p>
|
|
<p>13:58 * jrandom sees lots of blank fields ;)</p>
|
|
<p>13:59 <+bla> fox: All one exposes is the relation between an IP and a particular client destination, where the client destination will change at every router restart.</p>
|
|
<p>13:59 < jrandom> bla: unless the user is on some site like e.g. http://i_have_illegal_stuff.i2p/</p>
|
|
<p>14:00 < jrandom> (exposing the clients IP "just once" is fatal enough ;)</p>
|
|
<p>14:00 <+bla> jrandom: Yes. </p>
|
|
<p>14:00 <+bla> But then again, if you're serious about anonymous browsing, you'll use temporary HTTP proxies, and disable all things java, and plugins, and cookies, entirely</p>
|
|
<p>14:01 < jrandom> or use syndie :)</p>
|
|
<p>14:02 < ZULU> sorry for interruption,is duck.ip down ?</p>
|
|
<p>14:02 <+bla> jrandom: Is it time yet for general questions?</p>
|
|
<p>14:02 < jrandom> aye, we're on 4) ???</p>
|
|
<p>14:02 < jrandom> ZULU: yeah, duck is offline for the time being</p>
|
|
<p>14:03 <+bla> jrandom: I've edited the java-files that help profiles.jsp and tunnels.jsp generate the country-flags</p>
|
|
<p>14:04 <+bla> jrandom: However, where do I place images that I can actually LINK to, and that will work, on my local router (_not_ my eepsite)?</p>
|
|
<p>14:06 < jrandom> we need a "get.jsp?name" that dumps the contents of ./docs/'name' to the browser</p>
|
|
<p>14:06 < jrandom> (aka you need to have it in the .war right now, but with a tiny .jsp file, you could dump 'em in docs)</p>
|
|
<p>14:06 <+bla> jrandom: Ah, ok, so it wasn't my fault ;)</p>
|
|
<p>14:06 < jrandom> heh nope, blame me :)</p>
|
|
<p>14:09 < jrandom> ok, if there's nothing else for the meeting</p>
|
|
<p>14:09 * jrandom winds up</p>
|
|
<p>14:10 * jrandom *baf*s the meeting closed</p>
|
|
</div>
|
|
{% endblock %} |