propagate from branch 'i2p.www' (head 76427e8477fdb3faaf94a7352015e957e2a6f1c0)
to branch 'i2p.www.revamp' (head 2b6601322d54558bb7f8923141d8b300928afdf7)
This commit is contained in:
str4d
@@ -1,7 +1,7 @@
|
||||
{% extends "global/layout.html" %}
|
||||
{% block title %}I2CP Specification{% endblock %}
|
||||
{% block lastupdated %}November 2012{% endblock %}
|
||||
{% block accuratefor %}0.9.3{% endblock %}
|
||||
{% block lastupdated %}December 2012{% endblock %}
|
||||
{% block accuratefor %}0.9.4{% endblock %}
|
||||
{% block content %}
|
||||
<h1>I2P Control Protocol (I2CP) Specification</h1>
|
||||
<h2>Overview</h2>
|
||||
|
||||
@@ -10,13 +10,28 @@ the most popular browsers.
|
||||
<h2>How to configure your browser</h2>
|
||||
|
||||
<ul>
|
||||
<li><a href="#ie8">Internet Explorer 8</a></li>
|
||||
<li><a href="#firefox">Firefox</a></li>
|
||||
<li><a href="#konqueror">Konqueror</a></li>
|
||||
<li><a href="#ie8">Internet Explorer 8</a></li>
|
||||
<li><a href="#TOS">Outproxy Terms Of Service</a></li>
|
||||
</ul>
|
||||
|
||||
|
||||
<a name="ie8"></a>
|
||||
<h3>Internet Explorer 8 or Chrome</h3>
|
||||
<p>
|
||||
In the tools menu select the "Internet Options" line to open the settings. In the
|
||||
settings window choose the connections tab and click on LAN settings for the
|
||||
proxy port configuration.</p>
|
||||
<img src="{{ url_for('static', filename='images/ie.options.jpg') }}" alt="IEOptions" title="IEOptions">
|
||||
<p>
|
||||
Now set the checkmark at "use a proxy server for your LAN" and at the "Bypass
|
||||
proxy server for local addresses". With a click on Advanced-button you open the
|
||||
window to open the ports. Enter the values like on the picture, IP 127.0.0.1
|
||||
and port 4444 for HTTP, port 4445 for HTTPS. With clicks on OK you save the
|
||||
settings and your browser is set to use the I2P proxy.</p>
|
||||
<img src="{{ url_for('static', filename='images/ie.proxyports.jpg') }}" alt="IEPPorts" title="PPorts">
|
||||
|
||||
<a name="firefox"></a>
|
||||
<h3>Firefox</h3>
|
||||
<p>
|
||||
@@ -49,21 +64,6 @@ localhost and click OK. Click the <em>New</em> button once more and enter
|
||||
<img src="{{ url_for('static', filename='images/konqueror.proxyports.jpg') }}" alt="" title="KPPorts">
|
||||
<br>
|
||||
|
||||
<a name="ie8"></a>
|
||||
<h3>Internet Explorer 8</h3>
|
||||
<p>
|
||||
In the tools menu select the "Internet Options" line to open the settings. In the
|
||||
settings window choose the connections tab and click on LAN settings for the
|
||||
proxy port configuration.</p>
|
||||
<img src="{{ url_for('static', filename='images/ie.options.jpg') }}" alt="IEOptions" title="IEOptions">
|
||||
<p>
|
||||
Now set the checkmark at "use a proxy server for your LAN" and at the "Bypass
|
||||
proxy server for local addresses". With a click on Advanced-button you open the
|
||||
window to open the ports. Enter the values like on the picture, IP 127.0.0.1
|
||||
and port 4444 for HTTP, port 4445 for HTTPS. With clicks on OK you save the
|
||||
settings and your browser is set to use the I2P proxy.</p>
|
||||
<img src="{{ url_for('static', filename='images/ie.proxyports.jpg') }}" alt="IEPPorts" title="PPorts">
|
||||
|
||||
<a name="TOS"></a>
|
||||
<h3>Outproxy Terms Of Service</h3>
|
||||
<p>
|
||||
|
||||
268
www.i2p2/pages/meeting211.html
Normal file
268
www.i2p2/pages/meeting211.html
Normal file
@@ -0,0 +1,268 @@
|
||||
{% extends "_layout.html" %}
|
||||
{% block title %}I2P Development Meeting 211{% endblock %}
|
||||
{% block content %}<h3>I2P dev meeting, December 4, 2012 @ 20:00 UTC</h3>
|
||||
<div>
|
||||
<h4>Quick recap</h4>
|
||||
<ul>
|
||||
<li><b>Present:</b>
|
||||
|
||||
dg,
|
||||
hottuna,
|
||||
KillYourTV,
|
||||
lillith,
|
||||
Meeh,
|
||||
psi,
|
||||
str4d,
|
||||
weltende,
|
||||
zzz
|
||||
</li>
|
||||
<li>
|
||||
<b>Next Meeting</b>
|
||||
<p>
|
||||
The next meeting is scheduled for Tuesday, December 11 @ 20:00 UTC (8:00PM)
|
||||
</p>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="irclog">
|
||||
<h4>Full IRC Log</h4>
|
||||
<pre>
|
||||
{% filter escape %}
|
||||
20:18:53 * KillYourTV has noticed that we're 17 minutes into the meeting...and we're off to a quiet start...
|
||||
20:19:31 <lillith> i was wondering that, did i also get the wrong time or something?
|
||||
20:20:23 * dg is waiting for self to be free
|
||||
20:20:30 <dg> some stuff needs wrapping up first
|
||||
20:20:33 <dg> sorry
|
||||
20:20:39 <dg> you guys can start without me if you need to
|
||||
20:23:07 * KillYourTV 's mostly going to be an observer due to his rather insignificant & unimportant roles...
|
||||
20:23:15 <KillYourTV> ...so start times matter not.
|
||||
20:23:39 <Meeh> I will be here, but I can wait until dg is ready
|
||||
20:23:42 <str4d> I wonder if it would be possible to have two IRC leaf connections to the same leaf to reduce netsplits...
|
||||
20:23:48 <dg> As long as nobody's becoming annoyed, I'll wait a little longer
|
||||
20:23:59 <dg> Hopefully $task won't be too much longer
|
||||
20:24:02 <str4d> (without doubling up on messages)
|
||||
20:24:05 <dg> str4d: not without srs mods to IRCd
|
||||
20:24:16 <dg> (or i2p hax?)
|
||||
20:24:22 * KillYourTV nices his tasks to give more CPU time to dg
|
||||
20:25:07 <str4d> There are already I2P mods for the IRCd so why not redundancy?
|
||||
20:25:50 <dg> actually
|
||||
20:25:50 <str4d> I guess it depends on the IRCd
|
||||
20:26:04 <dg> I kind of see the amount of IRC splits as a way of measuring network health
|
||||
20:26:19 <dg> For me, it says something about tunnel success :-P
|
||||
20:27:07 <str4d> Speaking of which.
|
||||
20:27:30 <KillYourTV> I don't know what mods were applied and why they were needed. (Back in the day ngircd needed a brief mod for b32 displaying...but with webirc it's not needed (and they're not displayed here anyway))
|
||||
20:28:00 <str4d> -_-
|
||||
20:49:54 <psi> orion: re: c++ i2p you mind if i add a build system to your code? probably scons
|
||||
20:54:16 <dg> I'm ready
|
||||
20:54:27 <dg> Sorry for the delay, folks
|
||||
20:55:01 * dg pings #i2p-dev
|
||||
21:03:16 <str4d> o/ dg
|
||||
21:04:09 <hottuna> 'lo dg
|
||||
21:05:07 <iRelay> <weltende@freenode> *waves*
|
||||
21:05:53 <psi> yay
|
||||
21:05:56 * psi timed out
|
||||
21:11:17 <hottuna> ready dg?
|
||||
21:13:23 <dg> sorry, I d/c'd
|
||||
21:13:26 <dg> What did I miss?
|
||||
21:13:26 <dg> <+iRelay> <weltende@freenode> *waves*
|
||||
21:13:26 <dg> »» chanserv gives voice to psi
|
||||
21:13:26 <dg> <+psi> yay
|
||||
21:13:26 <dg> »» +psi timed out
|
||||
21:13:26 <dg> »» s-771 is now known as s-77
|
||||
21:13:26 <dg> <+dg> yay!
|
||||
21:13:26 <dg> <+dg> Everyone woke up for me<3
|
||||
21:13:27 <dg> <+dg> weltende: Any news regarding mailing list? plz have some for me
|
||||
21:13:27 <Meeh> *waves*
|
||||
21:13:27 <hottuna> I dont think you missed anything
|
||||
21:13:27 <psi> yup
|
||||
21:13:27 <dg> alrighty
|
||||
21:13:27 <dg> So, weltende: ..
|
||||
21:14:37 <iRelay> <weltende@freenode> not really.. no time so far
|
||||
21:14:47 <iRelay> <weltende@freenode> kytv could do it.. he has root access to the box I had in mind afair ;-)
|
||||
21:14:50 * dg waits a few minutes
|
||||
21:15:41 * dg pokes KillYourTV
|
||||
21:17:30 <iRelay> <weltende@freenode> dg: and more cowbell!
|
||||
21:17:34 <iRelay> <weltende@freenode> err.. structure
|
||||
21:18:02 * dg was never any good at that, but he'll try
|
||||
21:18:12 * dg moves on
|
||||
21:18:15 <dg> KillYourTV: ping when back
|
||||
21:18:21 <dg> So, status updates.
|
||||
21:18:40 * str4d has ~40 mins, so GTFG fg ;P
|
||||
21:18:40 <KillYourTV> hmm? I didn't realize I had root but I can to throw some time at it (coursework & moving has taken up a considerable bit of time)
|
||||
21:18:40 <dg> Are they worth bringing back since we have the meetings (and hopefully the summaries of them, but they're not working out right now)?
|
||||
21:19:15 <str4d> dg, who would the status updates be for?
|
||||
21:19:22 <str4d> s/for/aimed at/
|
||||
21:19:25 <iRelay> str4d meant: dg, who would the status updates be aimed at?
|
||||
21:19:34 <dg> Well, I assume the previous ones which jrandom maintained were for those who wanted a TL;DR of the meetings
|
||||
21:20:06 <dg> Perhaps what we did with the last meeting (on the website) where the results were summarized at the top of the page
|
||||
21:20:31 <hottuna> They would be nice for the sake of community-building, but also a bit of work.
|
||||
21:20:49 * dg doesn't think it's a necessity as such but it'd be nice to say what the meeting accomplished/decided
|
||||
21:21:32 <hottuna> Would anyone like to do it?
|
||||
21:22:01 <str4d> On the site revamp I've taken the status updates as "blog entries"
|
||||
21:22:05 <str4d> So it might be better to write those, or structure the status updates as such.
|
||||
21:22:20 <hottuna> that sounds pretty good
|
||||
21:22:57 <str4d> (And since the blog will end up with RSS or whatever, that can then be used to feed into any other distribution lines that are desired)
|
||||
21:23:24 <psi> point 1: to consider, CCC
|
||||
21:23:27 <lillith> i was thinking after a meeting we could have a new thread on zzz.i2p, to allow people to reply with any follow up things from what has been discussed
|
||||
21:23:30 <psi> how will "this side" organize?
|
||||
21:23:55 <hottuna> I support the blog idea, however someone would have to do it.
|
||||
21:24:50 <psi> oh damn lag
|
||||
21:25:27 <str4d> And the status updates don't need to necessarily be too "minutes-y", since the meetings section of the revamp is where actual minutes should go (and I'm thinking that the minutes could be put into a feed as well, while the full logs are displayed with the minutes on the site)
|
||||
21:26:10 <zzz> dg, fyi, jr's status updates were sent out hours before each meeting, and they were not minutes of the previous meeting
|
||||
21:26:55 <str4d> Ah, thanks zzz - so more of a general get-everyone-up-to-speed-before-the-meeting update.
|
||||
21:27:10 <zzz> correct
|
||||
21:27:39 <zzz> dg, fyi, jr's status updates were sent out hours before each meeting, and they were not minutes of the previous meeting
|
||||
21:28:00 <dg> zzz: ah ok, it was a tl;dr of the $week?
|
||||
21:28:03 <dg> <+dg> Moving on?
|
||||
21:28:03 <dg> <+dg> psi: ccc is on the agenda :)
|
||||
21:28:03 <dg> ---» aquarium (grenze@irc2p) has joined #i2p-dev
|
||||
21:28:06 <dg> «--- w8rabbit (w8rabbit@irc2p) has quit (Killed (nickserv (Nick kill enforced)))
|
||||
21:28:06 <zzz> <str4d> Ah, thanks zzz - so more of a general get-everyone-up-to-speed-before-the-meeting update.
|
||||
21:28:06 <zzz> <zzz> correct
|
||||
21:28:09 <dg> <+dg> Next topic: * PR management role (http://zzz.i2p/topics/1299)
|
||||
21:28:09 <dg> <+dg> I don't know if the guy who posted that is here..
|
||||
21:28:09 <str4d> dg, repost: And the status updates don't need to necessarily be too "minutes-y", since the meetings section of the revamp is where actual minutes should go (and I'm thinking that the minutes could be put into a feed as well, while the full logs are displayed with the minutes on the site)
|
||||
21:28:24 <str4d> Yes he is - orion?
|
||||
21:28:34 <hottuna> dg, would you be willing to write a status update before meetings in the blog?
|
||||
21:29:16 <str4d> (he's in-chan at least)
|
||||
21:29:23 <str4d> And FTR this is the guy working on I2PCPP
|
||||
21:30:15 * psi is compiling i2pcpp
|
||||
21:31:12 <psi> i am also looking at the code as well
|
||||
21:32:58 <psi> i've got a SConstruct file
|
||||
21:36:03 <dg> damn rats eating the cables
|
||||
21:36:03 <dg> [repost]
|
||||
21:36:03 <dg> <+psi> i've got a SConstruct file
|
||||
21:36:05 <dg> <+dg> str4d:
|
||||
21:36:05 <dg> <+dg> * Website revamp updates
|
||||
21:36:05 <dg> <+dg> Anything?
|
||||
21:36:08 <dg> [/repost]
|
||||
21:36:12 <str4d> dg, need m0ar stables
|
||||
21:36:15 <str4d> =P
|
||||
21:36:21 <dg> :(
|
||||
21:36:36 <str4d> dg, I've got per-net urls working
|
||||
21:36:59 <dg> oh nice, progress
|
||||
21:37:02 <dg> How did you do it?
|
||||
21:37:06 * psi note to self don't compile with -j8 on a machine with 4 cores
|
||||
21:37:13 <str4d> So in the page files, if you put <a href="http://{{ i2pconv(trac.i2p2.i2p) }}/"> it will convert to trac.i2p2.de
|
||||
21:37:32 <str4d> And likewise for any other sites that have (hardcoded) known public urls.
|
||||
21:37:39 <str4d> Otherwise it appends .to
|
||||
21:38:16 <str4d> dg, problem was that Flask was caching filters applied to strings.
|
||||
21:38:19 <str4d> So it was eval-ed on first template read and then stored.
|
||||
21:38:39 <iRelay> <weltende@freenode> psi: unless it does multiple threads per core ;)
|
||||
21:38:43 <str4d> Turning the filter into a context processor (so the func is eval-ed on every request) did the job.
|
||||
21:38:46 <dg> Oh, ha
|
||||
21:39:34 <str4d> I can try generalize the function so you pass in the entire URL and it finds and changes the domain bit, if people would prefer to use it that way.
|
||||
21:39:45 <str4d> But it Works For Now (TM)
|
||||
21:40:01 <dg> psi:
|
||||
21:40:04 <dg> * CCC workshop/lightning talk discussion
|
||||
21:40:28 <psi> yes
|
||||
21:40:39 * psi reviews zzz.i2p link
|
||||
21:40:58 <str4d> (aside: Once I get some free time (after getting the bugs out of the feed mechanism) I'd like to work out the download mirroring stuff with welterde.)
|
||||
21:42:36 <iRelay> <weltende@freenode> str4d: well.. should be simple enough.. text file in mtn with list of all http, ftp mirrors..
|
||||
21:44:32 <iRelay> <weltende@freenode> (and in the backend just an rsync master site, from which all mirrors pull)
|
||||
21:44:40 <hottuna> did we choose a lightning talk topic?
|
||||
21:44:40 <psi> ok regarding CCC there is 0% chance for me to get the required docs to get there in time
|
||||
21:44:40 <psi> also... lots of "other stuff"
|
||||
21:44:40 <psi> in general I am overloaded due to finals
|
||||
21:44:40 <psi> also lag
|
||||
21:45:31 <str4d> welterde, I guessed so, but I'm not familiar with the current mirror setup.
|
||||
21:47:26 <str4d> The other thing, of course, is migrating the rest of the old pages across (and tidying up nav layout)
|
||||
21:48:06 <dg> <+psi> ok regarding CCC there is 0% chance for me to get the required docs to get there in time
|
||||
21:48:06 <dg> <+psi> also... lots of "other stuff"
|
||||
21:48:06 <dg> <+psi> in general I am overloaded due to finals
|
||||
21:48:06 <dg> <+psi> also lag
|
||||
21:48:06 <dg> <+dg> Could probably ask the audience who has used i2p before
|
||||
21:48:09 <dg> <+iRelay> <weltende@freenode> (and in the backend just an rsync master site, from which all mirrors pull)
|
||||
21:48:09 <dg> <+dg> psi: yeah, ech and welt are going though afaik
|
||||
21:48:11 <dg> <+str4d> welterde, I guessed so, but I'm not familiar with the current mirror setup.
|
||||
21:51:57 <str4d> Okay, heading off o/
|
||||
21:52:13 <dg> bye o/
|
||||
21:52:28 <dg> We really should have started earlier
|
||||
21:52:31 <dg> g'damnit
|
||||
21:52:47 <str4d> I'll see if I can be back in time for the end, but no guarantees.
|
||||
21:53:35 <dg> alright, stenography
|
||||
21:53:42 * dg pokes Meeh
|
||||
21:54:01 <psi> we need a generic interface for making transports
|
||||
21:54:04 <psi> (imo)
|
||||
21:54:23 <psi> s/need/should\ have/
|
||||
21:54:26 <iRelay> psi meant: we should\ have a generic interface for making transports
|
||||
21:55:08 <Meeh> I'm here, sorry just got disturbed with a phone call, back now
|
||||
21:55:16 <dg> afaik there's something called "restricted routes" but I don't know how they work
|
||||
21:55:19 <Meeh> *catchin up/reading log*
|
||||
21:55:22 <dg> (nor have they been implemented..?)
|
||||
21:55:28 <dg> Meeh: there isn't too much to read.. :(
|
||||
21:55:50 <psi> dg no docs on that?
|
||||
21:56:10 <dg> psi: mention on www.i2p2.i2p is all I found under roadmap or something..
|
||||
21:56:47 <psi> if anyone happens to remember what "restricted routes" are/were please speak up
|
||||
21:56:50 <lillith> dg, as i understand it restricted routes are like 'darknet mode' on freenet, you only connect via trusted peers
|
||||
21:56:57 <psi> ah
|
||||
21:57:16 <dg> ah
|
||||
21:57:31 <lillith> i think :)
|
||||
21:57:34 <psi> sounds like that could be it
|
||||
21:58:11 <dg> matches the name
|
||||
21:58:33 <lillith> it's been mentioned on zzz.i2p recently iirc
|
||||
21:59:40 <psi> if someone who does know for sure from way back when a "confirmation" would be great
|
||||
22:01:31 <lillith> http://zzz.i2p/topics/114
|
||||
22:04:31 * dg reads
|
||||
22:04:31 <lillith> it's not what i meant, but it explains pretty thoroughly
|
||||
22:06:02 <Meeh> just wondering, where are we in the meeting?
|
||||
22:06:13 <Meeh> what's current topic
|
||||
22:06:16 <dg> We're kind of floating around, Meeh
|
||||
22:06:23 <Meeh> ah ok
|
||||
22:06:31 <dg> "* Hide I2P traffic. Like Tor, hide so it looks like SSL traffic, or something. (Considering countries where darknets is illegal) "
|
||||
22:06:41 <dg> (We started late and thus sucking)
|
||||
22:08:10 <Meeh> yea, we should think about possible alternative transport for countries blocking and making darknets illegal
|
||||
22:09:47 <lillith> well to start with: how distinctive is i2p traffic now?
|
||||
22:09:50 <hottuna> I think we ought to play something like that the same way tor does
|
||||
22:09:50 <hottuna> and deploy it not before it is needed
|
||||
22:09:50 <hottuna> as to prolong any arms-race
|
||||
22:09:50 <hottuna> but we haven't been blocked anywhere yet
|
||||
22:09:50 <hottuna> as far as I know
|
||||
22:10:05 <dg> (yet)
|
||||
22:10:25 <dg> Also, the lack of this sort of "protection" i.e system keeps some away from i2p
|
||||
22:10:32 <psi> in general a generic transport api would be a developer's goldmine
|
||||
22:10:32 <hottuna> we have a lot of random data, but none of the headers of ssl
|
||||
22:10:57 <dg> obfsproxy is amazing but we don't need something of that level
|
||||
22:11:48 <psi> some interface that you'd implement that does your version of data transport wether it's over goats or http+ssl
|
||||
22:11:50 <iRelay> <weltende@freenode> psi: we already have a generic transport api ;)
|
||||
22:11:54 <lillith> i2p can't really be 'too secure'
|
||||
22:12:02 <hottuna> a transport api would be a good idea, and would allow for rapid development of needed transports
|
||||
22:12:14 <psi> we do eh?
|
||||
22:12:36 <psi> i need to look at the code closer
|
||||
22:12:56 <psi> either it's not sticking out well or i over looked it or it's not there
|
||||
22:13:03 <Meeh> yea, yet.. it's a matter of time
|
||||
22:13:36 <iRelay> <weltende@freenode> router/java/src/net/i2p/router/transport/Transport.java is the interface you have implement
|
||||
22:13:36 <dg> certainly not, lillith
|
||||
22:13:46 <dg> although i2p is already a lot of crypto
|
||||
22:14:17 <hottuna> i think obfsproxy is horrible, and it's tacked onto tor in the most frankenstein-y fashion possible
|
||||
22:14:40 <dg> I don't like their pluggable transports but the tech is cool
|
||||
22:14:48 <dg> (emulating Skype is one cool thing)
|
||||
22:17:27 <psi> iirc obsproxy can be counter productive
|
||||
22:17:33 <hottuna> i've gotta go
|
||||
22:17:46 <psi> due to it emulating a survalence network
|
||||
22:17:53 * psi spelling
|
||||
22:18:00 <dg> bye
|
||||
22:19:55 <psi> i've got to part for now as well
|
||||
22:20:27 <dg> I think we can just call it a day now and have it next week/sometime soon(er)
|
||||
22:20:34 <dg> Kind of fucked this one up
|
||||
22:21:04 <iRelay> <weltende@freenode> sounds like a plan
|
||||
22:21:07 <psi> it's best to have a predefine meeting structure
|
||||
22:21:54 <dg> yeah
|
||||
22:26:10 <Meeh> disconnected...
|
||||
22:26:29 <Meeh> 23:10:30 <+psi> in general a generic transport api would be a developer's goldmine
|
||||
22:26:32 <Meeh> 23:10:31 < hottuna> we have a lot of random data, but none of the headers of ssl
|
||||
22:26:35 <Meeh> 23:13:01 <+Meeh> yea, yet.. it's a matter of time
|
||||
22:26:38 <Meeh> 23:13:15 <+Meeh> so why make people offline from i2p for a while.. better safe than sorry
|
||||
22:26:41 <Meeh> what did I miss?
|
||||
22:27:11 <psi> Meeh: meeting adjurned for now
|
||||
22:27:11 * psi spelling
|
||||
22:27:58 <psi> <dg> certainly not, lillith
|
||||
22:27:58 <Meeh> ah, lame.. meeting next week?
|
||||
22:28:10 * psi lag
|
||||
22:28:55 <lillith> Meeh, to be decided, maybe before since this one wasn't a great success
|
||||
22:29:25 <Meeh> true true, next week then
|
||||
{% endfilter %}
|
||||
{# TODO: pygments #}
|
||||
</pre>
|
||||
</div>
|
||||
{% endblock %}
|
||||
106
www.i2p2/pages/meeting212.html
Normal file
106
www.i2p2/pages/meeting212.html
Normal file
@@ -0,0 +1,106 @@
|
||||
{% extends "_layout.html" %}
|
||||
{% block title %}I2P Development Meeting 212{% endblock %}
|
||||
{% block content %}<h3>I2P dev meeting, December 11, 2012 @ 20:00 UTC</h3>
|
||||
<div>
|
||||
<h4>Quick recap</h4>
|
||||
<ul>
|
||||
<li><b>Present:</b>
|
||||
|
||||
lillith,
|
||||
Meeh,
|
||||
postman,
|
||||
psi,
|
||||
str4d,
|
||||
topiltzin,
|
||||
zzz
|
||||
</li>
|
||||
<li>
|
||||
<b>Next Meeting</b>
|
||||
<p>
|
||||
The next meeting is scheduled for Tuesday, December 18 @ 20:00 UTC (8:00PM)
|
||||
</p>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="irclog">
|
||||
<h4>Full IRC Log</h4>
|
||||
<pre>
|
||||
{% filter escape %}
|
||||
20:20:09 <str4d> <str4d> Not sure where dg is, so I propose that we get the meeting started anyway, continuing on with the agenda from last week (or restarting it if necessary).
|
||||
20:20:09 <str4d> (http://zzz.i2p/posts/5779)
|
||||
20:20:18 <iRelay> Title: zzz.i2p: IRC Meetings (at zzz.i2p)
|
||||
20:40:14 <str4d> No one going to reply?
|
||||
20:41:48 <Meeh> I'm in for a meeting
|
||||
20:42:09 <Meeh> but IRC was really unstable today
|
||||
20:51:48 <str4d> Does someone want to chair and start a meeting? No idea where dg has got to, and I've got to leave partway though so I can't.
|
||||
20:52:40 <str4d> Looks like iRelay is on postman's server, so if the chair is also there then disconnects won't affect the meeting log.
|
||||
21:01:13 <psi> meeting was...?
|
||||
21:01:32 * lillith volunteers to chair once i have zzz.i2p loaded succesfully
|
||||
21:04:05 <psi> meeting is now rite?
|
||||
21:05:43 <lillith> yep unless anyone else wants to chair
|
||||
21:07:16 <psi> ok
|
||||
21:07:16 <psi> topics?
|
||||
21:07:16 <lillith> So, Carrying on from where we left off last week, orion are you in here?
|
||||
21:09:52 <psi> sounds doable
|
||||
21:09:54 <lillith> i'm not sure what for though, seems a little pointless to me at least
|
||||
21:10:20 <psi> to make a more structured environment for helping users
|
||||
21:10:27 <psi> iirc
|
||||
21:10:48 <topiltzin> more like pool resources
|
||||
21:11:05 <topiltzin> +1 on that but iirc someone had to be asked first (the owner of the channel? who is/was that?)
|
||||
21:11:13 <lillith> so combine two fairly dead channels to a less dead one?
|
||||
21:11:50 <topiltzin> yah
|
||||
21:12:23 <lillith> okay item 2a: who owns each cannel and what do they think?
|
||||
21:12:50 <lillith> 2b: is the new channel #i2p or #i2p-help?
|
||||
21:12:57 * postman owns #i2p and thinks nothing in particular
|
||||
21:13:31 <postman> #i2p should keep its name
|
||||
21:13:33 <lillith> 2c: ask someone to delete one and redirect people to the other
|
||||
21:13:38 <postman> zzz owns #i2p-help
|
||||
21:14:10 <psi> i suppose the ircd can do a "symlink" of sorts for channels?
|
||||
21:14:12 <lillith> i think new users need an obvious 'help' channel to go to first when they connect
|
||||
21:14:31 <lillith> otherwise they will just ask in random channels
|
||||
21:14:51 <postman> re: symlink. i will check that
|
||||
21:16:35 <lillith> okay, item 2 dealt with?
|
||||
21:18:16 <lillith> item 3: website revamp updates.
|
||||
21:18:35 <lillith> str4d, any news?
|
||||
21:18:37 <psi> how many are working on that?
|
||||
21:23:13 <lillith> psi: afaik only str4d
|
||||
21:28:17 <lillith> re: Item 4 : 0.9.4 Console links additions, i think str4d has gone and books isn't here, maybe next week?
|
||||
21:28:17 <str4d> lillith, about to go afk
|
||||
21:28:26 <str4d> But website page reorganization is basically done.
|
||||
21:33:45 <str4d> I'd like some feedback from people on it (navigation and url structure) - see ticket #807 for the live url
|
||||
21:33:48 <iRelay> http://trac.i2p2.i2p/ticket/807 - (accepted enhancement) - Revamp of website
|
||||
21:33:50 <str4d> And that ticket also lists the next todo items for the revamp.
|
||||
21:33:50 <lillith> okay, thanks :)
|
||||
21:34:09 <lillith> item 5 ; 0.9.4 release
|
||||
21:35:46 <lillith> zzz, are you still aiming for mid-december?
|
||||
21:39:52 <zzz> monday. see also /topic and http://zzz.i2p/topics/1252
|
||||
21:39:55 <zzz> and re: console link additions, that agenda item can be pushed out 6 weeks for 0.9.5
|
||||
21:45:02 <lillith> okay thanks :)
|
||||
21:45:09 <lillith> item 6 : any notes from participants
|
||||
21:45:09 <lillith> ... anyone?
|
||||
21:45:09 <psi> notes?
|
||||
21:45:09 <lillith> anything you wish to add
|
||||
21:45:09 <psi> the most common complaint from new users is that it's slow at start
|
||||
21:45:22 <psi> is there any way to address that?
|
||||
21:49:54 <Meeh> make the installer include RIs could help on the startup speed. But it's not a flawless solution
|
||||
21:49:54 <Meeh> what if dose RIs goes down, or high load, etc etc
|
||||
21:49:54 <psi> is there a "faster" way to initial seed besides prebundling?
|
||||
21:49:54 <zzz> Meeh, is your reseed server script at all a bottleneck? is it slowing down reseeding at all?
|
||||
21:49:54 <Meeh> higher the limit before the router stop reseeding to 2-300.. But not a flawless idea either
|
||||
21:49:54 <lillith> Meeh,surely any solution would be better than none
|
||||
21:49:54 <Meeh> it slows the server down if it's much used since it's a write lock on sqlite
|
||||
21:49:56 <Meeh> I should make a mysql version, and those reseeders that could use it, would help a lot
|
||||
21:51:20 <lillith> prebundling RIs could only speed up initial startup; worst case is that it's the same as now
|
||||
21:51:20 <Meeh> then the file/db lock wouldn't be a bottleneck anymore
|
||||
21:52:49 <Meeh> or whatever else *sql as long as it run as a server
|
||||
22:01: <lillith> orion dosen't seem to be here, and i don't see how we can go on without him
|
||||
22:04: <lillith> item 7: next meeting
|
||||
22:06: <topiltzin> pre-bundling has some strong arguments against it, they are available on zzz.i2p
|
||||
22:07: <lillith> i'l leave this to dg , presumably it will be 8.00 UTC next tuesday (18th)
|
||||
22:08: <lillith> topiltzin, i'l take a look
|
||||
22:09: <lillith> I'd say this meeting is now officially over then :)
|
||||
{% endfilter %}
|
||||
{# TODO: pygments #}
|
||||
</pre>
|
||||
</div>
|
||||
{% endblock %}
|
||||
@@ -4,6 +4,7 @@
|
||||
<h1>Past I2P Release Announcements</h1>
|
||||
<h4>2012</h4>
|
||||
<ul class="infolist">
|
||||
<li>2012-12-17 - <a href="release-0.9.4.html">0.9.4</a></li>
|
||||
<li>2012-10-27 - <a href="release-0.9.3.html">0.9.3</a></li>
|
||||
<li>2012-09-21 - <a href="release-0.9.2.html">0.9.2</a></li>
|
||||
<li>2012-07-30 - <a href="release-0.9.1.html">0.9.1</a></li>
|
||||
|
||||
71
www.i2p2/pages/release-0.9.4.html
Normal file
71
www.i2p2/pages/release-0.9.4.html
Normal file
@@ -0,0 +1,71 @@
|
||||
{% extends "_layout.html" %}
|
||||
{% block title %}0.9.4 Release{% endblock %}
|
||||
{% block content %}
|
||||
|
||||
<p>0.9.4 includes a fix for a network capacity bug, introduced in 0.9.2,
|
||||
that was reducing network performance and reliability. It also includes
|
||||
major changes in the in-network update system, and adds the capability
|
||||
to update via in-network torrents. </p>
|
||||
|
||||
<p>We fixed several bugs in the i2psnark DHT implementation that was introduced
|
||||
last release. For those of you using console or http proxy passwords,
|
||||
we converted to the more-secure digest method and improved the security for console forms.</p>
|
||||
|
||||
<p>For those of you already running development builds, your router should automatically
|
||||
update to 0.9.4-0 using the new in-network torrent facility.
|
||||
For those running 0.9.3-0, you will update normally using in-network HTTP, and
|
||||
we will have more information for you when we release 0.9.5.</p>
|
||||
|
||||
<p>Files are available on the <a href="/download.html">download page</a>.</p>
|
||||
|
||||
<p><strong>RELEASE DETAILS</strong></p>
|
||||
|
||||
<p><strong>Major Changes</strong></p>
|
||||
|
||||
<p>- Big rework of the update system; Preliminary support for updates via i2psnark
|
||||
<br />- Add per-destination outbound priorities</p>
|
||||
|
||||
<p><strong>Bug Fixes</strong></p>
|
||||
|
||||
<p>- Fix major bug that reduced SSU connection limits which reduced tunnel build success rates
|
||||
<br />- Fix bug with external I2CP that prevented some external apps from working
|
||||
<br />- Fixed several bugs in i2psnark DHT
|
||||
<br />- Fixed bug in i2psnark PEX that inflated peer counts
|
||||
<br />- Handle dropped I2CP messages better
|
||||
<br />- Reduce overhead of I2CP messages
|
||||
<br />- Enforce max size in transport outbound message queues
|
||||
<br />- Fixes for Windows eepget.bat (new installs and PPA only)
|
||||
<br />- Fix a bug that would drop messages of exactly 512 bytes in SSU</p>
|
||||
|
||||
<p><strong>Other</strong></p>
|
||||
|
||||
<p>- More performance improvements, memory reduction, and object churn reduction
|
||||
<br />- Better detection of network disconnections
|
||||
<br />- Further improvements in the SSU transport
|
||||
<br />- Add console password form
|
||||
<br />- Convert http proxy and console from basic to digest authentication for added security
|
||||
<br />- Improved verification of console form submissions, using jsp sessions. Cookies may now be required on forms, except when the console password is enabled
|
||||
<br />- Initial work on new interfaces to manage applications started via clients.config
|
||||
<br />- Increase minimum peer port to 1024
|
||||
<br />- Increase granularity of bandwidth limiter for smoother transmissions
|
||||
<br />- Translation updates: Chinese, French, German, Italian, Polish, Portuguese, Swedish, and Ukrainian
|
||||
<br />- Update GeoIP data (new installs and PPA only)
|
||||
<br />- Update wrapper to 3.5.16 (new installs and PPA only)
|
||||
<br />- New ARMv6 wrapper for Raspberry Pi</p>
|
||||
|
||||
<b>
|
||||
SHA256 Checksums:
|
||||
</b>
|
||||
<pre>
|
||||
|
||||
c76bea15a6b7d98227466cc8025b1eb9069997e40e9d71ff49e55b2c8ac0b995 i2pinstall_0.9.4_windows.exe
|
||||
8e670ba26c04176ace9246d91a09951975e2965b89628f620f5a3dff917298e4 i2pinstall_0.9.4.jar
|
||||
1b7d9695555ed42142b04ad6bcda083cd1a064f6354b639ad2aef4d9cd474e06 i2psource_0.9.4.tar.bz2
|
||||
0f369d9b85793f157ec67c4d59723a2ad0c1de2a0902d35e11c26a2c74add824 i2pupdate_0.9.4.zip
|
||||
6e55d3c44d79b0727f5cd4075df4248e4d78f1736911e3504f6a8af45d973cfc i2pupdate.su2
|
||||
561e521a707fab457c9dfe166d41b446affbff5bc58ddf770d192235f51f4e90 i2pupdate.sud
|
||||
|
||||
|
||||
</pre>
|
||||
|
||||
{% endblock %}
|
||||
@@ -6,6 +6,7 @@
|
||||
</h1>
|
||||
<h4>2012</h4>
|
||||
<ul class="infolist">
|
||||
<li>2012-12-17 - <a href="release-0.9.4.html">0.9.4</a></li>
|
||||
<li>2012-10-27 - <a href="release-0.9.3.html">0.9.3</a></li>
|
||||
<li>2012-09-21 - <a href="release-0.9.2.html">0.9.2</a></li>
|
||||
<li>2012-07-30 - <a href="release-0.9.1.html">0.9.1</a></li>
|
||||
|
||||
@@ -5,6 +5,7 @@
|
||||
<p>Hinweis: Da i2p.net nicht erreichbar ist, sind viele Verweise nicht funktional</p>
|
||||
<h4>2012</h4>
|
||||
<ul class="infolist">
|
||||
<li>2012-12-17 - <a href="release-0.9.4.html">0.9.4</a></li>
|
||||
<li>2012-10-27 - <a href="release-0.9.3.html">0.9.3</a></li>
|
||||
<li>2012-09-21 - <a href="release-0.9.2.html">0.9.2</a></li>
|
||||
<li>2012-07-30 - <a href="release-0.9.1.html">0.9.1</a></li>
|
||||
|
||||
@@ -4,6 +4,7 @@
|
||||
<h1>Προηγουμενες ανακοινωσεις των εκδοσεων του I2P</h1>
|
||||
<h4>2012</h4>
|
||||
<ul class="infolist">
|
||||
<li>2012-12-17 - <a href="release-0.9.4.html">0.9.4</a></li>
|
||||
<li>2012-10-27 - <a href="release-0.9.3.html">0.9.3</a></li>
|
||||
<li>2012-09-21 - <a href="release-0.9.2.html">0.9.2</a></li>
|
||||
<li>2012-07-30 - <a href="release-0.9.1.html">0.9.1</a></li>
|
||||
|
||||
@@ -4,6 +4,7 @@
|
||||
<h1>Historique des versions publiées</h1>
|
||||
<h4>2012</h4>
|
||||
<ul class="infolist">
|
||||
<li>2012-12-17 - <a href="release-0.9.4.html">0.9.4</a></li>
|
||||
<li>2012-10-27 - <a href="release-0.9.3.html">0.9.3</a></li>
|
||||
<li>2012-09-21 - <a href="release-0.9.2.html">0.9.2</a></li>
|
||||
<li>2012-07-30 - <a href="release-0.9.1.html">0.9.1</a></li>
|
||||
|
||||
@@ -4,6 +4,7 @@
|
||||
<h1>Versioni di I2P Rilasciate e Annunciate</h1>
|
||||
<h4>2012</h4>
|
||||
<ul class="infolist">
|
||||
<li>2012-12-17 - <a href="release-0.9.4.html">0.9.4</a></li>
|
||||
<li>2012-10-27 - <a href="release-0.9.3.html">0.9.3</a></li>
|
||||
<li>2012-09-21 - <a href="release-0.9.2.html">0.9.2</a></li>
|
||||
<li>2012-07-30 - <a href="release-0.9.1.html">0.9.1</a></li>
|
||||
|
||||
Reference in New Issue
Block a user