180 lines
9.7 KiB
HTML
180 lines
9.7 KiB
HTML
{% extends "_layout.html" %}
|
|
{% block title %}I2P Development Meeting 18{% endblock %}
|
|
{% block content %}
|
|
<h3>I2P (invisiblenet) Development Meeting 18</h3>
|
|
<div class="irclog">
|
|
Courtesy of <a href="http://www.archive.org/">the wayback machine</a>.
|
|
<p>
|
|
<p>--- Log opened Tue Nov 05 23:14:03 2002
|
|
<p>23:14 < logger> test
|
|
<p>23:55 < nop> hineo
|
|
<p>23:55 < Neo> hinop
|
|
<p>23:57 < nop> hi hezekiah
|
|
<p>--- Day changed Wed Nov 06 2002
|
|
<p>00:00 < Neo> 23:00:00.00 UTC
|
|
<p>00:00 < nop> ok
|
|
<p>00:00 < nop> welcome
|
|
<p>00:00 < nop> I kind of want to wait, looks like a relay died
|
|
<p>00:00 < nop> just another minute
|
|
<p>00:00 < nop> so that people can re-assimilate ;)
|
|
<p>00:01 < hezekiah> Yeah. I got bumped out about 30 seconds ago.
|
|
<p>00:01 < nop> right
|
|
<p>00:01 < nop> ok
|
|
<p>00:01 < nop> ok
|
|
<p>00:01 < nop> welcome to the n-th iip-dev meeting
|
|
<p>00:02 < hezekiah> 18th!
|
|
<p>00:02 < nop> I think it's like the 18th
|
|
<p>00:02 < nop> yes
|
|
<p>00:02 < nop> thnx
|
|
<p>00:02 < nop> on the agenda
|
|
<p>00:02 < nop> 1) welcome <-- we're doing this now
|
|
<p>00:02 < nop> 2) agenda list <-- we're doing this now
|
|
<p>00:02 < nop> 3) ;)
|
|
<p>00:03 < nop> 4) IIP logo
|
|
<p>00:03 < nop> 5) Dev report
|
|
<p>00:03 < nop> 6) RC3 (coming soon, we promise)
|
|
<p>00:03 < nop> 7) questions
|
|
<p>00:03 < nop> .
|
|
<p>00:03 < nop> ok we did the welcome and the agenda
|
|
<p>00:03 < nop> let's do the ;)
|
|
<p>00:03 < nop> ;)
|
|
<p>00:04 < nop> Ok IIP logo
|
|
<p>00:04 < nop> and slogan
|
|
<p>00:04 < co> Where can we see the logos that have been submitted?
|
|
<p>00:04 < nop> none have really been submitted
|
|
<p>00:04 < nop> except one
|
|
<p>00:04 < nop> and I submitted a slogan for InvisibleNet
|
|
<p>00:04 < nop> I'll tell you mine
|
|
<p>00:05 < nop> front part of shirt "You can't attack what you can't see..."
|
|
<p>00:05 < nop> then back would say
|
|
<p>00:05 < nop> InvisibleNet
|
|
<p>00:05 < nop> then there's this other one, I'll mail to iip-dev
|
|
<p>00:05 < nop> but no one else seems to care
|
|
<p>00:05 < nop> so... :(
|
|
<p>00:06 < nop> then again
|
|
<p>00:06 < nop> no one seems to want to buy shirts for IIP anyway
|
|
<p>00:06 < nop> so... what can ya do
|
|
<p>00:06 < nop> yes we're working on getting black shirts
|
|
<p>00:06 < nop> next on the agenda
|
|
<p>00:06 < nop> Dev report
|
|
<p>00:07 < nop> same ol' same ol' dev is working on the core control
|
|
<p>00:08 < nop> userx will give a brief summary
|
|
<p>00:08 < hezekiah> *applause*
|
|
<p>00:09 < UserX> core control will provide a system for being able to support multiple cores in iip. each core is esssentially network protocol
|
|
<p>00:10 < UserX> .
|
|
<p>00:10 < nop> ok
|
|
<p>00:10 < nop> thank you UserX
|
|
<p>00:10 < nop> man of many words
|
|
<p>00:10 < nop> ;)
|
|
<p>00:10 < nop> or woman
|
|
<p>00:10 < nop> never know
|
|
<p>00:10 < nop> anyway
|
|
<p>00:10 < nop> RC3
|
|
<p>00:11 < nop> it's on it's way out the door, I believe there is an openbsd compatibility that was reported and from what I know, it's been patched and cvs'd
|
|
<p>00:11 < nop> (for some reason, I haven't got a listserv about it)
|
|
<p>00:11 < nop> but we're hoping that this weekend would be a good time to do an RC3 upgrade
|
|
<p>00:11 < nop> and it's not going to conflict with rc2 in any way
|
|
<p>00:12 < nop> just mostly bug fixes
|
|
<p>00:12 < nop> Questions
|
|
<p>00:12 < nop> anyone?
|
|
<p>00:12 < codeshark> so everything is in cvs now?
|
|
<p>00:12 < dj28> yea
|
|
<p>00:12 < dj28> i have a stupid one
|
|
<p>00:12 < dj28> when will the IIP core server migrate away from the irc protocol?
|
|
<p>00:12 < nop> codeshark - I believe so, please check with UserX to make sure he's comfortable with it
|
|
<p>00:13 < nop> this is what the core control dev work puts us in a position to do
|
|
<p>00:13 < dj28> and when will it become completely distributed?
|
|
<p>00:13 < dj28> oh ok
|
|
<p>00:13 < nop> so then we'll be able to build upon that
|
|
<p>00:13 < UserX> codeshark: it will be once my server is talking to the internet again
|
|
<p>00:13 < nop> and we hope to have 1.2 a fully distributed version
|
|
<p>00:13 < dj28> ok. cool
|
|
<p>00:13 < nop> at least at communication level
|
|
<p>00:13 < nop> the routing might still be run through inform
|
|
<p>00:14 < nop> but the communication should be decentralized
|
|
<p>00:14 < nop> similar to how freenet 0.3 was
|
|
<p>00:14 < dj28> yea
|
|
<p>00:14 < nop> any other questions?
|
|
<p>00:15 < co> So a core is a package of encryption algorithms that allow network communication?
|
|
<p>00:15 < co> Explain that concept again, please.
|
|
<p>00:15 < Mak> wow ...i jumped here ...sorry ...
|
|
<p>00:16 < nop> well
|
|
<p>00:16 < nop> a core is a network protocol
|
|
<p>00:16 < nop> this puts us in a modular position
|
|
<p>00:16 < nop> to possibly support many routing architectures
|
|
<p>00:16 < Neo> oooh nice...
|
|
<p>00:17 < nop> this could position us to support many protocols
|
|
<p>00:18 < nop> the core control is similar to an API for cores
|
|
<p>00:19 < nop> any more questions?
|
|
<p>00:19 < co> Thank you.
|
|
<p>00:19 < nop> np
|
|
<p>00:21 < nop> oh
|
|
<p>00:21 < nop> one more thing
|
|
<p>00:22 < nop> Many thanks to Phiberoptika for her fine translation of the El Pais newspaper article done on IIP
|
|
<p>00:22 < nop> it appears in spanish and with english translation (done by Phiberoptika) on the iip site www.invisiblenet.net/iip
|
|
<p>00:22 < nop> it's a good article
|
|
<p>00:22 < hezekiah> Cool! I'll have to check that out! Thanks, Phiberoptika! :)
|
|
<p>00:22 < al-jabr> I have a question...
|
|
<p>00:22 < nop> yes sir
|
|
<p>00:22 < al-jabr> Two questions
|
|
<p>00:22 < nop> sure
|
|
<p>00:22 < al-jabr> I had one problem
|
|
<p>00:23 < al-jabr> running IIP in linux, don't know if it's actually an IIP problem
|
|
<p>00:23 < al-jabr> after I killed isproxy
|
|
<p>00:23 < al-jabr> and tried to run again, it couldn't bind to the port
|
|
<p>00:23 < al-jabr> had this problem a couple times, had to change the port number
|
|
<p>00:23 < al-jabr> but when i logged of and on again (a few days later) the port was available
|
|
<p>00:24 < al-jabr> so I'm not sure that's directly an issue with isproxy
|
|
<p>00:24 < hezekiah> Is this reproducable, or just a random happening?
|
|
<p>00:24 < nop> right, if you wait like 1 minute with RC2 you can rebind
|
|
<p>00:24 < UserX> was something connected to it when you killed it?
|
|
<p>00:24 < al-jabr> i'll try to reproduce it
|
|
<p>00:24 < al-jabr> but
|
|
<p>00:24 < al-jabr> no, nothing was connected to 6667
|
|
<p>00:25 < nop> oh that port
|
|
<p>00:25 < nop> hmm
|
|
<p>00:25 < al-jabr> and it happened like three or four times and i had to keep changing ports
|
|
<p>00:25 < al-jabr> yeah
|
|
<p>00:25 < al-jabr> not the other one
|
|
<p>00:25 < Phiberoptika> re:article: ;)!!!, no problem chicos..
|
|
<p>00:25 < al-jabr> i haven't reproduced it since then, but i haven't been trying
|
|
<p>00:25 < nop> hehe
|
|
<p>00:25 < al-jabr> since i rarely go restarted isproxy
|
|
<p>00:26 < al-jabr> i should probably try to. also, i was experiencing a lot of problems with the network for the last few days
|
|
<p>00:26 < Povert> I have a question....
|
|
<p>00:26 < al-jabr> and i don't know if it's something local
|
|
<p>00:26 < UserX> odd. the only reason i know for that to happen is that if the connection is closed properly it will be left hanging and you have to wait for the OS to time it out
|
|
<p>00:26 < Povert> is de openbsd thing realy solved?
|
|
<p>00:26 < al-jabr> or if it's not really any worse than it's usually been
|
|
<p>00:27 < al-jabr> because, before the last couple days, i got kicked off, maybe a couple times a day at MOST, then all of the sudden i was getting kicked off every few minutes, and sometimes not getting on at all, and sometimes lagging
|
|
<p>00:27 < UserX> al-jabr: did you try using netstat to see if there were any lingering connections to port 6667
|
|
<p>00:27 < al-jabr> and changing node.refs didn't seem to help
|
|
<p>00:27 < al-jabr> no, i should have investigated that
|
|
<p>00:27 < al-jabr> silly me
|
|
<p>00:27 < al-jabr> i'll try it a bit more and i'll do that
|
|
<p>00:28 < al-jabr> i didn't think that there could be connections on the other end after the server is killed
|
|
<p>00:28 < nop> would netstat give a TIME_WAIT?
|
|
<p>00:29 < hezekiah> Also, sometimes a process of isproxy hangs (but that only has happened to me when I'm debugging buggy code.) You should be able to check to see if there are still a hanging process of isproxy by doing: ps -e | grep isproxy
|
|
<p>00:29 < al-jabr> i did that
|
|
<p>00:29 < al-jabr> no isproxies were running
|
|
<p>00:29 < hezekiah> Good. :)
|
|
<p>00:30 < al-jabr> no, bad.
|
|
<p>00:30 < al-jabr> but anyway, i'll investigate that some more, probably not a big issue
|
|
<p>00:32 < Povert> nop
|
|
<p>00:32 < Povert> is openbsd kompilation ready solved?
|
|
<p>00:32 < Neo> diff -r1.2 sock.h
|
|
<p>00:32 < Neo> 45c45
|
|
<p>00:32 < Neo> < #elif defined(__FreeBSD__) || defined(__MACH__)
|
|
<p>00:32 < Neo> ---
|
|
<p>00:32 < Neo> > #elif defined(__FreeBSD__) || defined(__MACH__) || defined(__OpenBSD__)
|
|
<p>00:33 < Povert> in codetree I meen
|
|
<p>00:34 < nop> it's about to be committed
|
|
<p>00:34 < Povert> ok
|
|
<p>00:34 < Povert> dank
|
|
<p>00:34 < nop> yep
|
|
<p>00:37 < nop> any more questions?
|
|
<p>00:42 < nop> thanks for attending
|
|
<p>00:42 < nop> .
|
|
</div>
|
|
{% endblock %}
|