propagate from branch 'i2p.www' (head e3db0e6a87a9bdf9505016ef90069beb21cadb69)
to branch 'i2p.www.revamp' (head 6b55da3ed369752ad914f36b972ab52e6652af88)
This commit is contained in:
str4d
@ -15,7 +15,9 @@ function get_revision_cert_trust(signers, id, name, val)
|
||||
"walking@mail.i2p", "neutron@mail.i2p", "HungryHobo@mail.i2p", "russiansponsor@mail.i2p",
|
||||
"echelon@mail.i2p", "forget@mail.i2p", "privateer@mail.i2p", "duck@mail.i2p",
|
||||
"m1xxy@mail.i2p", "hiddenz@mail.i2p", "dev@robertfoss.se", "hamada@mail.i2p",
|
||||
"magma@mail.i2p", "kytv@mail.i2p", "str4d@mail.i2p", "meeh@mail.i2p" }
|
||||
"magma@mail.i2p", "kytv@mail.i2p", "str4d@mail.i2p", "meeh@mail.i2p",
|
||||
"zab@mail.i2p"
|
||||
}
|
||||
local t = intersection(signers, trusted_signers)
|
||||
if t == nil then return false end
|
||||
if table.getn(t) >= 1 then return true end
|
||||
|
||||
@ -7,6 +7,8 @@ If you have something to discuss, please find the developers on IRC in #i2p-dev.
|
||||
<a href="{{ url_for('blog_index', lang=g.lang) }}">Status updates</a> from developers are also available.
|
||||
</p><div class="underline"></div>
|
||||
<ul class="infolist">
|
||||
<li><a href="meeting210">Meeting 210</a> - November 27, 2012</li>
|
||||
<li><a href="meeting209">Meeting 209</a> - November 20, 2012</li>
|
||||
{%- macro meeting_url(m_id) -%}{{ url_for('meetings_show', lang=g.lang, id=m_id) }}{%- endmacro -%}
|
||||
<li><a href="{{ meeting_url(208) }}">Meeting 208</a> - September 8, 2010</li>
|
||||
<li><a href="{{ meeting_url(207) }}">Meeting 207</a> - February 10, 2009</li>
|
||||
|
||||
@ -497,7 +497,7 @@ Contact us if you would like to help.
|
||||
<a href="http://www.imule.i2p/">IMule</a>
|
||||
</li><li>
|
||||
<a href="http://forum.i2p/viewforum.php?f=25">I2Phex</a> - contact Complication
|
||||
<a href="http://forum.i2p2.de/viewforum.php?f=25">(outside I2P)</a>
|
||||
<!--<a href="http://forum.i2p2.de/viewforum.php?f=25">(outside I2P)</a> -->
|
||||
</li><li>I2PRufus - contact codevoid
|
||||
</li><li>I2P-BT - contact sponge
|
||||
</li><li><a href="http://bob.i2p">BOB</a> - contact sponge
|
||||
|
||||
@ -689,6 +689,47 @@ R2VFZ/114yCNY74KmujA
|
||||
=jfFH
|
||||
-----END PGP SIGNATURE-----
|
||||
|
||||
zab:
|
||||
|
||||
-----BEGIN PGP SIGNED MESSAGE-----
|
||||
Hash: SHA1
|
||||
|
||||
I declare that:
|
||||
|
||||
Unless marked otherwise, all code I commit is implicitly licensed
|
||||
under the component's primary license
|
||||
If specified in the source, the code may be explicitly licensed under
|
||||
one of the component's alternate licenses
|
||||
I have the right to release the code I commit under the terms I am
|
||||
committing it
|
||||
|
||||
zab (topiltzin on irc)
|
||||
|
||||
[pubkey zab@mail.i2p]
|
||||
MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC0H8bP/f8v7KjnyGlZGWQsF5G3ppvJ1Kwt/dUGi7gHbclKPnFAWXmb7YWOhl9Ua2USjQ4YrIeB7/2uVOpe+3FrFgUzIiWsx6I2yiNI3TscDvQsa5wG0Z2G4BbHXjONyiUzzO+j2TWPs3x35r2LCy8plRzPAswCF1GaIEjJCce5zwIDAQAB
|
||||
[end]
|
||||
[pubkey zab-transport@mail.i2p]
|
||||
MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDLI/VD0KtrPPaCSQPHse4p53ze5yi/0CePfbh1YXTJieUzCGpD76IjlpRB8sRYIevWGglOjac6fhAA97VMlSmZHIxtBw3U4Y7kTkdZcsgkKTa756ge5UeURVmBaUZevb8DDRREUQ3ELt6bit9iQhOvsAeUNiB1IVmRRBXrYIQhSQIDAQAB
|
||||
[end]
|
||||
-----BEGIN PGP SIGNATURE-----
|
||||
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
|
||||
Comment: GPGTools - http://gpgtools.org
|
||||
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
|
||||
|
||||
iQIcBAEBAgAGBQJQmQeOAAoJEJkeLHPsdqhZgOUQAIRzuQZ3yF1r+P0iO390r+qy
|
||||
RxU0gQiPJDqDixDn0u8EAb2ljRWHTBfy792hs0nUu2//fNCh6chd7tbmJQn02Rm9
|
||||
nDICr2Lex6a9j498yWnkh0ZHq9yd1CPGT8xo3DW/KzLmqj+8xNUmx9RI3Y32wL9h
|
||||
H/O0VsGN0FhYeLU0vBlNkb+Vs9e0wY3/qCVMo1ldjVPahz6bblYXKVxfRhCThdfS
|
||||
ufUH2wqaDUozKabCeuM0xlll3PuaL2cATjUJuVWvO4Lahf6EZZBUvEgiW95wAL3q
|
||||
dFxZw9hUmFC4p30p0N+fQND/7aGfwujQO++S3D8gizqzSovaFpXxNzoQ6hSUWjI0
|
||||
+KsvbJXu0IguUen2p/Ka8EB0yWokYjIUH4V2kLt9jVJLuoSkejnTrFQuPIR1Qmcr
|
||||
31wqWJMWWbbFBR7KrPaDnBnRej5aIyZnHIyTtgUKhO+paDGQ0IYDirgXP10MtouY
|
||||
4Hl5v2OwhOwv/mPOm74EwJknFPhQThgxO8zG9sTHq5Lteb5SwaPLdZi7CruVU66p
|
||||
uCol/dZqVwrb2iVD19S4MvNQiOVQEWFKeBrxxBkT+qcGIWLMsG/o1qu0+VHpWQmo
|
||||
G4Adgew+7tIkak/71ss1pvUi05WsPP9KyzXrwqcFyoAmMFPtgxUIVYVc1kwYb5h3
|
||||
G58Br6HXTQLV8xAN1ml8
|
||||
=4989
|
||||
-----END PGP SIGNATURE-----
|
||||
|
||||
</pre>
|
||||
{% endblock %}
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
{% block title %}I2PControl API{% endblock %}
|
||||
{% block content %}
|
||||
<h1>I2PControl - Remote Control Service</h1>
|
||||
<p>I2P enables a <a href="http://en.wikipedia.org/wiki/JSON-RPC">JSONRPC2</a> interface via the plugin I2PControl.
|
||||
<p>I2P enables a <a href="http://en.wikipedia.org/wiki/JSON-RPC">JSONRPC2</a> interface via the plugin <a href="http://itoopie.net/">I2PControl</a>.
|
||||
The aim of the interface is to provide simple way to interface with a running I2P node. A client, itoopie, has been developed in parallel.
|
||||
The JSONRPC2 implementation for the client as well as the plugin is provided by the java libraries <a href="http://software.dzhuvinov.com/json-rpc-2.0.html">JSON-RPC 2.0</a>.
|
||||
A list of implementations of JSON-RPC for various languages can be found at <a href="http://json-rpc.org/wiki/implementations">the JSON-RPC wiki</a>.
|
||||
|
||||
@ -265,7 +265,7 @@ A chart of current tracker software capabilities is <a href="http://zzz.i2p/file
|
||||
</li>
|
||||
<li>
|
||||
The
|
||||
<a href="http://forum.i2p2.de/viewtopic.php?t=2068">I2P bittorrent FAQ</a>
|
||||
<a href="http://forum.i2p/viewtopic.php?t=2068">I2P bittorrent FAQ</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="http://zzz.i2p/topics/812">DHT on I2P discussion</a>
|
||||
|
||||
@ -205,7 +205,7 @@ Note: always verify that javadocs are current by checking the release number.
|
||||
</li><li>
|
||||
<a href="manualwrapper.html">Updating the wrapper manually</a>
|
||||
</li><li>
|
||||
<a href="http://forum.i2p2.de/">User forum</a>
|
||||
<a href="http://forum.i2p">User forum (I2P internal)</a>
|
||||
</li><li>
|
||||
<a href="http://zzz.i2p/">Developer forum inside I2P</a>
|
||||
</li><li>
|
||||
|
||||
@ -80,7 +80,7 @@ etc), and the like.</p>
|
||||
<table border="1">
|
||||
<tr><td><p><b>Name</b></p></td><td><p><b>Status</b></p></td><td><p><b>Judge</b></p></td><td><p><b>Dev <sup>*</sup></b></p></td><td><p><b>Bounty</b></p></td></tr>
|
||||
<tr>
|
||||
<td><p><b><a href="http://forum.i2p2.de/viewtopic.php?t=1136">Bundling bounties</a></b></p></td>
|
||||
<td><p><b><a href="http://forum.i2p/viewtopic.php?t=1136">Bundling bounties</a></b></p></td>
|
||||
<td><p>Proposed</p></td>
|
||||
<td><p>jrandom</p></td>
|
||||
<td><p>[vacant]</p></td>
|
||||
@ -104,7 +104,7 @@ etc), and the like.</p>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><p><b><a href="{{ site_url('volunteer/bounties/datastore') }}">Datastore over I2P</a></b></p></td>
|
||||
<td><p><a href="http://duck.i2p/tahoe-lafs/">CLAIMED</a> for 700 €</p></td>
|
||||
<td><p><a href="http://killyourtv.i2p/tahoe-lafs/install/">CLAIMED</a> for 700 €</p></td>
|
||||
<td><p>duck, smeghead</p></td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -114,12 +114,12 @@ etc), and the like.</p>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><p><b>Swarming file transfer</b></p></td>
|
||||
<td><p><a href="http://duck.i2p/i2p-bt/">CLAIMED</a> for €250 EUR</p></td>
|
||||
<td><p><a href="http://i2p-bt.postman.i2p">CLAIMED</a> for €250 EUR</p></td>
|
||||
<td><p>duck, ragnarok, dinoman, connelly, drwoo</p></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><p><b>Streaming library window size</b></p></td>
|
||||
<td><p><a href="http://dev.i2p.net/pipermail/i2p/2004-November/000491.html">Claimed</a></p></td>
|
||||
<td><p><a href="http://web.archive.org/web/20070404110818/http://dev.i2p.net/pipermail/i2p/2004-November/000491.html">Claimed (archived link)</a></p></td>
|
||||
<td><p>jrandom</p></td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -134,7 +134,7 @@ etc), and the like.</p>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><p><b><a href="http://gcc.gnu.org/java/">GCJ</a> support</b></p></td>
|
||||
<td><p><a href="http://dev.i2p.net/cgi-bin/cvsweb.cgi/i2p/Makefile.gcj">Claimed</a></p></td>
|
||||
<td><p><a href="https://trac.i2p2.de/browser/Makefile.gcj">Claimed</a></p></td>
|
||||
<td><p>jrandom</p></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
@ -216,6 +216,12 @@ CFhd0htyCw/l2/syEPeObx78Yf2pCnAIYAsapCa0kNQzlb4FB637Ql
|
||||
AmEGcRv0PjbW6USV41EWMad0RFWmq8SBkuZxbwpn33bUNkXQIDAQAB
|
||||
[end]
|
||||
|
||||
[pubkey zab@mail.i2p]
|
||||
MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC0H8bP/f8v7KjnyG
|
||||
lZGWQsF5G3ppvJ1Kwt/dUGi7gHbclKPnFAWXmb7YWOhl9Ua2USjQ4Y
|
||||
rIeB7/2uVOpe+3FrFgUzIiWsx6I2yiNI3TscDvQsa5wG0Z2G4BbHXj
|
||||
ONyiUzzO+j2TWPs3x35r2LCy8plRzPAswCF1GaIEjJCce5zwIDAQAB
|
||||
[end]
|
||||
</pre>
|
||||
<h3 id="transport">Developer Transport Keys</h3>
|
||||
<p><b>Note:</b> Transport keys are only needed for setting up a <a href="monotone#operating-a-monotone-server">Monotone server</a>.</p>
|
||||
@ -346,6 +352,20 @@ MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC1Qz/jUeOfzT+ZNm
|
||||
u0TN/SZhJUx/AvP/WBKL4rvLkdmVS8MDGjpmk+ErD5d9U/27+xw6wP
|
||||
MIDi4WGmTyjLS5nYHcrQa7SjW3xGQuyfWJXa2RuRMMtmum3wIDAQAB
|
||||
[end]
|
||||
|
||||
[pubkey zab-transport@mail.i2p]
|
||||
MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDLI/VD0KtrPPaCSQ
|
||||
PHse4p53ze5yi/0CePfbh1YXTJieUzCGpD76IjlpRB8sRYIevWGglO
|
||||
jac6fhAA97VMlSmZHIxtBw3U4Y7kTkdZcsgkKTa756ge5UeURVmBaU
|
||||
Zevb8DDRREUQ3ELt6bit9iQhOvsAeUNiB1IVmRRBXrYIQhSQIDAQAB
|
||||
[end]
|
||||
|
||||
[pubkey anarkon-transport@mail.i2p]
|
||||
MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDBZVg1jgWAWLn/6y
|
||||
C9zd4OqFuSNiWDH9hVA0kWNJvdhylp7bCP6Pd2mgNesyV1K9girW1M
|
||||
2r300Csm5v7kff8/ct3ef5HyoBMn2Ex8SgAmir2Pjgc6lFsn3I8hOv
|
||||
FAkUwH1CFtg6sjKUJMJQJbisfPmnhu20Ptf6VXaQtaG/JgCQIDAQAB
|
||||
[end]
|
||||
</pre>
|
||||
|
||||
{% endblock %}
|
||||
|
||||
@ -836,8 +836,14 @@ That message will contain the same nonce sent here.
|
||||
Later on,
|
||||
based on the delivery guarantees of the session configuration, the router may
|
||||
additionally send back another MessageStatusMessage updating the status.
|
||||
Note: As of release 0.8.1, the router does not send either Message Status Message if
|
||||
</p><p>
|
||||
As of release 0.8.1, the router does not send either Message Status Message if
|
||||
i2cp.messageReliability=none.
|
||||
</p><p>
|
||||
Prior to release 0.9.4, a nonce value of 0 was not allowed.
|
||||
As of release 0.9.4, a nonce value of 0 is allowed, and tells to the router
|
||||
that it should not send either Message Status Message, i.e. it acts as if
|
||||
i2cp.messageReliability=none for this message only.
|
||||
</p>
|
||||
|
||||
|
||||
@ -868,6 +874,21 @@ truncated from 8 bytes to 6 bytes
|
||||
<p>
|
||||
As of release 0.7.1.
|
||||
</p><p>
|
||||
As soon as the SendMessageExpiresMessage arrives fully intact, the router should return
|
||||
a MessageStatusMessage stating that it has been accepted for delivery.
|
||||
That message will contain the same nonce sent here.
|
||||
Later on,
|
||||
based on the delivery guarantees of the session configuration, the router may
|
||||
additionally send back another MessageStatusMessage updating the status.
|
||||
</p><p>
|
||||
As of release 0.8.1, the router does not send either Message Status Message if
|
||||
i2cp.messageReliability=none.
|
||||
</p><p>
|
||||
Prior to release 0.9.4, a nonce value of 0 was not allowed.
|
||||
As of release 0.9.4, a nonce value of 0 is allowed, and tells the router
|
||||
that it should not send either Message Status Message, i.e. it acts as if
|
||||
i2cp.messageReliability=none for this message only.
|
||||
</p><p>
|
||||
As of release 0.8.4, the upper two bytes of the Date are redefined to contain
|
||||
flags. The flags must default to all zeros for backward compatibility.
|
||||
The Date will not encroach on the flags field until the year 10889.
|
||||
|
||||
592
www.i2p2/pages/meeting209.html
Normal file
592
www.i2p2/pages/meeting209.html
Normal file
@ -0,0 +1,592 @@
|
||||
{% extends "_layout.html" %}
|
||||
{% block title %}I2P Development Meeting 209{% endblock %}
|
||||
{% block content %}<h3>I2P dev meeting, November 20, 2012</h3>
|
||||
<div>
|
||||
<h4>Quick recap</h4>
|
||||
<ul>
|
||||
<li><b>Present:</b>
|
||||
asdfsdafsdafsd,
|
||||
darrob,
|
||||
dg,
|
||||
k0e,
|
||||
KillYourTV,
|
||||
LaughingBuddah,
|
||||
nom,
|
||||
psi,
|
||||
st4d,
|
||||
thursday,
|
||||
user,
|
||||
weltende,
|
||||
zzz
|
||||
</li>
|
||||
<li>
|
||||
<b>Network Health - IRC</b>
|
||||
<ul><li>Russian User Support: Russians are the top country using I2P at
|
||||
this time, followed by USA and Germany. We know of one
|
||||
dedicated Russian user that is providing help in our IRC channel #ru
|
||||
(also see next point). If we add to this area, that would be
|
||||
great. Since most of the network is russian it makes sense to
|
||||
make sure they get quality help so they are running their
|
||||
router optimally.</li>
|
||||
<li>
|
||||
Complementing the above issue would be to have our irc
|
||||
operators <a href="http://www.unrealircd.com/files/docs/unreal32docs.html#denychannelblock">redirect</a>
|
||||
either #ru -> #i2p-ru or vice versa, there seems to be
|
||||
conflicting advice given to russian users asking for directions
|
||||
in this area.
|
||||
<code>
|
||||
<br />
|
||||
KillYourTV user 'slow' fits there<br />
|
||||
KillYourTV (and he's nearly always in #ru) <br/>
|
||||
dg btw, #ru has users, #i2p-ru does not<br />
|
||||
</code>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<li>
|
||||
<b>Next Meeting</b>
|
||||
<p>
|
||||
The next meeting is scheduled for Tuesday, November 27 @ 19:30 UTC (7:30PM)
|
||||
</p>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="irclog">
|
||||
<h4>Full IRC Log</h4>
|
||||
<pre>
|
||||
{% filter escape %}
|
||||
20:03:41 <Laughing1uddah> Meeting time?
|
||||
20:03:48 <dg> It is!
|
||||
20:04:01 <k0e> checkout http://www.youtube.com/watch?v=hgJ7yck1qwY
|
||||
20:04:01 <iRelay> Title: Android ICS on Raspberry Pi, Views: 139170, Rating: 99.0%
|
||||
20:04:05 * dg gulps
|
||||
20:04:15 <dg> okay then.. let's begin
|
||||
20:04:22 <dg> our topics today are:
|
||||
20:04:33 <dg> 0) Welcome
|
||||
20:04:40 <dg> (0a) Changing things up
|
||||
20:04:47 <dg> (Meetings, etc)
|
||||
20:05:00 <dg> (1) Network health
|
||||
20:05:03 <dg> (1a) IRC
|
||||
20:05:10 <dg> (1b) Growth (how do we get i2p out there?)
|
||||
20:05:13 <dg> (2) IRL events (CCC, Cryptoparties..)
|
||||
20:05:20 <dg> (3) - Merging Fux improvements into trunk
|
||||
20:05:23 <dg> (4) Website
|
||||
20:05:26 <dg> (4a) - Mirroring..
|
||||
20:05:33 <dg> (4b)- SSL
|
||||
20:05:36 <dg> (5) - Progress
|
||||
20:05:39 <dg> (6) - Next meeting
|
||||
20:05:50 <dg> (7) - Any other notes from participants, etc
|
||||
20:05:50 <dg> bit of a mouthful!
|
||||
20:06:28 <dg> I'm hoping we have enough people here today
|
||||
20:06:43 <dg> I'm trying to base things off of past meetings
|
||||
20:07:11 <dg> so uh..
|
||||
20:07:26 <dg> First of all, do we have anyone from long enough ago to recap the changes (big ones, notable ons)
|
||||
20:07:26 <dg> since the last meeting?
|
||||
20:07:33 <dg> (It was Sept 8)
|
||||
20:09:05 <nom> unlikely atm... could try a highlight all tho
|
||||
20:09:24 <asdfsdafsdafsd> Hear ye, Hear ye!
|
||||
20:09:27 * asdfsdafsdafsd pounds gavel
|
||||
20:09:35 <dg> I'm thinking maybe KillYourTV knows a little
|
||||
20:09:53 <dg> I was told welt could be here too, so hopefully he can wave at some time
|
||||
20:09:56 <dg> (no sign of zzz either)
|
||||
20:10:09 <dg> This will be somewhat awkward without most of the team
|
||||
20:10:23 <asdfsdafsdafsd> The honorable asdfsdafsdafsd is now presiding
|
||||
20:10:25 <iRelay> * weltende@freenode waves
|
||||
20:10:37 <dg> :)
|
||||
20:10:37 <dg> Okay
|
||||
20:10:48 <zzz> here
|
||||
20:10:51 <dg> So, first of all, as some of you may know, this is the first meeting in 2 years
|
||||
20:11:04 <dg> And even the last meeting was specalized
|
||||
20:11:08 <dg> specialized*
|
||||
20:11:30 <dg> I'm planning on booting up regular meetings to catch up on progress, etc, even if there is no big topic to discuss
|
||||
20:12:01 <dg> wrt "change", I'm contemplating taking up Project Manager
|
||||
20:12:04 <dg> or at least some sort of co-ordinator
|
||||
20:12:28 <dg> I'm proud of the progress that was made with dr|z3d although sadly, I don't think he's ready to join in -dev again just yet (speak, even)
|
||||
20:12:54 <dg> I can't comment on progress from the last 2 years since I haven't been here for that long
|
||||
20:12:57 <dg> If somebody else could, I'd appreciate it
|
||||
20:13:04 <dg> <pause for $person>
|
||||
20:13:18 <nom> might have to wait for netsplit to unsplit
|
||||
20:13:25 <dg> might be a good idea :-/
|
||||
20:13:36 <nom> hehe
|
||||
20:13:51 <LaughingBuddah> While we wait, what happened dr|z3d?
|
||||
20:13:54 <LaughingBuddah> what happened with*
|
||||
20:13:57 * nom pokes the intertubes
|
||||
20:14:13 <dg> There we go.
|
||||
20:14:20 <dg> Let me paste what they missed.
|
||||
20:15:42 <dg> this is painful haha
|
||||
20:16:09 <dg> ok, netsplit folk: http://pastethis.i2p/show/2297/
|
||||
20:16:12 <iRelay> Title: Paste #2297 | LodgeIt! (at pastethis.i2p)
|
||||
20:16:12 <dg> <+dg> I can't comment on progress from the last 2 years since I haven't been here for that long
|
||||
20:16:15 <dg> <+dg> If somebody else could, I'd appreciate it
|
||||
20:16:15 <dg> <+dg> <pause for $person>
|
||||
20:16:27 <dg> LaughingBuddah: alright
|
||||
20:16:53 <dg> Basically, after dr|z3d was kicked out for a long period, etc etc, I raised the point that he should be unmuted in -dev as we're all on the same team here, etc
|
||||
20:17:00 <dg> He doesn't seem to be up to joining us again yet though
|
||||
20:17:06 <nom> Complication: KillYourTV badger darrob dg gatekeeper iRelay Meeh postman RN_ Shinobiwan slow sponge str4d albat asdfsdafsdafsd Astral2012_1 Biotrophy blitzkrieg christoph cipher__ dr4wd3- eight_ joepie95 k0e kytv|away LaughingBuddah lezz luminosus MTN nom operhiem1 PrivacyHawk psi SanguineRose soundwave thursday tycho usr w8rabbit woox2k Xtothec zzz meeting time people
|
||||
20:17:14 <LaughingBuddah> Nono, I was wondering why he was kicked out
|
||||
20:17:21 <dg> I wanted him to have the choice to in any case, even if he didn't *want to right now*
|
||||
20:17:21 <dg> Oh
|
||||
20:17:28 <dg> There were disagreements with the team a while back
|
||||
20:17:35 <SanguineRose> I'm not here, I am invisible
|
||||
20:17:38 <LaughingBuddah> I see
|
||||
20:17:38 <dg> It turned into quite a big disagreement after small ones added up
|
||||
20:17:53 <dg> It's lead to a pissing contest and a division of the community to an extent :-P
|
||||
20:17:56 <dg> not nice
|
||||
20:18:03 <LaughingBuddah> Alright. Proceed :)
|
||||
20:18:06 <nom> ha! you may be invisible but we can hear you :P
|
||||
20:18:17 <dg> I'll give the $person a few more seconds to appear..
|
||||
20:18:20 <SanguineRose> lies, you can not read what I am thinking right now!
|
||||
20:18:27 * dg sits awkwardly
|
||||
20:18:44 <iRelay> <weltende@freenode> dg: yeah.. in dr|z3d and !dr|z3d mostly *cough*
|
||||
20:18:48 <dg> Clearly nobody is wishing to recite history.. heh
|
||||
20:18:51 * nom lounges awkwardly while reading SanguineRose's mind
|
||||
20:18:57 <dg> Okay
|
||||
20:19:16 <nom> meh, figure out history later when the historian decides to show up
|
||||
20:19:23 <dg> so
|
||||
20:19:23 <dg> (1) - network health
|
||||
20:19:45 <dg> From what I've seen on the stats, we're doing okay on that front, although since the Russians left (rusleaks disappeared in general), there's been a drop
|
||||
20:19:52 <dg> Returning to pre-rus levels (hah)
|
||||
20:20:05 <dg> Hopefully zzz is available to comment on how we're doing on this front..
|
||||
20:20:29 <nom> imo network health is opaque, but based just on netsplits it could be better...
|
||||
20:21:06 <zzz> it's shaky but kytv and I last night found the bug introduced in 0.9.2 causing all the trouble
|
||||
20:21:21 <dg> zab and I have doubts about something so simple causing the issues though
|
||||
20:21:27 * nom :| at timing
|
||||
20:21:30 <asdfsdafsdafsd> ugh... split
|
||||
20:21:36 <dg> >.>
|
||||
20:21:48 <nom> zzz: what was the bug?
|
||||
20:21:54 <dg> i guess that's the network speaking to us
|
||||
20:22:13 <zzz> we accidentally cut the capacity of the network in half.
|
||||
20:22:53 <LaughingBuddah> haha
|
||||
20:23:04 * dg didn't see much of a difference on the tunnel success rates but you seem a lot more confident about it fixing things
|
||||
20:23:07 <nom> lol rather unfortunate bug
|
||||
20:23:14 <dg> ^
|
||||
20:23:21 <dg> I suppose we're doing alright on that front
|
||||
20:23:44 <zzz> it's a network thing. You can't fix the network by just upgrading yourself.
|
||||
20:23:50 <KillYourTV> of course one person upgrading to -10 will fix ALL the problems ;)
|
||||
20:23:59 <dg> I can't comment for (1a) (IRC) because I've obviously been unable to contact badger
|
||||
20:23:59 <KillYourTV> bah, I was too slow
|
||||
20:23:59 <dg> KillYourTV: of course, haven't you heard of Java music?
|
||||
20:24:02 <dg> *magic
|
||||
20:24:02 <dg> pfft
|
||||
20:24:13 <dg> (and i've been unable to contact postman, I was too late to get ech too..)
|
||||
20:24:17 <dg> so that was a mess up on my part
|
||||
20:24:51 <dg> (1b) then.
|
||||
20:24:55 <dg> "
|
||||
20:24:58 <dg> (1b) - Growth (how to make i2p grow more, developments with Russia (how do we get ourselves out there? outreach to big rus-sites?)) "
|
||||
20:25:01 <nom> - if (style.equals("udp"))
|
||||
20:25:01 <nom> + if (style.equals("SSU"))
|
||||
20:25:01 <dg> Pretty broard
|
||||
20:25:04 *** eight_ is now known as eight
|
||||
20:25:07 <nom> ? that the bug?
|
||||
20:25:24 <dg> (and there's a variable changed)
|
||||
20:25:36 <zzz> thatsit
|
||||
20:25:58 <dg> What was the commit excuse for that, anyway?
|
||||
20:25:58 <dg> (in 0.9.2)
|
||||
20:26:59 <k0e> regarding russian users, I think a big question is how is the #i2p-ru channel here doing? Are the russian users getting good support as compared to when english speakers come here and receive help
|
||||
20:28:13 <LaughingBuddah> Do we have someone familiar with i2p that speaks russian?
|
||||
20:28:24 <LaughingBuddah> Maybe even a dev?
|
||||
20:29:02 * nom wanted to learn russian at one point, but never found the time...
|
||||
20:29:21 <KillYourTV> user 'slow' fits there
|
||||
20:29:32 <k0e> and on a sidenote, german looks to be the 3rd largest country after russia and USA
|
||||
20:29:35 <str4d> slow hangs out there, right?
|
||||
20:29:35 * nom thinks we need to go hunting for a russian and english speaking user who is dev inclined
|
||||
20:29:38 <KillYourTV> (and he's nearly always in #ru)
|
||||
20:29:53 <nom> nvm guess we found one
|
||||
20:30:22 <LaughingBuddah> GOod
|
||||
20:31:48 <nom> wrt growth generally, i would say working out all the network stability / performance bugs is a good step
|
||||
20:32:09 <nom> also more content = more users = more content, sharing is caring and all that
|
||||
20:32:28 <LaughingBuddah> What he said ^
|
||||
20:33:02 <dg> #i2p-ru is dead
|
||||
20:33:02 <dg> zab is able to convert RU->EN but not EN->RU
|
||||
20:33:16 <dg> btw, #ru has users, #i2p-ru does not
|
||||
20:33:31 <dg> while working out bugs is great
|
||||
20:33:42 <dg> We've certainly got a community based issue and I have not the slightest clue how to solve it
|
||||
20:33:49 <nom> so yah.. everyone upload their media stashes to postman, and run high cap routers
|
||||
20:34:13 <dg> i wish it was that simple
|
||||
20:34:27 <dg> I guess this kind of includs IRL meetings
|
||||
20:34:34 <dg> We've got a bunch of i2p-folk going to CCC this year
|
||||
20:34:52 <dg> I think an "i2p workshop" is the best way to utilize this since it is too late to book a talk
|
||||
20:35:02 <nom> lol yah increasing content is never simple, but good to remind people
|
||||
20:35:18 <k0e> dg: suggest, maybe you can talk to eche|on and postman about combining those two channels (redirect to one of them)
|
||||
20:35:18 <dg> i2p is barely out there like Tor
|
||||
20:35:53 <dg> k0e: noted, will look into it later, thanks :)
|
||||
20:36:16 <nom> re irl community meetings, at conferences and such, yah there needs to be more of it. ideally with the organizers staying connected to those of us back home in i2p, with videos and blogs, etc
|
||||
20:36:55 <dg> Not sure how we could reach out to the russians, but someone could try speaking to the censored websites
|
||||
20:36:59 <dg> prominent ones which are controversial, etc
|
||||
20:37:06 <dg> Sadly, rusleaks is absolutely gone
|
||||
20:37:09 <dg> So we can't rely on that
|
||||
20:37:34 <dg> I tried reaching out to the an*on folk but I was unable to get on their networks anonymously so that was a little redundant
|
||||
20:38:21 <LaughingBuddah> Let's move on
|
||||
20:38:36 <darrob> i don't know about the reaching out, dg. does tor do that? this going from door to door advertising doesn't seem right.
|
||||
20:38:43 <dg> Okay.
|
||||
20:39:04 <dg> darrob: They don't do the door-to-door, and us doing that officially isn't right either. I was going to just encourage them a little.
|
||||
20:39:22 <dg> LaughingBuddah: sure.
|
||||
20:39:29 <str4d> Doc improvements would help a lot.
|
||||
20:39:41 * dg was thinking about that earlier
|
||||
20:39:44 <dg> I wasn't sure on the standards of them
|
||||
20:40:51 <nom> yah doc improvements, and also some rigorous security testing could go a long way towards user growth
|
||||
20:41:25 <dg> actually, we missed out on security testing due to lack of recent docs
|
||||
20:41:35 <dg> of course, we couldn't have done anything since doc improvement took a while but yeah
|
||||
20:42:09 <dg> Right now, the only way to say i2p is safer than something heavily audited e.g Tor is to read all the code + design yourself
|
||||
20:42:15 <dg> That's fine for those who are wise in that area but bs for users
|
||||
20:42:25 <dg> i2p has had little academic research too
|
||||
20:42:35 <nom> imo at least, most users of this kinda thing want to get into the details of how it works and how secure it is. the threadmodel page is useful, but their not the results of extensive testing
|
||||
20:42:46 <dg> Of course, you can't exactly force academics to write papers on i2p..
|
||||
20:42:57 <dg> nom: I agree.
|
||||
20:43:19 <iRelay> <weltende@freenode> dg: that's not really true anymore imho
|
||||
20:43:38 <dg> hm?
|
||||
20:43:45 <nom> lol .... i suppose we could try to blackmail some grad students into writing papers on i2p \o/
|
||||
20:43:55 <dg> $5 wrench
|
||||
20:44:08 <iRelay> <weltende@freenode> ah.. just got an mail of an talk about i2p @ athens cryptoparty #0
|
||||
20:44:24 <dg> oh, nice. I was wondering about Cryptoparty
|
||||
20:44:27 <dg> Tor has been heavily featured at them
|
||||
20:44:41 <iRelay> <weltende@freenode> dg: there are a few papers about i2p.. (remember that tum i2p paper for example? ;)
|
||||
20:44:50 <asdfsdafsdafsd> I doubt many academics will write papers or advocate I2P.... they're all in league with the globalists
|
||||
20:45:44 <iRelay> <weltende@freenode> asdfsdafsdafsd: academics won't promote anything except their own software they are working on atm ;-)
|
||||
20:45:48 <dg> i2p, not so much
|
||||
20:46:28 <dg> The only papers I've seen about i2p are the french and correlation with headers/clocks
|
||||
20:46:48 <dg> moving on
|
||||
20:46:55 <asdfsdafsdafsd> weltende... exactly
|
||||
20:47:02 <dg> "(3) - Discussion regarding merging current fux with trunk "
|
||||
20:47:14 <nom> soooo.... gsoc? seems like security testing would be a good thing for that
|
||||
20:47:17 <dg> I'm not sure if anyone can give a real answer to this apart from zzz
|
||||
20:47:35 *** str4d is now known as str4d_afk
|
||||
20:47:46 <dg> for those of you not aware, fux is a branch of i2p dev'd by str4d among others with user interfaces improvements. Theme improvements, that kind of thing.
|
||||
20:47:49 <dg> nom: nobody wants to do gsoc
|
||||
20:47:56 *** str4d_afk is now known as str4d
|
||||
20:48:13 <dg> nom: zzz is on trac as a mentor but he apparently doesn't want to have a student
|
||||
20:48:24 <zzz> sorry dg, all I know is 2-3 months old. last I heard, they were forking?
|
||||
20:48:27 <dg> (not sure if correct, that's what I was told)
|
||||
20:48:43 <zzz> wrong
|
||||
20:48:58 <nom> no kidding, probably why it hasn't got done, but its a resource that gives access to the kind of people that could actually do a security assessment
|
||||
20:49:24 <dg> zzz: There was some discussion of a fork, it's kind of died down now as some people have had a change of heart. Not sure what's going to be going on there, I don't think anyone is. Regarding the current changes though, I feel they could be somewhat beneficial. Nothing massive/feature breaking in there, however.
|
||||
20:49:34 <dg> zzz: also, wrong?
|
||||
20:49:38 <str4d> I am happy to mentor for GSoC
|
||||
20:50:09 <dg> nom: Yup.
|
||||
20:50:21 <dg> str4d: We could apply for next year, the application for 2010(?) is still up on trac.
|
||||
20:50:25 <zzz> re: gsoc: wrong as in I'm happy to help but I'm not going to be in charge and not going to do it myself.
|
||||
20:50:43 <dg> totally different to what i heard
|
||||
20:50:53 <dg> key word: heard, I suppose
|
||||
20:51:05 <dg> relevant trac page: http://trac.i2p2.i2p/wiki/gsoc
|
||||
20:51:32 <zzz> dg re: fux, you're asking the wrong guy. I have no recent info.
|
||||
20:51:39 <nom> imo fork is both exactly what is happening and exactly what is not happening, zzz you 'control' the official i2p.i2p branch in that you give out commit keys, but theres always gonna be people/groups writing their own features/code into i2p, if theres no interest in merging it stays a 'fork' but otherwise its not really
|
||||
20:52:01 <dg> zzz: generally asking if you'd be ok with merging some of the themes, etc
|
||||
20:52:04 <str4d> AFAIK there is nothing stopping mentors being anon, but we need a contactable liason (not sure if they must be non-anon) and some tax form as an organization.
|
||||
20:52:23 <dg> Right.
|
||||
20:52:37 <dg> I'm fine with being a liason but I'm sure a few people would be.
|
||||
20:52:56 <dg> Tax form .. ugh
|
||||
20:53:05 <LaughingBuddah> We will need some people to agree to be the face of i2p
|
||||
20:53:24 <str4d> IIRC there was a USA-based one, or a Foreign-based one.
|
||||
20:53:31 <dg> sadly we can't avoid that, LaughingBuddah..
|
||||
20:53:59 <dg> I don't want to be the guy trying to force people to give up anonymity and get up on stages but
|
||||
20:54:18 <dg> We do need someone who wants to and can fulfill the job
|
||||
20:54:41 <zzz> dg the last I looked at it was months ago. It was a big grab bag of stuff and I had some objections. Nobody has since asked me to look again - or spilt out the bad from the good - or given me any updates - or mentioned any progress about addressing my issues.. Unless that happens I have no update for you and i assume they are either working on it or forking.
|
||||
20:54:49 <str4d> (Might not have been tax, but it was something financial)
|
||||
20:54:52 <str4d> Not sure what was done in 2010 for that.
|
||||
20:55:19 <dg> zzz: Alright, if I can get them to talk about it etc, I may be able to get you an update.
|
||||
20:55:27 <dg> just a note
|
||||
20:55:30 <dg> http://trac.i2p2.i2p/wiki/gsoc/ideas
|
||||
20:55:37 <dg> seems quite interesting
|
||||
20:55:40 <iRelay> Title: gsoc/ideas – I2P (at trac.i2p2.i2p)
|
||||
20:55:44 <zzz> so I repeat, you are asking the wrong guy. If you want to know about status, ask the guys working on it, not me.
|
||||
20:56:07 <dg> I was asking if you'd be okay with merging is all, if they co-operated.
|
||||
20:56:19 <dg> I felt that the changes could benefit i2p somewhat.
|
||||
20:56:34 <dg> welcome psi
|
||||
20:56:41 <psi> ??
|
||||
20:56:48 <dg> dev meeting
|
||||
20:56:55 <psi> ok
|
||||
20:57:36 <dg> The application for GSOC seems solid
|
||||
20:57:39 <dg> Could possibly reuse it
|
||||
20:57:39 <nom> zzz: what were the issues you needed addressed?
|
||||
20:59:54 <str4d> There was an image in a dark theme that has since been replaced. Were there any other major issues?
|
||||
21:00:17 <psi> ah yes... the assange character should've been removed for now
|
||||
21:00:20 <psi> s/for/by
|
||||
21:00:35 <dg> What's wrong with Assange? :P
|
||||
21:00:46 <zzz> the main thing in remember is regressions in legibility and color choices, esp. in snark. But it's been months since I looked at it
|
||||
21:00:49 <darrob> nom: you should try to find logs. it would be hard to recall or summarize. (for me, anyway, and i tried to give feedback, too).
|
||||
21:00:56 <zzz> I felt it was a big step backwards
|
||||
21:01:18 <KillYourTV> http://killyourtv.i2p/irclogs/%23i2p-dev.2012-08-23.log.html
|
||||
21:01:21 <iRelay> Title: #i2p-dev logs for Thursday, 2012-08-23 (at killyourtv.i2p)
|
||||
21:01:32 <dg> seems too late to enter gsoc this time now
|
||||
21:01:43 <psi> regardless... i think we need a "real life" UI testing mechanism that isn't totally subjective
|
||||
21:01:47 <dg> or uh, next year's are not open (what i mean)
|
||||
21:01:54 <dg> psi: exactly
|
||||
21:01:57 <psi> this is where users like Zorya come into play
|
||||
21:02:12 <psi> Zorya especially is the perfect feedback tool for UI stuff
|
||||
21:02:35 <nom> re assange, imo hes a cool dude, but as he 'officially' has nothing to do with i2p, we shouldn't be using his image on stuff... unless its like something related to him or wikileaks...
|
||||
21:02:38 <psi> "regular" or "casual" users are VERY important and should be utilized for feedback
|
||||
21:02:41 <zzz> but if the fux guys dont remember my objections either, then they probably haven't addressed them, and we're in the same place we were 3 months ago.
|
||||
21:02:51 <psi> nom: i2p is politically neutral
|
||||
21:03:37 <str4d> zzz, I recall your legibility issues, and I still think that is more a personal preference matter (since there are clear examples of people both liking and disliking the changes)
|
||||
21:03:49 <nom> psi: right... if such a thing is possible
|
||||
21:03:52 <psi> nom: no need to take any stance on things that are politically sensitive anywhere
|
||||
21:03:59 <str4d> and color*
|
||||
21:04:02 <str4d> The major issue was the image, and that has been addressed.
|
||||
21:04:13 <nom> pretty sure were taking a stand about anonymity and free exchange of data tho....
|
||||
21:04:35 <str4d> psi, what's Zorya?
|
||||
21:04:42 <asdfsdafsdafsd> assange is cointelpro
|
||||
21:04:53 <dg> a person, not sure who/what they do though
|
||||
21:04:53 <KillYourTV> I can say that when I last looked a few weeks ago, the constrasts in snark weren't nearly as jarring as they had been.
|
||||
21:04:53 <psi> str4d: Zorya is a user in this channel
|
||||
21:05:15 <psi> str4d: a "regular" user in jester's group
|
||||
21:05:15 <zzz> so none of my issues were addressed? (except perhaps the assange image)
|
||||
21:05:19 <zzz> then we're in the same place
|
||||
21:05:38 <dg> actually, iirc, the colors were improved
|
||||
21:05:42 <dg> i'm not sure they are perfect however
|
||||
21:05:56 <zzz> at the time, I thought that fux was unmergable, that you should kill it and start over, separating out the good from the bad and the ugly.
|
||||
21:06:08 <psi> zzz: tbh i'm not entirely sure that style issues are that critical unless they impact usability
|
||||
21:06:36 <str4d> psi, ah - I read your sentence as Zorya being an automated testing tool =P
|
||||
21:06:39 <dg> the best bit about fux, for me, was the framing of apps inside the console
|
||||
21:06:46 <dg> i don't care as much about themes
|
||||
21:07:01 <darrob> psi: that argument works for and against changes. ;)
|
||||
21:07:20 <psi> darrob: correct
|
||||
21:07:23 <nom> imo themes are themes and should be a basket of everyones options, if your problem is the default theme... then yah i guess i can see you not wanting to merge that... but still
|
||||
21:07:23 <zzz> I gave my comments 3 months ago and havent heard anything since. If somebody would like to identify changes and ask me to look at it again, fine.
|
||||
21:07:38 <dg> nom: my thoughts.
|
||||
21:07:49 <zzz> you people that are saying you like some of it and dont care about the rest are missing the point completely.
|
||||
21:07:49 <psi> darrob: however in its current state, the router console is in need of a redesign as it fails as a UI
|
||||
21:07:52 <user> an improvement from the ui guys's side would be a UI plugin, I think.
|
||||
21:08:04 <zzz> split out the good from the bad. right now it's a grab bag
|
||||
21:08:11 <user> <dg> the best bit about fux, for me, was the framing of apps inside the console <<<---- that one I liked too.. gave an impression of unity
|
||||
21:08:26 <dg> Made things a lot less clunky IMO, user.
|
||||
21:08:56 <str4d> zzz, the point here is that there is nothing bad/ugly in fux, there is just stuff that everyone likes and stuff that some like and some don't.
|
||||
21:09:07 <zzz> sounds like you guys are saying you still want to merge it but haven't done anything in 3 months?
|
||||
21:09:33 <zzz> disagree. your snark changes are objectively bad/ugly.
|
||||
21:09:56 <user> what's it that everyone likes? maybe one could start identifying that and only merge that
|
||||
21:09:59 <psi> zzz: much has been done but that doesn't mean anything is "complete", as for something being "objectively ugly" is kind of an oxymoron
|
||||
21:10:02 <nom> right well the good, the bad, and the ugly, are subjective.... imo as long its configurable personal taste of devs shouldn't come into it
|
||||
21:10:24 <dg> Yes, we have?
|
||||
21:10:27 <dg> In fact, I believe the color issue was also addressed.
|
||||
21:10:27 <dg> see nom's comment
|
||||
21:10:27 <dg> <nom> imo themes are themes and should be a basket of everyones options, if your problem is the default theme... then yah i guess i can see you not wanting to merge that... but still
|
||||
21:10:27 <dg> psi: Exactly.
|
||||
21:10:27 <dg> psi: It's great for nerds like us, not so much for a grandma who wants to be safe.
|
||||
21:10:34 <dg> zzz: I can somewhat agree for snark but the rest, no.
|
||||
21:10:45 <dg> user: the unification.
|
||||
21:10:48 <dg> user: the non-default themes, too.
|
||||
21:10:59 <dg> user: if it's non-default, I think it's fine to merge and improve along the way. Doesn't hurt.
|
||||
21:11:06 <nom> how bout this, default keeps theme the same, but includes all the things fux adds, to use them you just set something in config?
|
||||
21:11:14 <dg> ^
|
||||
21:11:29 <zzz> If the people doing the work say they think it's ready for another look, I'll take a look. I have nothing more to say.
|
||||
21:11:32 <psi> currently (afaik), fux is aimed at hackability and flexibility, not explicitly general pleaseability
|
||||
21:11:43 <dg> alright
|
||||
21:11:46 <str4d> Given the users that have said otherwise, I find that hard to take as truly objective.
|
||||
21:11:46 <dg> fair enough, zzz.
|
||||
21:11:46 <str4d> Nevertheless, I do agree that fux is not ready for merging dg
|
||||
21:12:09 <psi> str4d: fux is no where near merging
|
||||
21:12:09 <dg> str4d: all I wanted was some discussion on it to see what needed doing :)
|
||||
21:12:12 <psi> not sure who suggested a merge
|
||||
21:12:15 <maidenboi> i like the snark changes
|
||||
21:12:26 <nom> zzz: can you agree to that principle tho? that its mergeable if you're experience/view isn't changed unless you select it to happen? ie no default changes
|
||||
21:13:44 <nom> or rather, since as you said its a grab bag, that pieces are mergeable if they don't change default things and only add options
|
||||
21:14:14 <psi> at the moment fux is more of a sandbox for ideas, not really meant to be merged over to mainline in its entirety
|
||||
21:14:45 <psi> i don't expect fux to ever be fully merged over nor would it be a good idea
|
||||
21:14:56 <dg> I wanted some parts merged
|
||||
21:15:18 <psi> dg: if they are "done" then sure
|
||||
21:15:25 <psi> dg: which ones?
|
||||
21:15:29 <LaughingBuddah> How to we determine them to be done?
|
||||
21:15:48 <str4d> dg, I agree about the changes to non-default themes being mergable, especially since the majority of changes are by the original theme author, but there are other things that need work first.
|
||||
21:15:55 <user> again, plugins would be handy, as to not increase the i2p package's size unneededly.
|
||||
21:16:30 <KillYourTV> One thing for sure would be the pull the fix for ticket #773. It's fine in fux; it's not fine in the vanilla builds.
|
||||
21:16:37 <iRelay> http://trac.i2p2.i2p/ticket/773 - (new defect) - Overlapping text in midnight theme
|
||||
21:16:49 <psi> i do like the unified css and inline frames for snark and mail
|
||||
21:16:49 <psi> especially the unified css
|
||||
21:16:52 <KillYourTV> iirc LaughingBuddah reported that in this channel as well.
|
||||
21:16:59 <str4d> user, that does require getting the UI separation done though (which I hope to work on with top[tabfail] when I get some time)
|
||||
21:17:22 <dg> psi: mainly the embedding of things, like snark
|
||||
21:17:25 <dg> LaughingBuddah: majority satisfaction
|
||||
21:17:28 <psi> dg: yes i like that too
|
||||
21:17:46 <str4d> dg, #define majority =P
|
||||
21:17:49 <darrob> i'm confused. i was under the impression that fux was supposed to be merged (rather sooner than later even). i wouldn't have taken the time and given detailed criticism if i was told that it was just a sandbox.
|
||||
21:18:00 <LaughingBuddah> KillYourTV: Yeah I remember doing that
|
||||
21:18:11 <psi> darrob: my impression was that it is a sandbox
|
||||
21:18:36 <psi> as i have been treating it as such so far
|
||||
21:18:46 <str4d> darrob, I always intended it to be merged. But in some ways it is meant as a UI sandbox.
|
||||
21:18:53 <dg> str4d: i'd like the creator of the functionality to think it's ok to merge (time to), and a lot of the fux/users with it liking it
|
||||
21:19:00 <dg> darrob: so was I?
|
||||
21:19:00 <dg> Anyway,
|
||||
21:19:07 <dg> I think we can agree that fux needs work
|
||||
21:19:22 <dg> unification + #773 fix should get merged sooner rather than later
|
||||
21:19:40 <dg> Let's move on ;-)
|
||||
21:19:43 <str4d> It's Future UX, so it's for testing and trying out new UX ideas, working out the kinks and polishing.
|
||||
21:19:58 <str4d> +1 dg
|
||||
21:20:09 <psi> str4d: that would be sandbox... moving on
|
||||
21:20:37 <nom> honestly i think we need to have better communication here, theres always going to be things that are mergable, and we need people who can discuss that merging without getting into fights ;)
|
||||
21:21:03 <nom> so far so win today, which is nice
|
||||
21:21:06 <str4d> I also need to work out how to best merge parts of branches in monotone.
|
||||
21:21:43 <KillYourTV> and yeah, it looks like assange (and the dark snark theme) are completely gone
|
||||
21:21:54 <str4d> At present I only know about "propagate" and "explicit_merge", but they merge everything up to a specific commit, rather than cherry-picking changes.
|
||||
21:22:24 <nom> str4d: probably something involving editing a diff down to just the parts you want
|
||||
21:22:24 <str4d> KillYourTV, dark snark is not in mtn, but it's in my fux builds.
|
||||
21:22:51 <KillYourTV> ah..so assange (run through a filter) may still live...
|
||||
21:23:02 <dg> as for fux's issues, we can co-ordinate on that after the meeting
|
||||
21:23:05 <dg> we're doing well so far though
|
||||
21:23:05 * dg highfives
|
||||
21:23:05 <dg> (4) - Website
|
||||
21:23:09 <dg> (4a) - Mirroring i2p2.de/etc
|
||||
21:23:09 <dg> (4b) - SSL for the sites.
|
||||
21:23:09 <dg> We need welt for this..
|
||||
21:23:09 <dg> Tor's mirroring setup is great right now, rsync etc.
|
||||
21:23:09 <dg> Plus a clear list of mirrors and how to do it
|
||||
21:23:09 <dg> nom: Yeah.
|
||||
21:23:09 <dg> nom: We did well now, just that we have other issues to discuss so.. ha
|
||||
21:23:31 * dg coughs
|
||||
21:24:21 <nom> right, re website.... same as before re docs i guess, theres good info, but it feels like it hasn't been touched in a while
|
||||
21:24:36 <dg> precisely my feelings
|
||||
21:24:39 <dg> it seems very out of time
|
||||
21:24:49 <str4d> KillYourTV, no - did you not read my earlier message?
|
||||
21:25:03 <iRelay> <weltende@freenode> dg: rsync master thingy is already running
|
||||
21:25:46 <str4d> nom, that seems a bit hacky... I'd prefer a solution that still allowed for a "propagate" at a later stage once the other branch was exactly as wanted.
|
||||
21:25:46 <dg> I've noticed some issues between how things really are and what the website says
|
||||
21:26:24 <psi> in general the website seems to feel old and the "revamp" last i checked looks really good
|
||||
21:26:28 <nom> str4d: yah... could separate each mergeable thing into its own branch and merge that i suppose, and keep fux as a sandbox/catch all
|
||||
21:26:52 <dg> weltende: not documented anywhere, iirc
|
||||
21:26:59 <dg> psi: we should speed up on the revamp
|
||||
21:27:05 <dg> the current one feels extremely stale
|
||||
21:27:12 <psi> dg: priorities
|
||||
21:27:23 <nom> like use fux as a test branch, when something is ready to be included as its own component, separate the branch and merge it there, also so you can maintain it as its own thing
|
||||
21:27:32 <psi> dg: what has more importance? website or the software?
|
||||
21:27:43 <str4d> There does need to be improvement of the website content. I've been working on layout and structure in i2p.www.revamp but haven't touched the content (otherwise propagations would be a nightmare), so that needs working on in i2p.www
|
||||
21:27:46 * str4d is still not happy with the design of the revamp, but that is not the focus right now - proper content structuring so that (a) new content can be easily added, and (b) users can find what they want easily, is the main focus
|
||||
21:28:15 <thursday> Could we set up a blog on the official site? I'd gladly chip write a post a week or so - short tutorials and tips, development updates, etc.
|
||||
21:28:18 <str4d> psi, that is a chicken-and-egg question. Both are important.
|
||||
21:28:21 <dg> psi: Hell, I think the website is a big deal and it affects the software.
|
||||
21:28:24 <dg> thursday: me too.
|
||||
21:28:59 <iRelay> <weltende@freenode> thursday: already kinda done in the revamp branch.. not feature complete.. but the basic stuff is there
|
||||
21:29:42 <dg> str4d: +1
|
||||
21:29:42 <nom> ....big picture software is more important, but the website needs improvement, and imo theres enough people with enough time and skills to work on the website, without it impacting how much 'code' gets done
|
||||
21:29:42 * psi refreshes the revamp branch
|
||||
21:29:42 <str4d> thursday, at present the main site is just a collection of HTML files. The revamp reorganizes things so that there is a specific blog.
|
||||
21:29:42 <str4d> (Still a collection of HTML files, but blog generation etc. is dynamic so it makes maintaining a blog much simpler)
|
||||
21:29:42 <nom> software = community = website, as its the first introduction most people get
|
||||
21:29:49 <dg> current site makes me think nerdy
|
||||
21:30:11 <dg> and dead, old
|
||||
21:30:18 <dg> I didn't know if i2p was even in active dev when I first saw it
|
||||
21:30:37 <str4d> thursday, (and those who haven't seen it): http://vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p/en/site/ is the revamp
|
||||
21:31:01 <LaughingBuddah> psi: they could be worked on my different people. no need to decide for only one of the two
|
||||
21:31:16 <dg> I can do blog posts/write ups for pages.
|
||||
21:32:51 <KillYourTV> yes, I read your message str4d. and I call http://killyourtv.i2p/tmp/nffnatr.png "assange run through a filter"
|
||||
21:33:17 <KillYourTV> (hell, back in early september it was still 'assange.png' :P)
|
||||
21:34:13 <thursday> That looks fantastic. As someone who wants to help out with the site, is there a list of the major things that need to be done before this revamp can go live?
|
||||
21:34:24 <str4d> KillYourTV, that is not current. If you run fux you'll see that replaced with a variant of hat guy.
|
||||
21:34:47 <KillYourTV> I *just* downloaded that from you.
|
||||
21:35:18 <str4d> KillYourTV, oh, then the image file might still be sitting there. But snark does not use it.
|
||||
21:35:45 * str4d has often forgotten to remove random files, sometimes leaving .zip files in the update packages >_<
|
||||
21:36:11 <KillYourTV> alright...NOW I can agree. It's not in the css. carry on :) (and sorry)
|
||||
21:36:32 <iRelay> <weltende@freenode> hmm.. that News thingy at the end of the page is a bit to hidden imho
|
||||
21:36:52 <dg> thursday: +1, I'd like this too. We can wrap up on this if we have that and can decide on a few people to work on that.
|
||||
21:36:55 <str4d> thursday, feedback is key. I'm still working out the structure and layout at present, so comments on that are welcome (url layout as well as navigation)
|
||||
21:36:59 <dg> <+dg> thursday: +1, I'd like this too. We can wrap up on this if we have that and can decide on a few people to work on that.
|
||||
21:38:11 <str4d> thursday, if you want to improve content, there are many pages that could do with reworking to make it easier for end users to find/understand what they need to.
|
||||
21:38:33 * str4d can go through some of that later if desired.
|
||||
21:38:51 <dg> That'd be nice
|
||||
21:39:57 <LaughingBuddah> Timed out...What's the topic?
|
||||
21:40:40 <dg> Not much was said about mirroring, I think that includes the re-design though
|
||||
21:40:40 <dg> imo, any changes to the current design are just temporary and not worth thinking too much about
|
||||
21:42:10 <LaughingBuddah> Link to logs please
|
||||
21:42:10 <LaughingBuddah> I'd like to read the part about mirroring/offer my services
|
||||
21:42:10 <str4d> welterde, you were making changes to the mirroring scripts IIRC?
|
||||
21:42:10 <dg> weltende: SSL on the sites, legit certs, SSL on the mirrors (at least some) - how possible is this?
|
||||
21:42:10 <dg> unprofessional to have expired/none/CACert (which throws up errors = scary)
|
||||
21:42:10 <dg> you could argue CA system is weak but better than nothing
|
||||
21:42:10 <dg> LaughingBuddah: website etc
|
||||
21:42:10 <dg> LaughingBuddah: very little was said wrt mirroring
|
||||
21:42:10 <LaughingBuddah> I'd like to set up a mirror
|
||||
21:42:19 <str4d> dg, yeah, there are long-standing issues in trac related to that.
|
||||
21:42:19 <dg> LaughingBuddah: I figure it was because the current site is dire and we might as well wait for the new design before we do anything big.
|
||||
21:42:19 <dg> The new site can highlight important things as well as a surge of new information.
|
||||
21:42:22 <LaughingBuddah> Fair enough
|
||||
21:42:22 <dg> Anything for the old site, again, IMO is just trying to keep something dead afloat.
|
||||
21:42:34 <dg> Thank you though! :-)
|
||||
21:42:34 <LaughingBuddah> Offer still stands
|
||||
21:42:43 <dg> Oh, by the way, syndie.i2p2.i2p doesn't exist, but syndie.i2p2.de does
|
||||
21:42:46 <dg> inconsistency..
|
||||
21:42:55 <iRelay> <weltende@freenode> str4d: uh..
|
||||
21:43:07 <dg> (Regarding Syndie, it'd be cool if someone could try poke it back alive, but we probably do not have the men)
|
||||
21:43:16 <iRelay> <weltende@freenode> str4d: you mean for the revamp thing or what do you mean?
|
||||
21:43:20 <nom> yah, wrt syndie that really should be removed from the frontpage... unless someone has taking it back up without me noticing, its been dead for years
|
||||
21:43:31 <dg> Syndie is a really cool idea.
|
||||
21:43:49 <str4d> welterde, IIRC you said you were reworking the mirroring scripts, and that they would be shifted out of i2p.www eventually
|
||||
21:43:55 <iRelay> <weltende@freenode> str4d: I was gonna integrate that into the main site, so the mirror sites don't depend on my site anymore
|
||||
21:44:14 <str4d> dg, one thing I hope to fix on the new site is that urls we know exist in i2p and in clearnet get auto-changed based on the user's location (rather than an i2p user having links to trac.i2p2.de for example).
|
||||
21:44:32 <str4d> welterde, ah, okay.
|
||||
21:45:03 <dg> str4d: oh, yes. I was thinking about that a while ago. That'd be a small but very good change for UX.
|
||||
21:45:03 <dg> good call
|
||||
21:45:03 <LaughingBuddah> We've got all these projects that need manpower. Maybe we start assigning people to make sure they move forward?
|
||||
21:45:42 <str4d> dg, small from UX standpoint. %^&*ing annoying from backend standpoint >_<
|
||||
21:45:53 * str4d has tried and so far failed
|
||||
21:46:03 <dg> ^ this
|
||||
21:47:13 <hottuna> are the projects organized / listed anywhere?
|
||||
21:47:32 <psi> hottuna: iirc projects.i2p is one place
|
||||
21:47:35 <psi> not sure
|
||||
21:47:39 <dg> Perhaps we should create tickets in trac and assign them?
|
||||
21:47:42 <dg> This would mean a clear, documented timeline of progress on work and to follow up who is working on it..
|
||||
21:47:45 <dg> str4d: sounds quite easy? :s. just s/$domain/$currentdomain/..
|
||||
21:47:45 <dg> str4d: Also, could do in JavaScript although not ideal.
|
||||
21:47:45 <dg> hottuna: we're discussing them / and there's a topic on zzz.i2p to an extent about it but we're kind of trying to fix that
|
||||
21:47:48 <dg> I propose we have trac tickets for each of the issues we've raised here, but if we can't use trac (we should though, imo since it's official)
|
||||
21:47:55 <dg> we can use projects.i2p
|
||||
21:48:10 <dg> trac also allows parent tickets and such, so we could have a complete way of planning this
|
||||
21:48:13 <LaughingBuddah> What's the status on trac ---> redmine?
|
||||
21:48:21 <psi> LaughingBuddah: probably not needed atm
|
||||
21:48:32 <dg> LaughingBuddah: awaiting weltende.. but not needed right now
|
||||
21:48:35 <LaughingBuddah> I see
|
||||
21:48:41 <iRelay> <weltende@freenode> haven't had time yet to give it a try yet
|
||||
21:48:41 <dg> the issues with trac are more so on welt's end, not trac
|
||||
21:48:44 <dg> software.
|
||||
21:49:00 <dg> psi: Can you get to creating tickets for some of the issues we've raised today?
|
||||
21:50:40 <iRelay> <weltende@freenode> dg: actually it's just the monotone plugin as I said before.. other downtimes weren't *that* often to be really annoying imho..
|
||||
21:50:46 <nom> also re trac / redmine, if anyone has any experience with fossil, i would love to hear about it, im mulling over the possibility of trying to use it to make a system for actually distributed repos/bug tracking
|
||||
21:50:48 <psi> dg: which and where?
|
||||
21:50:57 <dg> psi: Trac, website reorganization, managing the necessary fux changes, dealing with the mirroring stuff, etc. Just general parent ones which we can assign to people so they do not forget and it's clear who we can grill if something breaks/doesn't work.
|
||||
21:50:57 <darrob> hasn't this "assigning jobs to people will ensure that they'll get done real quick" meme been discussed on zzz.i2p already?
|
||||
21:51:04 <dg> darrob: maybe, but was it even done?
|
||||
21:51:11 <dg> (or work?)
|
||||
21:51:30 <dg> We've clearly got some people who can get some tasks done
|
||||
21:51:33 <psi> dg: i dont get things done "fast"
|
||||
21:51:33 <dg> trac is a way of documenting proress
|
||||
21:51:33 <psi> dg: for me they are eventual
|
||||
21:51:33 <dg> psi: neither do i, but i do get them done
|
||||
21:52:47 <iRelay> <weltende@freenode> nom: people used to run a fossil thingy.. but afair you got into trouble if two people edited the wiki at once(in two different instances that is..)
|
||||
21:53:44 <nom> speaking of eventual, psi: i/others could get a lot out of you writing up your thoughts on netdb structure / your baromatrix experiences so far.. like a running blog or something
|
||||
21:53:59 <dg> nom: i certainly would
|
||||
21:54:14 <dg> psi: if not you, I can/someone else. I'd just like something to come out of this meeting so we can follow up on it next time. :)
|
||||
21:54:14 <nom> weltende: hmm interesting... so there would have to be some sort of system for consistency
|
||||
21:54:55 <iRelay> <weltende@freenode> nom: or simply support for merging as it does for files
|
||||
21:56:08 <psi> nom: current "status" of baromatrix is "being worked on"
|
||||
21:56:08 <psi> nom: i have more than just i2p right now going on
|
||||
21:56:15 <nom> psi: right, i understand, don't mean to pressure you or your time, just saying its always good to share your thoughts
|
||||
21:56:46 <psi> i'll share thoughts when they happen nom
|
||||
21:56:49 <iRelay> <weltende@freenode> baromatrix?
|
||||
21:56:57 <nom> weltende: indeed, guess i'l have to experiment with it a bit
|
||||
21:57:00 <dg> statistics project
|
||||
21:57:10 <psi> baromatrix is a distributed version of stats.i2p
|
||||
21:57:15 <iRelay> <weltende@freenode> ah
|
||||
21:57:15 <psi> to "double check" the numbers
|
||||
21:57:30 <psi> it's something that i've been meaning to do for a while
|
||||
21:57:59 <psi> also to get a general demographic of the userbase too without being invasive
|
||||
21:58:58 <nom> also uh... wheres the code? the git.repo seems to be .... nothing?
|
||||
22:03:28 <dg> I guess we should wrap up then
|
||||
22:03:35 <dg> Thanks for being involved, everyone. hopefully this can become a regular thing.
|
||||
22:03:46 <dg> Anyone got any more to say/issues to raise?
|
||||
22:04:07 <LaughingBuddah> Maybe we should schedule the next one?
|
||||
22:04:26 <dg> Next Tuesday at 9PM UTC?
|
||||
22:04:29 <dg> 8PM seemed a little rough for some people.
|
||||
22:04:45 <hottuna> bampf?
|
||||
22:04:56 * dg bampfs the meeting closed ;-)
|
||||
22:05:30 <hottuna> thanks dg, this seems like a good thing
|
||||
22:06:00 <iRelay> <weltende@freenode> dg: for me 7PM would be better..
|
||||
22:06:10 <dg> hottuna: Thank you, I've had a lot of support, it was a little rough at the start of this and I felt anxious about how it'd go, but it went well. Perhaps we could see more of you/others next time too!
|
||||
22:06:17 <dg> weltende: 7PM UTC is ok for me, I think.
|
||||
22:06:28 <dg> weltende: 8PM caused issues for str4d
|
||||
22:06:43 <dg> Next Tuesday @ 7:30PM?
|
||||
22:09:40 <iRelay> <weltende@freenode> sounds good
|
||||
22:10:28 <LaughingBuddah> +1
|
||||
22:10:39 <dg> Great.
|
||||
22:14:59 <LaughingBuddah> Cya all
|
||||
22:15:02 <LaughingBuddah> dg: good meeting
|
||||
{% endfilter %}
|
||||
{# TODO: pygments #}
|
||||
</pre>
|
||||
</div>
|
||||
{% endblock %}
|
||||
466
www.i2p2/pages/meeting210.html
Normal file
466
www.i2p2/pages/meeting210.html
Normal file
@ -0,0 +1,466 @@
|
||||
{% extends "_layout.html" %}
|
||||
{% block title %}I2P Development Meeting 210{% endblock %}
|
||||
{% block content %}<h3>I2P dev meeting, November 27, 2012</h3>
|
||||
<div>
|
||||
<h4>Quick recap</h4>
|
||||
<ul>
|
||||
<li><b>Present:</b>
|
||||
|
||||
christop1,
|
||||
darrob,
|
||||
dg,
|
||||
hottuna,
|
||||
KillYourTV,
|
||||
LaughingBuddha,
|
||||
RN,
|
||||
Schnaubelt,
|
||||
str4d,
|
||||
topiltzin,
|
||||
weltende
|
||||
</li>
|
||||
<li>
|
||||
<b>Next Meeting</b>
|
||||
<p>
|
||||
The next meeting is scheduled for Tuesday, December 4 @ 20:00 UTC (8:00PM)
|
||||
</p>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="irclog">
|
||||
<h4>Full IRC Log</h4>
|
||||
<pre>
|
||||
{% filter escape %}
|
||||
19:33:46 <dg> Alrighty.
|
||||
19:33:49 <dg> So, today's agenda is:
|
||||
19:33:52 <dg> 0) Hi
|
||||
19:33:55 <dg> 1) IRL events
|
||||
19:33:55 <dg> 2) Websiet
|
||||
19:33:58 <dg> (2a) redux
|
||||
19:34:01 <dg> (2b) SSL
|
||||
19:34:08 <dg> 3) that space where you can pitch anything else
|
||||
19:34:39 *** KillYourTV sets mode: +l 65
|
||||
19:34:45 <dg> psi, Meeh, and ech (among others) are those who are attending IRL stuff or are able to/willing
|
||||
19:34:51 * dg pokes
|
||||
19:35:02 <str4d> 0) Hi
|
||||
19:35:02 <str4d> Hi!
|
||||
19:35:18 *** KillYourTV sets mode: +lf 60 [10j#R10,20m#m5,3n#N15]:15
|
||||
19:35:28 <iRelay> <weltende@freenode> oh.. it's meeting time..
|
||||
19:35:29 *** KillYourTV sets mode: +l 65
|
||||
19:35:32 <dg> Hey
|
||||
19:35:32 <KillYourTV> sorry
|
||||
19:35:35 <KillYourTV> hi
|
||||
19:35:38 <dg> no problem welt, hi!
|
||||
19:35:49 <hottuna_> 'lo
|
||||
19:35:57 <dg> 1) IRL events then
|
||||
19:36:24 <dg> We kind of touched on this last time--, I'm wondering if we can utilize the tickets (and men) we have at CCC to get i2p out there somehow
|
||||
19:36:39 <dg> http://zzz.i2p/topics/1273 is relevant
|
||||
19:36:56 <iRelay> <weltende@freenode> I'll be @ 29c3
|
||||
19:36:59 <hottuna_> I've got stickers and am going to 29c3
|
||||
19:37:01 <iRelay> <weltende@freenode> (and bring stickers)
|
||||
19:37:18 <hottuna_> What would be nice is a talk or a workshop
|
||||
19:37:41 <dg> Exactly my thoughts. Stickers are cool and all but they only vaguely provoke interest.
|
||||
19:37:55 <iRelay> <weltende@freenode> (hmm.. maybe I should bring a big "LANG=en" along this time :P)
|
||||
19:37:55 <dg> A workshop/talk would be far better
|
||||
19:38:04 <iRelay> <weltende@freenode> +sign
|
||||
19:38:12 <dg> (A talk would have lasting effects)
|
||||
19:38:37 <iRelay> * weltende@freenode is an terrible speaker.. *waves vaguely at other people*
|
||||
19:38:52 <hottuna_> What would be the talking points of a talk?
|
||||
19:38:55 <hottuna_> a general into talk probably wouldnt be very interesting to many people
|
||||
19:39:39 <dg> It's not really *our* place to perform a talk on the French researcher's points
|
||||
19:39:41 <iRelay> <weltende@freenode> we could do an getting started with i2p workshop or so?
|
||||
19:39:49 <dg> General intro would need some sort of point also
|
||||
19:39:51 <dg> Yeah
|
||||
19:40:01 <hottuna_> intro*
|
||||
19:40:01 <hottuna_> (due to the technical nature of the event)
|
||||
19:40:16 <LaughingBuddha> Maybe a comparison to other solutions like tor?
|
||||
19:40:31 <LaughingBuddha> s/solutions/options/
|
||||
19:40:34 <iRelay> LaughingBuddha meant: Maybe a comparison to other options like tor?
|
||||
19:41:22 <hottuna_> What does make I2P an attractive option?
|
||||
19:41:22 <Schnaubelt> LaughingBuddha: maybe I didn't see your suggestion in context, but I don't think we should compare software made for different purposes.
|
||||
19:41:34 <dg> Tor's .onion then, heh.
|
||||
19:41:45 <dg> That may or may not interest the CCC folk
|
||||
19:42:00 <dg> It'd still be somewhat generic *as a talk*
|
||||
19:42:06 <dg> A workshop however would be perfectly apt
|
||||
19:43:34 <darrob> i don't think differences to tor are a good topic. they are rather subtle from a listener's POV and you would have to go into too much detail.
|
||||
19:43:49 <RN> workshops are good if you can get a knowledgable volunteer to run it
|
||||
19:44:00 <darrob> i vaguely remember an i2p workshop in the past that didn't go so well. i might be making that up though.
|
||||
19:44:11 <str4d> What would we be trying to convey to the listeners? Are we assuming no knowledge of I2P? Passing knowledge?
|
||||
19:44:15 <dg> any hint as to why?
|
||||
19:44:26 <hottuna_> There was a tor/i2p workshop last ccc, but it was cancelled by its creator (gamambel). About 10 ppl were there before realizing it was cancelled.
|
||||
19:45:04 <iRelay> <weltende@freenode> ah.. I remember
|
||||
19:45:04 <dg> str4d: I'd assume a brief kind of acknowledgement and "hey, I've heard of that. maybe." but nothing more(?)
|
||||
19:45:18 <dg> hottuna_: is 10 good or bad for CCC? I've really no idea about it :(
|
||||
19:45:18 <LaughingBuddha> Schnaubelt: I am aware of that. But i2p and tor often get used in the same sentence.
|
||||
19:47:44 <hottuna_> I dont know, not terrible at the very least?
|
||||
19:47:47 <str4d> What does a workshop usually entail?
|
||||
19:47:47 <hottuna_> Im not sure, that was the only one I've ever been to.
|
||||
19:47:47 <RN> welt please pm me on ein after meeting... have a couple questions
|
||||
19:47:50 <darrob> i think a lightning talk would be pretty good. a diverse selection of people watch them for one. and even if they wonder about the apparent lack of differences to tor, it's still a win if that gets them to look into it more.
|
||||
19:47:50 <hottuna_> But probably some setting up and demo:ing
|
||||
19:47:50 <hottuna_> yeah, a lightning talk would be appropriate
|
||||
19:48:13 <hottuna_> do we have anything new and/or interesting to present?
|
||||
19:48:19 *** Farside <Farside!Farside@irc2p> has left #i2p-dev (leaving)
|
||||
19:48:22 <hottuna_> maybe something that tor does not offer?
|
||||
19:48:28 <iRelay> <weltende@freenode> RN: k
|
||||
19:48:32 <dg> Well, torrents..
|
||||
19:48:36 <dg> That's not new but.
|
||||
19:48:42 <dg> Big.
|
||||
19:49:28 <hottuna_> the torrent bridging idea/infrastructure is interesting
|
||||
19:49:39 <hottuna_> but not very complete/deployed
|
||||
19:50:41 <str4d> Yeah, that needs work.
|
||||
19:51:00 <hottuna_> having a lightning talk is something the ccc visitors can discuss later on
|
||||
19:51:00 <darrob> hottuna_: that would deserve an extra lightning talk. i'd worry that mentioning it briefly with i2p would only create the old "is everyone an exit node?" kind of confusion.
|
||||
19:51:11 <hottuna_> it doesnt have to be planned extensively
|
||||
19:51:14 <str4d> What would our desired result be? What sort of people would/should this attract? New general users? New high-profile routers? New technical users? New researchers?
|
||||
19:52:23 <hottuna_> technical users and researchers?
|
||||
19:52:46 <str4d> darrob, true. We do need to be consistent with terminology in that respect I think - outproxies are a service run by volunteers, just like IRC servers, eepsites and repository hosts. They are not something hard-baked into the router like Tor.
|
||||
19:55:44 <str4d> In that case, posing some open research questions near the end of the talk would be useful, to show that there is room for novel research (always a drawcard for academics ^_^)
|
||||
19:56:19 <darrob> str4d: sounds good.
|
||||
19:56:19 <RN> yes squashing the misconception that I2P is meant to hide your login on facebook should be a big bullet point in any such talk/demo imho
|
||||
19:59:09 <str4d> "I2P is not a ${DEITY}damn proxy!"
|
||||
19:59:34 <dg> Hm, ok
|
||||
19:59:55 <RN> proxy is a really tricky term in I2P context
|
||||
20:00:24 <str4d> Yep. That's why I changed the default text for the IRC tunnel.
|
||||
20:00:46 <str4d> (It said "IRC proxy" which is *technically* true but not in the way users think it)
|
||||
20:00:53 <dg> I think those of us visiting CCC could *really* do a workshop this year, and possibly a lightning talk (although that'd most likely be regarding torrents)
|
||||
20:01:05 <dg> Time to move on to website
|
||||
20:01:05 <dg> ?
|
||||
20:06:52 <RN> did you skip updated info on mergability?
|
||||
20:08:14 * dg missed messages
|
||||
20:09:02 <dg> str4d: that's a good idea
|
||||
20:09:05 <dg> also:
|
||||
20:09:12 <dg> <+dg> I think those of us visiting CCC could *really* do a workshop this year, and possibly a lightning talk (although that'd most likely be regarding torrents)
|
||||
20:09:12 <dg> <+dg> Time to move on to website
|
||||
20:09:12 <dg> <+dg> ?
|
||||
20:10:19 <dg> Messages keep getting dropped. gah.
|
||||
20:10:19 <topiltzin> oops sorry I was late
|
||||
20:10:26 <dg> no problem
|
||||
20:10:26 * topiltzin catching up with backlog
|
||||
20:10:49 *** w8rabbit_ is now known as w8rabbit
|
||||
20:11:11 <iRelay> <ReturningNovice_@kytv> dg, I was asking if you were skipping over mergability of fux update to website, (but my connection is tripping)
|
||||
20:11:39 <dg> Mine is too.
|
||||
20:12:08 <iRelay> * ReturningNovice_@kytv flips some switches and adjusts some knobs
|
||||
20:12:14 <str4d> fux hasn't changed in the last week, so no need to cover it at present.
|
||||
20:12:25 <dg> I am. The outcome last time wasn't good and the fux folk have expressed that any merging is not desirable (at least right now). It may be possible for us to grab some features in future but I guess there's more important things right now?
|
||||
20:12:28 <dg> Perhaps I'm wrong.
|
||||
20:12:28 <dg> Yeah.
|
||||
20:13:43 <str4d> (I'm working on feeds for 0.9.5 so that's my priority)
|
||||
20:13:54 <dg> Oh, right.
|
||||
20:14:20 <dg> I setup #i2p-www (just reg'd it), and the idea was that me among others could participate in a "book sprint" almost to get the pages done
|
||||
20:14:28 <dg> I wasn't sure which pages *actually* needed work, though
|
||||
20:14:57 <dg> The idea is that #i2p-www could be used as a sort of web committee to get revamp up to scratch and report back to -dev (in meetings I assume) when there's updates
|
||||
20:15:28 <hottuna> We're updating docs or are we revamping the site?
|
||||
20:15:37 <dg> Revamping the site
|
||||
20:15:51 <dg> <@dg> http://vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p/en/site/
|
||||
20:15:51 <dg> <@dg> i2p.www.revamp is the mtn
|
||||
20:15:57 <str4d> dg, I'd recommend that text revamp be done know
|
||||
20:16:00 <str4d> argh
|
||||
20:16:03 <dg> We determined that the current design isn't friendly enough etc.
|
||||
20:16:20 <str4d> in I2p.www
|
||||
20:16:48 <topiltzin> ok caught up with backlog
|
||||
20:16:59 <str4d> and design/structure of the new site in I2p.www.revamp
|
||||
20:16:59 <topiltzin> we on website now?
|
||||
20:17:07 <dg> yup
|
||||
20:17:22 <hottuna> alright! duck's design. Very nice.
|
||||
20:17:34 <dg> str4d: If that's easier for you, sure.
|
||||
20:17:57 <topiltzin> do we have a eepsite with that design?
|
||||
20:18:04 <topiltzin> does it require javascript for anything?
|
||||
20:18:11 <christop1> huch can you reaach the eepsite
|
||||
20:18:11 <christop1> ?
|
||||
20:18:20 <dg> &cs http://vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p/en/site/
|
||||
20:18:20 <iRelay> Trying to check status of "http://vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p/en/site/" for dg. Please wait...
|
||||
20:18:26 <iRelay> http://vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p/en/site/ responded with status 200 within 5 seconds.
|
||||
20:19:09 <topiltzin> and "Ur mom" is still there. :-/
|
||||
20:19:12 <hottuna> What work needs to be done before it's a viable alternative?
|
||||
20:20:04 * dg is wondering this
|
||||
20:20:47 <str4d> topiltzin, I apologize for not removing that yet -_-
|
||||
20:20:58 <str4d> design needs work/overhaul
|
||||
20:21:45 <RN> yeah, I remember seing a preview of that... it was a nice profesional look...
|
||||
20:21:45 <RN> (and vekw35...i2p's bandwidth gets slashdotted lol)
|
||||
20:21:48 <str4d> but that can be worked on later, with multiple proposals if necessary
|
||||
20:21:55 <topiltzin> looks alright to me. Is all the content - mtn howto, developer keys, that stuff there?
|
||||
20:22:22 <str4d> first priority IMHO is getting backend finished.
|
||||
20:22:41 <str4d> topiltzin, I've migrated most of it.
|
||||
20:22:44 *** sayliwo_ is now known as sayliwo
|
||||
20:23:03 <RN> does the revamp use the regular trac tickets?
|
||||
20:23:41 <str4d> I'm still not happy with the page / navigation layout though..
|
||||
20:23:48 <RN> a ticket for "remove "ur mom" " would serve as a reminder to whom it gets assigned to...
|
||||
20:24:07 <topiltzin> I don't know if "Supported Software" is the best name for the middle column because it's really listing actions, not actual software
|
||||
20:24:30 <str4d> RN, the frontpage needs a rethink.
|
||||
20:25:09 <str4d> duck's layout copied the Tor site, and it would be good to make it more unique.
|
||||
20:25:20 <dg> Could we get a list of things that need doing so someone could perhaps tackle it/at least we have a clear, concise list?
|
||||
20:25:39 <hottuna> I agree dg
|
||||
20:25:54 <topiltzin> how drastic of a rethink do you have in mind, str4d ?
|
||||
20:25:57 <str4d> I can outline later what I know needs doing.
|
||||
20:26:19 <dg> Thanks!
|
||||
20:26:22 <dg> I guess we're done with that
|
||||
20:26:36 <dg> weltende: you here?
|
||||
20:26:46 <iRelay> <weltende@freenode> yup
|
||||
20:26:59 <str4d> topiltzin, I like the general layout, but the three columns content needs rethinking.
|
||||
20:28:17 <topiltzin> Agreed. I'm available to discuss whenever you think it's best
|
||||
20:29:45 <str4d> and the footer is almost unnecessary
|
||||
20:29:48 <str4d> fwiw the news column on the right is dynamic
|
||||
20:29:48 <str4d> (i.e add a new article to backed and the list is updated)
|
||||
20:29:48 <str4d> That's another thing- caching needs thought
|
||||
20:29:48 <str4d> </braindump>
|
||||
20:30:36 <topiltzin> dg: we can dig in deeper on the website or keep going - your call
|
||||
20:34:32 <dg> <+topiltzin> dg: we can dig in deeper on the website or keep going - your call
|
||||
20:34:35 <dg> <+dg> I'm fine with digging deeper, I just don't want this to drag on too long and have some people leave, but the remaining topic is pretty small and mainly just between me and welt
|
||||
20:35:11 <topiltzin> ok
|
||||
20:36:00 <topiltzin> I would change the name of the middle column "Supported Software" -> "What can I2P do"
|
||||
20:36:11 <topiltzin> and since we already have a similar question in the title above, I would consider changing that
|
||||
20:36:34 <topiltzin> maybe "What does I2P do for you" -> "What is I2P"
|
||||
20:37:28 <dg> RN: Do we actually have a trac category for this?
|
||||
20:37:35 <topiltzin> no passive tense on the front page == good
|
||||
20:37:38 <RN> I'd suggest changing "can be conducted anonymously on I2P." to "can be conducted anonymously inside I2P."
|
||||
20:37:50 <dg> Ooh.
|
||||
20:37:57 <dg> inside does sound far better, actually.
|
||||
20:38:08 <dg> A lot of people do not seem to understand that i2p is a space.
|
||||
20:38:19 <str4d> We don't want too much text on front page, but given the improved navigation, how much redundant linking is needed?
|
||||
20:38:37 <RN> dg, if we don't one could probably be created...
|
||||
20:38:59 <str4d> And could some of it be replaced with other feeds/intro text/something?
|
||||
20:39:14 <str4d> dg, www
|
||||
20:39:21 <dg> of course, I'll go create a ticket for "your mom".
|
||||
20:39:28 <topiltzin> What about simplifying that sentence a bit? "Many things would risk your privacy on the public Internet but you can do them anonymously inside I2P"
|
||||
20:39:46 * topiltzin was hoping we were mature enough to not need ticket for "ur mom" but we do, so be it
|
||||
20:40:48 <dg> Should I spare us the embarrassment or do we actually need to make a ticket?
|
||||
20:40:51 <topiltzin> I'm trying to come up with the most condensed and accessible description possible for the front page
|
||||
20:41:25 * RN giggles at "<dg> of course, I'll go create a ticket for "your mom"."
|
||||
20:41:44 <KillYourTV> I think str4d won't forget about it so it's probably not needed.
|
||||
20:41:59 <KillYourTV> (nor anyone else that does anything on it)
|
||||
20:42:02 <topiltzin> toss a coin. whatever it takes to get it done :-/
|
||||
20:42:05 <str4d> we don't need a ticket for it
|
||||
20:42:24 <RN> didn't mean to start such an uproar
|
||||
20:42:27 <dg> It'd be nice to have some things officially noted, although uh.. not the "your mom"..
|
||||
20:42:30 <str4d> as I said, I think that entire column needs replacing with something else.
|
||||
20:42:38 * dg sweeps "your mom"-gate under the rug.
|
||||
20:42:45 <RN> but at least we know there's definately an apropos place for such
|
||||
20:43:00 <str4d> dg, then a ticket for "replace left column content with something else"
|
||||
20:43:51 <dg> ok
|
||||
20:44:22 <topiltzin> left column could even go away entirely imo
|
||||
20:44:49 <topiltzin> gives us more room to expand on the functionality more
|
||||
20:45:16 <str4d> as
|
||||
20:45:16 <str4d> Argh, ignore that- _-
|
||||
20:45:49 <dg> Trac keywords are delimited by "," right?
|
||||
20:46:12 <KillYourTV> afaik, yes
|
||||
20:47:11 <topiltzin> we could even remove the heading "Supported Software" and just use that space to list the different things I2P can do
|
||||
20:47:26 <dg> http://trac.i2p2.i2p/ticket/792
|
||||
20:47:29 <topiltzin> better than list - give a small blurb on each if appropriate or include an icon
|
||||
20:47:39 <dg> topiltzin: That'd be sweet, actually.
|
||||
20:48:00 <str4d> remember that the navigation, columns and footer are just lists, so the left column could be altered/removed with a different theme as well.
|
||||
20:48:03 <dg> "Supported Software" isn't user friendly anyway
|
||||
20:49:06 <RN> hmm.... icons... that could get stylisticly opinionated quickly
|
||||
20:50:34 <str4d> icons etc should be left to theming. maybe we should think about the content we want on the front page for now, and not necessarily how it will be arranged?
|
||||
20:50:45 <topiltzin> if we can't agree on what icons we think look good we don't have to have any
|
||||
20:51:49 <topiltzin> you mean beyond removing the left column str4d ?
|
||||
20:52:35 <RN> yeah, I agree with str4d I think content first, form second, icons as eyecandy in theemes or later
|
||||
20:52:50 <RN> the most important two questions someone will likely have when they come to the site, are either, why do I need this? and I've got it, so what now?
|
||||
20:53:16 <str4d> Well, does it need removal? Would a brief intro with a "read more" link be useful? Would a small infographic be helpful?
|
||||
20:53:35 <str4d> Things like that - content.
|
||||
20:53:38 <topiltzin> I like infographics in Pretty Colors (TM)
|
||||
20:54:30 <topiltzin> and as RN asked - what do we answer when the first-time visitor asks "why do I need this?"
|
||||
20:54:33 <RN> yeah topiltzin, but you use paint
|
||||
20:54:40 <RN> ;)
|
||||
20:54:51 <topiltzin> it wouldn't be me alright, zero visual skill here :-P
|
||||
20:55:43 <RN> breif with a "read more" is a good idea imho
|
||||
20:55:57 <dg> <+dg> I'd rather not fill up trac with loads of unnecessary tickets but at the same time, it helps to keep a handle on what needs to be done.
|
||||
20:56:00 <dg> <+dg> Oh, and http://vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p/en/site/volunteer/bounties - Bounties links are broken.
|
||||
20:56:00 <dg> <+dg> I think I'm going to go ahead and make tickets for these.
|
||||
20:56:11 <iRelay> Title: Bounties - I2P (at vekw35szhzysfq7cwsly37coegsnb4rrsggy5k4wtasa6c34gy5a.b32.i2p)
|
||||
20:56:40 <str4d> dg, are they? Must have missed a link migration...
|
||||
20:57:11 <KillYourTV> I tried a few links at random and they loaded for me
|
||||
20:57:18 <topiltzin> what would you say in such brief RN ?
|
||||
20:57:45 <dg> GCJ, for example. "http://dev.i2p.net/cgi-bin/cvsweb.cgi/i2p/Makefile.gcj"
|
||||
20:57:52 <dg> A duck.i2p one too.
|
||||
20:58:07 <dg> I'll trac these too.
|
||||
20:59:10 <str4d> Oh, that is text- related dg
|
||||
20:59:17 <RN> well, I'd say something like, the internet is watching you...
|
||||
20:59:17 <RN> lol
|
||||
20:59:24 * dg notes
|
||||
20:59:24 <str4d> they will fail on current website as well.
|
||||
20:59:39 <RN> I'd need a little time to think up something more serious
|
||||
20:59:47 <dg> str4d: Thanks :)
|
||||
21:00:13 <topiltzin> I'm not opposed to having something not-so-serious but not all the way to "ur mom"
|
||||
21:01:25 <topiltzin> ideally something inviting.. not too formal
|
||||
21:01:36 <topiltzin> definitely worth brainstorming
|
||||
21:06:05 <MTN_> i2p.trac: #795: Bounties being broken http://trac.i2p2.i2p/ticket/795
|
||||
21:06:08 <MTN_> i2p.trac: #793: Mirror links http://trac.i2p2.i2p/ticket/793
|
||||
21:06:08 <MTN_> i2p.trac: #792: Replace left column content http://trac.i2p2.i2p/ticket/792
|
||||
21:06:43 <dg> <+dg> Tickets #793 - #795 I have created so far.
|
||||
21:06:43 <dg> <+topiltzin> ideally something inviting.. not too formal
|
||||
21:06:43 <dg> <+topiltzin> definitely worth brainstorming
|
||||
21:06:43 <dg> <+dg> btw I'm in no rush to close this up unless you guys are ready
|
||||
21:07:41 <topiltzin> I guess it comes down to why do we want more people to use i2p and what do we tell them so that they start using it
|
||||
21:08:00 <RN> mirroring and ssl are the only remaining items, aside from brainstorming about the content?
|
||||
21:08:19 <dg> SSL is between me and welt mainly, and I made a ticket for it
|
||||
21:08:19 <topiltzin> wanna take care of those two and come back to content at the end?
|
||||
21:08:34 <dg> Mirroring was touched on last week.. I think we still may need welt for that.
|
||||
21:08:34 <dg> Oh.
|
||||
21:08:42 <dg> I'd like to bring up something, actually
|
||||
21:08:56 <iRelay> <weltende@freenode> I am here..
|
||||
21:09:00 <dg> Do you guys think that a mailing list returning for dev discussion etc would be useful or not?
|
||||
21:09:10 <topiltzin> +1 yes please
|
||||
21:09:17 <dg> weltende: See ticket #794
|
||||
21:09:29 <dg> imo we closed the discussion wrt SSL last week
|
||||
21:09:40 <RN> a mailing list yes, would be good to start one up again imhho
|
||||
21:09:43 <hottuna> Im not so sure about a mailinglist. zzz.i2p seems to fill that void very well.
|
||||
21:10:02 <iRelay> http://trac.i2p2.i2p/ticket/794 - (assigned defect) - SSL
|
||||
21:10:03 <RN> though, the warm fish has a good point
|
||||
21:10:39 <iRelay> <weltende@freenode> hottuna: the old ML attracted outsiders though..
|
||||
21:10:59 <hottuna> zzz.i2p is also already established and working quite well
|
||||
21:11:23 <iRelay> <weltende@freenode> hottuna: not as much as the ML used to be
|
||||
21:11:35 <hottuna> welt: yeah, that is true. but it has to be useful and not just bloat for the sake having more stuff
|
||||
21:11:56 <topiltzin> both work although mailing lists in general are very common in open-source projects
|
||||
21:11:56 <topiltzin> it's a long-standing tradition in a way. I can live with zzz.i2p but I'd feel right at home with a developer mailing list
|
||||
21:12:17 <str4d> mailing list could be handy (I'd considered setting a mailing list site up, but wasn't sure how to handle emails without creating one email per list on postman)
|
||||
21:12:23 *** blitzkrieg_ is now known as blitzkrieg
|
||||
21:12:38 <topiltzin> is attracting outsiders a bad thing? ;-)
|
||||
21:12:46 <hottuna> maybe build it and they will come? if no-one cares it will die soon enough
|
||||
21:13:00 <iRelay> <weltende@freenode> topiltzin: I meant it as a pro-argument for an ML
|
||||
21:13:12 <topiltzin> oh ok
|
||||
21:13:32 <hottuna> alternatively ask zzz for an externalized versions / linkto zzz.i2p.to / linkto zzz.i2p.in
|
||||
21:13:39 <iRelay> <weltende@freenode> yeah.. will set one up once I have time
|
||||
21:14:43 <topiltzin> I generally don't feel comfortable typing in my password when using those in/out proxies but others may not mind
|
||||
21:15:56 <hottuna> yeah, an inproxy is probably not optimal
|
||||
21:16:26 <dg> <+dg> This exists, by the way. It's dead though.
|
||||
21:16:29 <topiltzin> what's the last thing you got dg?
|
||||
21:16:29 <dg> <+dg> http://lists.welterde.de/mailman/listinfo/i2p-general
|
||||
21:16:29 <dg> <+dg> Also, might wanna turn directory listing off on *.welterde.de.
|
||||
21:16:32 <dg> <+dg> http://lists.welterde.de/mailman/
|
||||
21:16:32 <dg> <+dg> Anyway, ok
|
||||
21:16:32 <dg> <+topiltzin> I generally don't feel comfortable typing in my password when using those in/out proxies but others may not mind
|
||||
21:16:35 <iRelay> Title: I2p-general Info Page (at lists.welterde.de)
|
||||
21:16:35 <dg> <+dg> I don't either.
|
||||
21:16:38 <iRelay> Title: Index of /mailman/ (at lists.welterde.de)
|
||||
21:17:14 <iRelay> <weltende@freenode> dg: ah.. I forgot about that.. just never made it onto the website I guess..
|
||||
21:17:25 <iRelay> <weltende@freenode> (would rather make it lists.i2p2.de or so though)
|
||||
21:17:33 <dg> I would too :-)
|
||||
21:20:27 <dg> topiltzin, personally - I'd like a mailing list but for me, at least it'd be more about the professionalism of it et all, rather than any benefit I can describe to you and preach
|
||||
21:20:42 <dg> but I suppose the rest of you feel that it'd be beneficial, so that's good
|
||||
21:20:45 <topiltzin> dg: return true;
|
||||
21:20:45 <topiltzin> having mailing list archives is very useful; makes the project more like other open-source projects if nothing else
|
||||
21:21:49 <topiltzin> how is that different from zzz.i2p + inproxy access : not much different other than the random new developer would have less of a learning curve to deal with
|
||||
21:22:30 <topiltzin> also allowing search engines to index the mailing list archives contributes to the global knowledge base so that's good
|
||||
21:22:40 <RN> or someone curious about I2P could read some discussion and perhaps decide to install it and try it out
|
||||
21:22:55 <topiltzin> very often I'm searching for something and I find the answer in the mailing archive of some open-source project
|
||||
21:23:18 <topiltzin> RN: that is possible, I prefer to keep all possible venues open.
|
||||
21:23:28 <iRelay> <weltende@freenode> topiltzin: the ML is not about new developers.. or people that are involved in i2p at all.. but rather people outside of the project, that critique the protocol, implementation, etc.
|
||||
21:23:40 <topiltzin> and then let the users / developers / market decide which place is the best
|
||||
21:23:47 <iRelay> <weltende@freenode> which has very much died down since the crash
|
||||
21:24:14 <topiltzin> I don't see why it can't be for both, weltende
|
||||
21:24:44 <iRelay> <weltende@freenode> topiltzin: sure.. but imho my aspect is the more important aspect ;-)
|
||||
21:25:04 <topiltzin> :-P
|
||||
21:25:14 <dg> <+topiltzin> I don't see why it can't be for both, weltende
|
||||
21:25:14 <dg> <+dg> Also, going to throw an idea out here: geti2p.net as a default domain from some $period onwards
|
||||
21:25:14 <dg> <+dg> (maybe when we launch the new design)
|
||||
21:25:34 <dg> <+dg> <+dg> I was thinking that, actually
|
||||
21:25:34 <dg> <+dg> <+dg> It paints a better picture
|
||||
21:25:34 <dg> <+dg> <+topiltzin> I don't see why it can't be for both, weltende
|
||||
21:25:34 <dg> <+dg> <+dg> Also, going to throw an idea out here: geti2p.net as a default domain from some $period onwards
|
||||
21:25:37 <dg> <+dg> <+dg> (maybe when we launch the new design)
|
||||
21:25:44 <hottuna> I like geti2p.net
|
||||
21:25:55 <topiltzin> iRelay> <weltende@freenode> topiltzin: sure.. but imho my aspect is the more important aspect ;-)
|
||||
21:25:55 <topiltzin> <topiltzin> :-P
|
||||
21:26:06 <dg> So do I, not perfect (i2p.net would be better, obviously) but better than the current IMO.
|
||||
21:26:17 <KillYourTV> ticket #795 is now fixed for the live site.
|
||||
21:26:20 <dg> also, sorry for my flaky connection.
|
||||
21:26:26 <iRelay> <weltende@freenode> the stickers already say geti2p.net iirc ;)
|
||||
21:26:34 <iRelay> http://trac.i2p2.i2p/ticket/795 - (new defect) - Bounties being broken
|
||||
21:26:38 <str4d> Is I2p.net still registered to jrandom?
|
||||
21:26:48 <dg> it was paid for many years
|
||||
21:26:51 <dg> so yes
|
||||
21:26:58 <dg> unless jrandom returns, we're kind of screwed.
|
||||
21:27:02 <dg> There's no promise we'll get i2p.net once it expires, either.
|
||||
21:27:08 <dg> (unless we go to ICANN?)
|
||||
21:27:10 <iRelay> <weltende@freenode> yeah... until 2016
|
||||
21:27:18 <str4d> And I agree with your idea dg
|
||||
21:27:29 <iRelay> <weltende@freenode> dg: verizone actually
|
||||
21:27:42 <topiltzin> yeah, new design + new domain name = freshness
|
||||
21:27:51 <iRelay> <weltende@freenode> err.. verisign
|
||||
21:27:57 <dg> I thought you'd go to ICANN for getting a domain back if someone else steals it afterwards, say it is your "brand".
|
||||
21:28:04 <str4d> I already plan to have the site dynamically change URLs for sites it knows are available inside and outside I2p
|
||||
21:28:15 <dg> sadly, I doubt we can go to ICANN/etc now and say "hey, can we have it now please? We don't want to wait until 2016!"
|
||||
21:28:35 <dg> (unless we have some good friends)
|
||||
21:28:41 <iRelay> <weltende@freenode> dg: no.. ICANN only deals with TLD's.. you have to go to the TLD
|
||||
21:28:49 <str4d> So e.g. forum.I2p <-> forum.i2p2.de
|
||||
21:28:52 <dg> ah, rite
|
||||
21:29:07 <dg> Is it possible to get in contact with $hostOfForum?
|
||||
21:29:11 <str4d> We could get *.i2p? :D
|
||||
21:29:22 <dg> forum.i2p is/was popular and the stability would help..
|
||||
21:29:51 <dg> (It doesn't help that an officially linked forum is down a lot of the time and we have.. no forum for users). It worked good for a while.
|
||||
21:30:08 <dg> str4d: also, yes. the "(in i2p)" and conflicting linking styles on pages is strange and obscure.
|
||||
21:30:15 <dg> I'd rather what you suggested. :-)
|
||||
21:31:10 <dg> btw - "2007-09-28 - Syndie 1.101a" is kind of lame to have on the site..
|
||||
21:35:18 <RN> syndie actually is something I think we should keep
|
||||
21:35:25 <RN> it needs a dev to show it some love, but it works and is quite usefull once you get used to it
|
||||
21:35:25 <RN> heck, putting this meeting log in syndie would be a cool idea imho
|
||||
21:35:32 <dg> Keep but find someone to work on.
|
||||
21:35:35 <dg> Yeah.
|
||||
21:36:14 <topiltzin> So we have domain name, mailing list, content brainstorm. Any specific one we want to or need to focus on further?
|
||||
21:36:56 <dg> I don't think so, but maybe someone disagrees heh.
|
||||
21:38:53 <topiltzin> what do you mean by "should keep" RN?
|
||||
21:39:05 <dg> <+dg> btw - "2007-09-28 - Syndie 1.101a" is kind of lame to have on the site..
|
||||
21:40:30 <iRelay> <RN__@kytv> I think syndie has huge potential
|
||||
21:41:02 <iRelay> <RN__@kytv> it seemed dg was suggesting removing it from the software list or something
|
||||
21:41:18 <KillYourTV> We need to have updated tarballs/installers linked. Perhaps we should also have syndie.i2p2.de managed by mtn as well.
|
||||
21:41:40 <dg> Kind of. I was proposing that we perhaps hide the date or change the design to have it standing out less, it looks bad IMHO to have such stale software on the page
|
||||
21:41:47 <dg> It hurts first impressions of Syndie and i2p
|
||||
21:42:01 <dg> KillYourTV: Yeah. Just having those tarballs/etc up would help..
|
||||
21:42:04 <topiltzin> Maybe we can keep it but remove the date? I think the lameness stems from the 2007 token
|
||||
21:42:15 <dg> (and the broken installer..)
|
||||
21:42:19 <dg> s/installer/packaging
|
||||
21:42:29 <iRelay> <RN@kytv> ah, just changing the link text to "Syndie"
|
||||
21:42:29 <topiltzin> that is until active development picks up again (re: removing the date)
|
||||
21:42:32 <iRelay> <RN@kytv> I agree
|
||||
21:43:28 <iRelay> <RN@kytv> yeah, I'm with that
|
||||
21:43:44 <topiltzin> :)
|
||||
21:43:55 <str4d> dg, revamp doesn't have it there.
|
||||
21:43:55 <str4d> That box on current site is meant to be the equivalent of the "news"
|
||||
21:43:55 <str4d> Having a Syndie link would be good, but more as e.g. part of middle column.
|
||||
21:44:05 <dg> I think we're mostly done
|
||||
21:44:16 <dg> Although netsplit
|
||||
21:44:23 <str4d> (So the 2007 syndie page is still there, but accessible through the blog)
|
||||
21:44:26 <dg> pfft, I don't think we're missing anyone who was involved
|
||||
21:44:33 <dg> Good meeting, guys.
|
||||
21:44:40 <dg> How about 8:00PM next time?
|
||||
21:44:43 <iRelay> <weltende@freenode> dg: next meeting could with a bit more structure ;-)
|
||||
21:45:14 <dg> weltende: heh, sorry. We had a lot to talk about and I didn't anticipate it'd go like this, I figured it'd be short. I'll include that in my planning next time. :-)
|
||||
21:45:14 <dg> oh well
|
||||
21:45:17 <dg> still, good outcome.
|
||||
21:45:24 <topiltzin> RN: since you brought the focus on content I'm looking forward to hearing your suggestions :)
|
||||
21:45:31 <str4d> Mmm. Maybe structure the shorter topics first, and the more discussion-y ones later.
|
||||
21:45:31 <topiltzin> whenever they're available
|
||||
21:45:42 <topiltzin> +1 str4d
|
||||
21:45:53 <topiltzin> the more open-ended ones at the end makes sense
|
||||
21:45:56 <dg> str4d: Yeah, might be a good idea. I hope I'm doing okay though, heh.
|
||||
21:45:59 <dg> I think I have.
|
||||
21:46:14 <str4d> It's better than no meeting at all =)
|
||||
21:46:28 <topiltzin> topiltzin> RN: since you brought the focus on content I'm looking forward to hearing your suggestions :)
|
||||
21:46:31 <topiltzin> <topiltzin> whenever they're available
|
||||
21:46:31 * dg smiles
|
||||
21:46:42 <topiltzin> return true; // ;-)
|
||||
21:46:44 <iRelay> <RN@kytv> you are getting a good start dg...
|
||||
21:46:44 <dg> topiltzin: nah, RN got it from kytv
|
||||
21:47:10 <iRelay> <RN@kytv> yeah yeah topz
|
||||
21:47:13 <iRelay> <RN@kytv> ;)
|
||||
21:47:23 <iRelay> <RN@kytv> so did you bang the mallot... ?
|
||||
21:47:27 <dg> I'm glad, I feel as if we've done something good today (and last week)
|
||||
21:47:27 * dg uh.. bamfs the meeting closed.
|
||||
21:47:38 <dg> Meeting will be 8:00PM next time, same day.
|
||||
21:47:47 <iRelay> <RN@kytv> YAY! officialness
|
||||
21:47:47 <dg> RN: bam
|
||||
21:48:05 <iRelay> <RN@kytv> :)
|
||||
21:48:06 * dg highfives RN
|
||||
21:48:20 *** KillYourTV changes topic to "Latest dev build: 0.9.3-11 | Dev mtg here 8:00 PM (20:00) UTC Tues. Dec. 4 | Report bugs at http://trac.i2p2.i2p / http://trac.i2p2.de"
|
||||
21:48:28 <iRelay> * RN@kytv gives dg a beer
|
||||
21:48:31 <topiltzin> **smooth**
|
||||
21:48:38 <iRelay> <weltende@freenode> dg: actually it used to be *baf*s I think :P
|
||||
21:48:50 <dg> drat
|
||||
21:48:53 * dg notes
|
||||
21:49:00 <str4d> Yep. So not finished yet =P
|
||||
21:49:30 <dg> *baf*s
|
||||
{% endfilter %}
|
||||
{# TODO: pygments #}
|
||||
</pre>
|
||||
</div>
|
||||
{% endblock %}
|
||||
@ -7,65 +7,18 @@ Following are links to papers, presentations, videos, and tutorials about I2P.
|
||||
</p><p>
|
||||
To request an addition to this page, please send to press ~~~at~~~ i2p2.de.
|
||||
</p><p>
|
||||
Newest links are at the bottom of the page.
|
||||
Newest links are at the bottom of each section.
|
||||
</p>
|
||||
<div class="links">
|
||||
|
||||
<h2>Papers and Research</h2>
|
||||
<ul>
|
||||
|
||||
<li>
|
||||
IIP Presentation at CodeCon
|
||||
<a href="http://invisibleip.sourceforge.net/iip/resources/codecon_0x90.mp3">MP3 audio</a>
|
||||
<a href="http://invisibleip.sourceforge.net/iip/resources/iip_transcript.txt">transcript</a>
|
||||
Lance James (0x90), February 2002.
|
||||
|
||||
</li><li>
|
||||
0x90 Interviewed by DistributedCity
|
||||
<a href="http://invisibleip.sourceforge.net/iip/mediaDCInterview1.php">Part 1</a>
|
||||
<a href="http://invisibleip.sourceforge.net/iip/mediaDCInterview2.php">Part 2</a>
|
||||
July 26, 2002.
|
||||
|
||||
</li><li>
|
||||
IIP Presentation at ToorCon
|
||||
<a href="http://invisibleip.sourceforge.net/iip/resources/toorconspeech.mp3">MP3 audio</a>
|
||||
<a href="http://invisibleip.sourceforge.net/iip/resources/toorconspeech/">slides</a>
|
||||
Lance James (0x90), September 2002.
|
||||
|
||||
</li><li>
|
||||
0x90 Interviewed by El Pais
|
||||
(original in Spanish)
|
||||
<a href="http://invisibleip.sourceforge.net/iip/resources/elpais-iip.txt">English translation</a>
|
||||
October 31, 2002.
|
||||
|
||||
</li><li>
|
||||
<a href="/_static/pdf/i2p_philosophy.pdf">Invisible Internet Project (I2P) Project Overview</a>, jrandom, August 28, 2003.
|
||||
</li>
|
||||
|
||||
</li><li>
|
||||
<a href="http://www.businessweek.com/magazine/content/03_37/b3849089_mz063.htm">2003 Business Week article referencing invisiblenet</a>
|
||||
|
||||
</li><li>
|
||||
<a href="http://www.netzwelt.de/news/75371-i2p-das-anonyme-netz-im.html">Netzwelt.de article about being anonymous in the Internet</a>
|
||||
(German)
|
||||
November 2007.
|
||||
|
||||
</li><li>
|
||||
<a href="http://www.youtube.com/watch?v=TsfdzfGZyu0">To Be or I2P</a>
|
||||
(Youtube Video)
|
||||
An introduction into anonymous communication with I2P.
|
||||
<a href="http://events.ccc.de/congress/2007/Fahrplan/attachments/1017_24c3-i2p.pdf">To Be or I2P (PDF presentation)</a>,
|
||||
Jens Kubieziel, 24C3 Berlin, December 28, 2007.
|
||||
|
||||
</li><li>
|
||||
<a href="http://www.gulli.com/news/i2p-an-anonymous-network-2009-03-09/">zzz interviewed by gulli.com</a>
|
||||
March 2009
|
||||
<a href="http://www.gulli.com/news/i2p-anonymes-netzwerk-im-2009-03-09/">German translation</a>
|
||||
<a href="http://translated.by/you/i2p-an-anonymous-network-interrogated/into-ru/">Russian translation</a>
|
||||
|
||||
</li><li>
|
||||
<a href="http://marge.informatik.tu-chemnitz.de/archiv/CLT2009/V4-Sa1200-Security-Lars_Schimmer.mp4">Video of I2P talk at Chemnitz Linux Tag</a>,
|
||||
Lars Schimmer,
|
||||
March 14-15, 2009
|
||||
|
||||
</li><li>
|
||||
<li>
|
||||
<a href="/_static/pdf/I2P-PET-CON-2009.1.pdf">Peer Profiling and Selection in the I2P Anonymous Network</a> -
|
||||
zzz and Lars Schimmer,
|
||||
presented at
|
||||
@ -74,8 +27,9 @@ Dresden, Germany, March 24-25, 2009.
|
||||
Also available in the
|
||||
<a href="http://freehaven.net/~karsten/volatile/petcon-proceedings-2009.1.pdf">Proceedings</a>
|
||||
page 59.
|
||||
</li>
|
||||
|
||||
</li><li>
|
||||
<li>
|
||||
Anonymity Techniques - Usability Tests of Major Anonymity Networks
|
||||
- Jens Schomburg,
|
||||
Presented at
|
||||
@ -85,8 +39,9 @@ Available in the
|
||||
<a href="http://freehaven.net/~karsten/volatile/petcon-proceedings-2009.1.pdf">Proceedings</a>
|
||||
page 49.
|
||||
Extended 20-page version also may be available.
|
||||
</li>
|
||||
|
||||
</li><li>
|
||||
<li>
|
||||
L'émergence au sein d'internet de communautés virtuelles et anonymes, Freenet et i2p
|
||||
- Laurie Delmer -
|
||||
Université catholique de Louvain
|
||||
@ -95,81 +50,17 @@ Département des sciences politiques et sociales
|
||||
Department of Political and Social Science -
|
||||
The rise in internet virtual and anonymous communities, Freenet and I2P)
|
||||
Master's Thesis, 2009.
|
||||
</li>
|
||||
|
||||
</li><li>
|
||||
<a href="http://www.youtube.com/watch?v=5J3nh1DoRMw">I2P Windows Tutorial</a>
|
||||
(Youtube Video)
|
||||
This guide will show you how to install I2P in Windows XP.
|
||||
By <a href="http://telecomix.org/">Telecomix</a>
|
||||
|
||||
</li><li>
|
||||
<a href="http://www.youtube.com/watch?v=QeRN2G9VW5E">I2P Debian Tutorial</a>
|
||||
(Youtube Video)
|
||||
This will guide you through how to install I2P on a Debian Linux System.
|
||||
By <a href="http://telecomix.org/">Telecomix</a>
|
||||
|
||||
</li><li>
|
||||
<a href="http://www.youtube.com/watch?v=2ylW85vc7SA">How to set up anonymous site in I2P</a>
|
||||
(Youtube Video)
|
||||
How to set up an anonymous web site in I2P.
|
||||
By <a href="http://telecomix.org/">Telecomix</a>
|
||||
|
||||
</li><li>
|
||||
<a href="http://www.youtube.com/watch?v=d8mvGZqVgE4">I2P Tutorial Mac OS X</a>
|
||||
(Youtube Video)
|
||||
A tutorial on how to run i2p on Mac OS X and how to connect to irc.telecomix.i2p.
|
||||
By <a href="http://telecomix.org/">Telecomix</a>
|
||||
|
||||
</li><li>
|
||||
<a href="http://www.youtube.com/watch?v=5jv7tVVJdTQ">Felix Atari explains the basic principles of I2P</a>
|
||||
(Youtube Video)
|
||||
Agent Felix Atari of the Telecomix Crypto Munitions Bureau.
|
||||
By <a href="http://telecomix.org/">Telecomix</a>
|
||||
|
||||
</li><li>
|
||||
HOPE New York July 17, 2010 - Brief overview of I2P by zzz, at the end of Adrian Hong's talk
|
||||
"Hackers for Human Rights".
|
||||
<a href="http://c2047862.cdn.cloudfiles.rackspacecloud.com/tnhc21.mp3">MP3 audio</a>
|
||||
|
||||
</li><li>
|
||||
<a href="http://www.youtube.com/watch?v=WyN_QK-_3GA">How to get onto I2P, the anonymous P2P Darknet (Windows Install)</a>
|
||||
(Youtube Video)
|
||||
This tutorial shows how to install and configure software needed to access I2P.
|
||||
|
||||
</li><li>
|
||||
<a href="http://www.youtube.com/watch?v=q4owyd_CaGc">How to connect to I2P</a>
|
||||
(Youtube Video)
|
||||
How to install I2P on Ubuntu.
|
||||
|
||||
</li><li>
|
||||
<a href="http://www.irongeek.com/i.php?page=videos/i2p-darknet-software-in-linux">Installing the I2P darknet software in Linux</a>
|
||||
(Video)
|
||||
Adrian Crenshaw.
|
||||
January 2011
|
||||
|
||||
</li><li>
|
||||
<li>
|
||||
<a href="http://www.irongeek.com/i.php?page=security/darknets-i2p-identifying-hidden-servers">Darknets - I2P Identifying Hidden Servers</a>
|
||||
Adrian Crenshaw.
|
||||
Presented at Black Hat DC,
|
||||
January 18-19 2011
|
||||
<a href="http://translated.by/you/darknets-and-hidden-servers-identifying-the-true-ip-network-identity-of-i2p-service-hosts/into-ru/">Russian translation</a>
|
||||
</li>
|
||||
|
||||
</li><li>
|
||||
<a href="http://www.irongeek.com/i.php?page=videos/shmoocon-firetalks-2011">Into the I2P Darknet: Welcome to Cipherspace</a>
|
||||
Adrian Crenshaw. Schmoocon Firetalk, January 2011
|
||||
|
||||
</li><li>
|
||||
<a href="http://www.youtube.com/watch?v=TexNr_5J5AU">Using techhnology to advance liberty</a>
|
||||
(Youtube Video)
|
||||
Eric Johnson.
|
||||
<a href="http://agora.io/etienne">Agora I/O Unconference</a>, March 27, 2011.
|
||||
I2P covered from 10:00 to 20:00 in the video.
|
||||
|
||||
</li><li>
|
||||
<a href="http://patras.fosscomm.gr/talks/BSoD_Pub.pdf">The Bright side of darknets</a>, FOSSCOMM Patras May 2011
|
||||
|
||||
|
||||
</li><li>
|
||||
<li>
|
||||
Privacy-Implications of Performance-Based Peer Selection by Onion-Routers: A Real-World Case Study using I2P,
|
||||
Michael Hermann.
|
||||
Master's Thesis, TU-Munich, March 28, 2011.
|
||||
@ -177,65 +68,234 @@ Master's Thesis, TU-Munich, March 28, 2011.
|
||||
Michael Hermann, Christian Grothoff.
|
||||
Presented at PET Symposium, Waterloo Canada, July 27, 2011.
|
||||
<a href="http://grothoff.org/christian/teaching/2011/2194/i2p.odp">presentation slides (odp)</a>
|
||||
</li>
|
||||
|
||||
</li><li>
|
||||
<a href="http://www.youtube.com/watch?v=bI_1qlcwfE0">Common Darknet Weaknesses</a>
|
||||
(Youtube Video)
|
||||
Adrian Crenshaw, <a href="http://aide.marshall.edu/">AIDE</a>, July 11-15, 2011.
|
||||
|
||||
</li><li>
|
||||
<a href="http://www.youtube.com/watch?v=NV90TRs_pGE">Short garlic routing animation</a>
|
||||
(Youtube Video)
|
||||
Adrian Crenshaw.
|
||||
|
||||
</li><li>
|
||||
<a href="http://www.irongeek.com/i.php?page=security/i2p-tor-workshop-notes">I2P / Tor Workshop Notes</a>
|
||||
Adrian Crenshaw. DEF CON 19, Las Vegas, August 6, 2011.
|
||||
|
||||
</li><li>
|
||||
<a href="http://www.youtube.com/watch?v=xxKXkbohRZM">Cipherspaces/Darknets: An Overview Of Attack Strategies -
|
||||
DEF CON Live version (Youtube Video)</a>,
|
||||
<a href="http://www.youtube.com/watch?v=xFxJ6Dc5ass">"Studio" version (Youtube Video)</a>,
|
||||
<a href="http://www.irongeek.com/downloads/Adrian-Crenshaw-darknet-weaknesses.pptx">Slides (ppt)</a>
|
||||
Adrian Crenshaw. DEF CON 19, Las Vegas, August 7, 2011.
|
||||
|
||||
</li><li>
|
||||
<a href="http://www.isdpodcast.com/podcasts/infosec-daily-podcast-episode-454.mp3">zzz interviewed on the InfoSec Daily Podcast Ep. 454 (mp3)</a>
|
||||
August 18, 2011
|
||||
|
||||
</li><li>
|
||||
<li>
|
||||
<a href="http://hal.inria.fr/inria-00632259/en/">Monitoring the I2P Network</a>,
|
||||
Juan Pablo Timpanaro, Isabelle Chrisment, Olivier Festor,
|
||||
INRIA Nancy-Grand Est, France,
|
||||
LORIA - ESIAL, Henri Poincare University, Nancy 1, France.
|
||||
October 2011.
|
||||
</li>
|
||||
|
||||
</li><li>
|
||||
<a href="http://0x375.org/">Modern cipherspace ecosystems</a>, 0x375 0x06 4/11/2011
|
||||
|
||||
</li><li>
|
||||
<li>
|
||||
<a href="http://userpage.fu-berlin.de/~semu/docs/2011_seminar_ehlert_i2p.pdf">I2P Usability vs. Tor Usability A Bandwidth and Latency Comparison</a>
|
||||
Mathias Ehlert,
|
||||
Humboldt University of Berlin,
|
||||
November 2011.
|
||||
<a href="http://translated.by/you/i2p-usability-vs-tor-usability-a-bandwidth-and-latency-comparison/into-ru/">Russian translation</a>
|
||||
</li>
|
||||
|
||||
</li><li>
|
||||
<a href="http://how-to.linuxcareer.com/i2p-anonymity-for-the-masses">I2P - Anonymity for the Masses</a>,
|
||||
Jonathan Cox,
|
||||
November 11, 2011.
|
||||
|
||||
</li><li>
|
||||
<a href="http://www.isdpodcast.com/podcasts/infosec-daily-podcast-episode-596.mp3">zzz and Lance James interviewed on the InfoSec Daily Podcast Ep. 596 (mp3)</a>
|
||||
February 16, 2012
|
||||
|
||||
</li><li>
|
||||
<li>
|
||||
<a href="http://hal.inria.fr/hal-00744922/">Improving Content Availability in the I2P Anonymous File-Sharing Environment</a>
|
||||
Juan Pablo Timpanaro, Isabelle Chrisment, Olivier Festor,
|
||||
INRIA Nancy-Grand Est, France,
|
||||
LORIA - ESIAL, Universite de Lorraine
|
||||
October 2012.
|
||||
|
||||
</li>
|
||||
</ul></div>
|
||||
|
||||
<li>
|
||||
<a href="http://hal.inria.fr/hal-00744919">A Bird's Eye View on the I2P Anonymous File-sharing Environment</a>
|
||||
Juan Pablo Timpanaro, Isabelle Chrisment, Olivier Festor,
|
||||
INRIA Nancy-Grand Est, France,
|
||||
LORIA - ESIAL, Universite de Lorraine
|
||||
November 2012.
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<h2>Presentations</h2>
|
||||
<ul>
|
||||
|
||||
<li>
|
||||
IIP Presentation at CodeCon
|
||||
<a href="http://invisibleip.sourceforge.net/iip/resources/codecon_0x90.mp3">MP3 audio</a>
|
||||
<a href="http://invisibleip.sourceforge.net/iip/resources/iip_transcript.txt">transcript</a>
|
||||
Lance James (0x90), February 2002.
|
||||
</li>
|
||||
|
||||
<li>
|
||||
IIP Presentation at ToorCon
|
||||
<a href="http://invisibleip.sourceforge.net/iip/resources/toorconspeech.mp3">MP3 audio</a>
|
||||
<a href="http://invisibleip.sourceforge.net/iip/resources/toorconspeech/">slides</a>
|
||||
Lance James (0x90), September 2002.
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://www.youtube.com/watch?v=TsfdzfGZyu0">To Be or I2P</a>
|
||||
(Youtube Video)
|
||||
An introduction into anonymous communication with I2P.
|
||||
<a href="http://events.ccc.de/congress/2007/Fahrplan/attachments/1017_24c3-i2p.pdf">To Be or I2P (PDF presentation)</a>,
|
||||
Jens Kubieziel, 24C3 Berlin, December 28, 2007.
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://marge.informatik.tu-chemnitz.de/archiv/CLT2009/V4-Sa1200-Security-Lars_Schimmer.mp4">Video of I2P talk at Chemnitz Linux Tag</a>,
|
||||
Lars Schimmer,
|
||||
March 14-15, 2009
|
||||
</li>
|
||||
|
||||
<li>
|
||||
HOPE New York July 17, 2010 - Brief overview of I2P by zzz, at the end of Adrian Hong's talk
|
||||
"Hackers for Human Rights".
|
||||
<a href="http://c2047862.cdn.cloudfiles.rackspacecloud.com/tnhc21.mp3">MP3 audio</a>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://www.irongeek.com/i.php?page=videos/shmoocon-firetalks-2011">Into the I2P Darknet: Welcome to Cipherspace</a>
|
||||
Adrian Crenshaw. Schmoocon Firetalk, January 2011
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://www.youtube.com/watch?v=TexNr_5J5AU">Using techhnology to advance liberty</a>
|
||||
(Youtube Video)
|
||||
Eric Johnson.
|
||||
<a href="http://agora.io/etienne">Agora I/O Unconference</a>, March 27, 2011.
|
||||
I2P covered from 10:00 to 20:00 in the video.
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://patras.fosscomm.gr/talks/BSoD_Pub.pdf">The Bright side of darknets</a>, FOSSCOMM Patras May 2011
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://www.youtube.com/watch?v=bI_1qlcwfE0">Common Darknet Weaknesses</a>
|
||||
(Youtube Video)
|
||||
Adrian Crenshaw, <a href="http://aide.marshall.edu/">AIDE</a>, July 11-15, 2011.
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://www.irongeek.com/i.php?page=security/i2p-tor-workshop-notes">I2P / Tor Workshop Notes</a>
|
||||
Adrian Crenshaw. DEF CON 19, Las Vegas, August 6, 2011.
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://www.youtube.com/watch?v=xxKXkbohRZM">Cipherspaces/Darknets: An Overview Of Attack Strategies -
|
||||
DEF CON Live version (Youtube Video)</a>,
|
||||
<a href="http://www.youtube.com/watch?v=xFxJ6Dc5ass">"Studio" version (Youtube Video)</a>,
|
||||
<a href="http://www.irongeek.com/downloads/Adrian-Crenshaw-darknet-weaknesses.pptx">Slides (ppt)</a>
|
||||
Adrian Crenshaw. DEF CON 19, Las Vegas, August 7, 2011.
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://0x375.org/">Modern cipherspace ecosystems</a>, 0x375 0x06 4/11/2011
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
|
||||
<h2>Tutorials</h2>
|
||||
<ul>
|
||||
|
||||
<li>
|
||||
<a href="http://www.youtube.com/watch?v=5J3nh1DoRMw">I2P Windows Tutorial</a>
|
||||
(Youtube Video)
|
||||
This guide will show you how to install I2P in Windows XP.
|
||||
By <a href="http://telecomix.org/">Telecomix</a>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://www.youtube.com/watch?v=QeRN2G9VW5E">I2P Debian Tutorial</a>
|
||||
(Youtube Video)
|
||||
This will guide you through how to install I2P on a Debian Linux System.
|
||||
By <a href="http://telecomix.org/">Telecomix</a>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://www.youtube.com/watch?v=2ylW85vc7SA">How to set up anonymous site in I2P</a>
|
||||
(Youtube Video)
|
||||
How to set up an anonymous web site in I2P.
|
||||
By <a href="http://telecomix.org/">Telecomix</a>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://www.youtube.com/watch?v=d8mvGZqVgE4">I2P Tutorial Mac OS X</a>
|
||||
(Youtube Video)
|
||||
A tutorial on how to run i2p on Mac OS X and how to connect to irc.telecomix.i2p.
|
||||
By <a href="http://telecomix.org/">Telecomix</a>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://www.youtube.com/watch?v=5jv7tVVJdTQ">Felix Atari explains the basic principles of I2P</a>
|
||||
(Youtube Video)
|
||||
Agent Felix Atari of the Telecomix Crypto Munitions Bureau.
|
||||
By <a href="http://telecomix.org/">Telecomix</a>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://www.youtube.com/watch?v=WyN_QK-_3GA">How to get onto I2P, the anonymous P2P Darknet (Windows Install)</a>
|
||||
(Youtube Video)
|
||||
This tutorial shows how to install and configure software needed to access I2P.
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://www.youtube.com/watch?v=q4owyd_CaGc">How to connect to I2P</a>
|
||||
(Youtube Video)
|
||||
How to install I2P on Ubuntu.
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://www.irongeek.com/i.php?page=videos/i2p-darknet-software-in-linux">Installing the I2P darknet software in Linux</a>
|
||||
(Video)
|
||||
Adrian Crenshaw.
|
||||
January 2011
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://www.youtube.com/watch?v=NV90TRs_pGE">Short garlic routing animation</a>
|
||||
(Youtube Video)
|
||||
Adrian Crenshaw.
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
|
||||
<h2>Articles and Interviews</h2>
|
||||
<ul>
|
||||
|
||||
<li>
|
||||
0x90 Interviewed by DistributedCity
|
||||
<a href="http://invisibleip.sourceforge.net/iip/mediaDCInterview1.php">Part 1</a>
|
||||
<a href="http://invisibleip.sourceforge.net/iip/mediaDCInterview2.php">Part 2</a>
|
||||
July 26, 2002.
|
||||
</li>
|
||||
|
||||
<li>
|
||||
0x90 Interviewed by El Pais
|
||||
(original in Spanish)
|
||||
<a href="http://invisibleip.sourceforge.net/iip/resources/elpais-iip.txt">English translation</a>
|
||||
October 31, 2002.
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://www.businessweek.com/magazine/content/03_37/b3849089_mz063.htm">2003 Business Week article referencing invisiblenet</a>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://www.netzwelt.de/news/75371-i2p-das-anonyme-netz-im.html">Netzwelt.de article about being anonymous in the Internet</a>
|
||||
(German)
|
||||
November 2007.
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://www.gulli.com/news/i2p-an-anonymous-network-2009-03-09/">zzz interviewed by gulli.com</a>
|
||||
March 2009
|
||||
<a href="http://www.gulli.com/news/i2p-anonymes-netzwerk-im-2009-03-09/">German translation</a>
|
||||
<a href="http://translated.by/you/i2p-an-anonymous-network-interrogated/into-ru/">Russian translation</a>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://www.isdpodcast.com/podcasts/infosec-daily-podcast-episode-454.mp3">zzz interviewed on the InfoSec Daily Podcast Ep. 454 (mp3)</a>
|
||||
August 18, 2011
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://how-to.linuxcareer.com/i2p-anonymity-for-the-masses">I2P - Anonymity for the Masses</a>,
|
||||
Jonathan Cox,
|
||||
November 11, 2011.
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<a href="http://www.isdpodcast.com/podcasts/infosec-daily-podcast-episode-596.mp3">zzz and Lance James interviewed on the InfoSec Daily Podcast Ep. 596 (mp3)</a>
|
||||
February 16, 2012
|
||||
</li>
|
||||
|
||||
</div>
|
||||
{% endblock %}
|
||||
|
||||
@ -5,7 +5,7 @@ See the
|
||||
<a href="http://www.monotone.ca/">Monotone website</a> for information
|
||||
on monotone.
|
||||
See
|
||||
<a href="http://forum.i2p2.de/viewtopic.php?t=2524">this forum post on i2p monotone</a>
|
||||
<a href="http://forum.i2p/viewtopic.php?t=2524">this forum post on i2p monotone</a>
|
||||
for more information on how to get started and check out the source anonymously.
|
||||
There is also a quick-start guide on the
|
||||
<a href="newdevelopers.html">new developer's page</a>.
|
||||
|
||||
@ -217,7 +217,7 @@ Un tableau de compatibilité actuelle des trackers est également
|
||||
<a href="http://zzz.i2p/files/trackers.html">disponible ici</a>.
|
||||
</li>
|
||||
<li>
|
||||
La <a href="http://forum.i2p2.de/viewtopic.php?t=2068">FAQ bittorrent I2P</a>
|
||||
La <a href="http://forum.i2p/viewtopic.php?t=2068">FAQ bittorrent I2P</a>
|
||||
</li>
|
||||
<li>
|
||||
<a href="http://zzz.i2p/topics/812">Discussion de DHT sur I2P</a>
|
||||
|
||||
@ -91,7 +91,7 @@
|
||||
<td><p>$0.0 USD</p></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><p><b><a href="http://forum.i2p2.de/viewtopic.php?t=1136">Bundling bounties</a></b></p></td>
|
||||
<td><p><b><a href="http://forum.i2p/viewtopic.php?t=1136">Bundling bounties</a></b></p></td>
|
||||
<td><p>Proposed</p></td>
|
||||
<td><p>jrandom</p></td>
|
||||
<td><p>[فارغة]</p></td>
|
||||
@ -105,7 +105,7 @@
|
||||
<tr><td><p><b>الاسم</b></p></td><td><p><b>الحالة</b></p></td><td><p><b>فريق التطوير<sup>*</sup></b></p></td></tr>
|
||||
<tr>
|
||||
<td><p><b><a href="bounty_datastore">حفظ البيانات فوق I2P</a></b></p></td>
|
||||
<td><p><a href="http://duck.i2p/tahoe-lafs/">مستعمل</a> for 700 €</p></td>
|
||||
<td><p><a href="http://killyourtv.i2p/tahoe-lafs/install/">مستعمل</a> for 700 €</p></td>
|
||||
<td><p>duck, smeghead</p></td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -115,12 +115,12 @@
|
||||
</tr>
|
||||
<tr>
|
||||
<td><p><b>Swarming file transfer</b></p></td>
|
||||
<td><p><a href="http://duck.i2p/i2p-bt/">مستعمل</a> for €250 EUR</p></td>
|
||||
<td><p><a href="http://i2p-bt.postman.i2p">مستعمل</a> for €250 EUR</p></td>
|
||||
<td><p>duck, ragnarok, dinoman, connelly, drwoo</p></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><p><b>Streaming library window size</b></p></td>
|
||||
<td><p><a href="http://dev.i2p.net/pipermail/i2p/2004-November/000491.html">مستعمل</a></p></td>
|
||||
<td><p><a href="http://web.archive.org/web/20070404110818/http://dev.i2p.net/pipermail/i2p/2004-November/000491.html">مستعمل</a></p></td>
|
||||
<td><p>jrandom</p></td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -135,7 +135,7 @@
|
||||
</tr>
|
||||
<tr>
|
||||
<td><p><b><a href="http://gcc.gnu.org/java/">GCJ</a> دعم</b></p></td>
|
||||
<td><p><a href="http://dev.i2p.net/cgi-bin/cvsweb.cgi/i2p/Makefile.gcj">مستعمل</a></p></td>
|
||||
<td><p><a href="https://trac.i2p2.de/browser/Makefile.gcj">مستعمل</a></p></td>
|
||||
<td><p>jrandom</p></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
@ -84,7 +84,7 @@ etc.) benutzt wird.</p>
|
||||
<table border="1">
|
||||
<tr><td><p><b>Name</b></p></td><td><p><b>Status</b></p></td><td><p><b>Richter</b></p></td><td><p><b>Entwickler <sup>*</sup></b></p></td><td><p><b>Bounty</b></p></td></tr>
|
||||
<tr>
|
||||
<td><p><b><a href="http://forum.i2p2.de/viewtopic.php?t=1136">zusammenlegen von Programmen</a></b></p></td>
|
||||
<td><p><b><a href="http://forum.i2p/viewtopic.php?t=1136">zusammenlegen von Programmen</a></b></p></td>
|
||||
<td><p>Vorgeschlagen</p></td>
|
||||
<td><p>jrandom</p></td>
|
||||
<td><p>[vacant]</p></td>
|
||||
@ -108,7 +108,7 @@ etc.) benutzt wird.</p>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><p><b><a href="bounty_datastore_de">Datencontainer im I2P</a></b></p></td>
|
||||
<td><p><a href="http://duck.i2p/tahoe-lafs/">Ausgezahlt</a> mit €700 EUR</p></td>
|
||||
<td><p><a href="http://killyourtv.i2p/tahoe-lafs/">Ausgezahlt</a> mit €700 EUR</p></td>
|
||||
<td><p>duck,smeghead</p></td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -118,12 +118,12 @@ etc.) benutzt wird.</p>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><p><b>Verteilter Datei Transfer</b></p></td>
|
||||
<td><p><a href="http://duck.i2p/i2p-bt/">Ausgezahlt</a> mit €250 EUR</p></td>
|
||||
<td><p><a href="http://i2p-bt.postman.i2p">Ausgezahlt</a> mit €250 EUR</p></td>
|
||||
<td><p>duck, ragnarok, dinoman, connelly, drwoo</p></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><p><b>Streaming Bibliothek Fenstergrösse</b></p></td>
|
||||
<td><p><a href="http://dev.i2p.net/pipermail/i2p/2004-November/000491.html">Bezahlt</a></p></td>
|
||||
<td><p><a href="http://web.archive.org/web/20070404110818/http://dev.i2p.net/pipermail/i2p/2004-November/000491.html">Bezahlt</a></p></td>
|
||||
<td><p>jrandom</p></td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -138,7 +138,7 @@ etc.) benutzt wird.</p>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><p><b><a href="http://gcc.gnu.org/java/">GCJ</a> support</b></p></td>
|
||||
<td><p><a href="http://dev.i2p.net/cgi-bin/cvsweb.cgi/i2p/Makefile.gcj">Ausgezahlt</a></p></td>
|
||||
<td><p><a href="https://trac.i2p2.de/browser/Makefile.gcj">Ausgezahlt</a></p></td>
|
||||
<td><p>jrandom</p></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
@ -72,7 +72,7 @@ etc e simili.</p>
|
||||
<td><p>$0.0 USD</p></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><p><b><a href="http://forum.i2p2.de/viewtopic.php?t=1136">Bundling bounties</a></b></p></td>
|
||||
<td><p><b><a href="http://forum.i2p/viewtopic.php?t=1136">Bundling bounties</a></b></p></td>
|
||||
<td><p>Proposed</p></td>
|
||||
<td><p>jrandom</p></td>
|
||||
<td><p>[vacant]</p></td>
|
||||
@ -85,7 +85,7 @@ etc e simili.</p>
|
||||
<tr><td><p><b>Name</b></p></td><td><p><b>Status</b></p></td><td><p><b>Dev team<sup>*</sup></b></p></td></tr>
|
||||
<tr>
|
||||
<td><p><b><a href="bounty_datastore">Datastore over I2P</a></b></p></td>
|
||||
<td><p><a href="http://duck.i2p/tahoe-lafs/">CLAIMED</a> for 700 €</p></td>
|
||||
<td><p><a href="http://killyourtv.i2p/tahoe-lafs/install/">CLAIMED</a> for 700 €</p></td>
|
||||
<td><p>duck, smeghead</p></td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -95,12 +95,12 @@ etc e simili.</p>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><p><b>Swarming file transfer</b></p></td>
|
||||
<td><p><a href="http://duck.i2p/i2p-bt/">CLAIMED</a> for €250 EUR</p></td>
|
||||
<td><p><a href="http://i2p-bt.postman.i2p">CLAIMED</a> for €250 EUR</p></td>
|
||||
<td><p>duck, ragnarok, dinoman, connelly, drwoo</p></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><p><b>Streaming library window size</b></p></td>
|
||||
<td><p><a href="http://dev.i2p.net/pipermail/i2p/2004-November/000491.html">Claimed</a></p></td>
|
||||
<td><p><a href="http://web.archive.org/web/20070404110818/http://dev.i2p.net/pipermail/i2p/2004-November/000491.html">Claimed</a></p></td>
|
||||
<td><p>jrandom</p></td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -115,7 +115,7 @@ etc e simili.</p>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><p><b><a href="http://gcc.gnu.org/java/">GCJ</a> support</b></p></td>
|
||||
<td><p><a href="http://dev.i2p.net/cgi-bin/cvsweb.cgi/i2p/Makefile.gcj">Claimed</a></p></td>
|
||||
<td><p><a href="https://trac.i2p2.de/browser/Makefile.gcj">Claimed</a></p></td>
|
||||
<td><p>jrandom</p></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
@ -61,7 +61,7 @@
|
||||
<td><p>$0.0 USD</p></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><p><b><a href="http://forum.i2p2.de/viewtopic.php?t=1136">Кроссплатформенные I2P-комплекты</a></b></p></td>
|
||||
<td><p><b><a href="http://forum.i2p/viewtopic.php?t=1136">Кроссплатформенные I2P-комплекты</a></b></p></td>
|
||||
<td><p>Предложено</p></td>
|
||||
<td><p>jrandom</p></td>
|
||||
<td><p>[vacant]</p></td>
|
||||
@ -74,7 +74,7 @@
|
||||
<tr><td><p><b>Название</b></p></td><td><p><b>Статус</b></p></td><td><p><b>Разработчики<sup>*</sup></b></p></td></tr>
|
||||
<tr>
|
||||
<td><p><b><a href="bounty_datastore_ru">Децентрализованное хранилище данных поверх I2P</a></b></p></td>
|
||||
<td><p><a href="http://duck.i2p/tahoe-lafs/">Востребована</a>, €70 EUR</p></td>
|
||||
<td><p><a href="http://killyourtv.i2p/tahoe-lafs/install/">Востребована</a>, €70 EUR</p></td>
|
||||
<td><p>duck, smeghead</p></td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -84,12 +84,12 @@
|
||||
</tr>
|
||||
<tr>
|
||||
<td><p><b>Swarming file transfer</b></p></td>
|
||||
<td><p><a href="http://duck.i2p/i2p-bt/">Востребована</a>, €250 EUR</p></td>
|
||||
<td><p><a href="http://i2p-bt.postman.i2p">Востребована</a>, €250 EUR</p></td>
|
||||
<td><p>duck, ragnarok, dinoman, connelly, drwoo</p></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><p><b>Streaming library window size</b></p></td>
|
||||
<td><p><a href="http://dev.i2p.net/pipermail/i2p/2004-November/000491.html">Востребована</a></p></td>
|
||||
<td><p><a href="http://web.archive.org/web/20070404110818/http://dev.i2p.net/pipermail/i2p/2004-November/000491.html">Востребована</a></p></td>
|
||||
<td><p>jrandom</p></td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -104,7 +104,7 @@
|
||||
</tr>
|
||||
<tr>
|
||||
<td><p><b>Поддержка <a href="http://gcc.gnu.org/java/">GCJ</a></b></p></td>
|
||||
<td><p><a href="http://dev.i2p.net/cgi-bin/cvsweb.cgi/i2p/Makefile.gcj">Востребована</a></p></td>
|
||||
<td><p><a href="https://trac.i2p2.de/browser/Makefile.gcj">Востребована</a></p></td>
|
||||
<td><p>jrandom</p></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
@ -6,30 +6,8 @@
|
||||
</p><p>Following is a monotonerc file defining the current trust list.
|
||||
Developers must use this file in ~/.monotone/monotonerc or
|
||||
_MTN/montonerc in their i2p.i2p workspace.
|
||||
<pre>
|
||||
function intersection(a,b)
|
||||
local s={}
|
||||
local t={}
|
||||
for k,v in pairs(a) do s[v.name] = 1 end
|
||||
for k,v in pairs(b) do if s[v] ~= nil then table.insert(t,v) end end
|
||||
return t
|
||||
end
|
||||
|
||||
function get_revision_cert_trust(signers, id, name, val)
|
||||
local trusted_signers = { "complication@mail.i2p", "zzz@mail.i2p", "dev@welterde.de",
|
||||
"Oldaris@mail.i2p", "sponge@mail.i2p", "dream@mail.i2p", "mathiasdm@mail.i2p",
|
||||
"mkvore-commit@mail.i2p", "z3d@mail.i2p", "cervantes@mail.i2p", "BlubMail@mail.i2p",
|
||||
"walking@mail.i2p", "neutron@mail.i2p", "HungryHobo@mail.i2p", "russiansponsor@mail.i2p",
|
||||
"echelon@mail.i2p", "forget@mail.i2p", "privateer@mail.i2p", "duck@mail.i2p",
|
||||
"m1xxy@mail.i2p", "hiddenz@mail.i2p", "dev@robertfoss.se", "hamada@mail.i2p",
|
||||
"magma@mail.i2p", "kytv@mail.i2p", "str4d@mail.i2p", "meeh@mail.i2p" }
|
||||
local t = intersection(signers, trusted_signers)
|
||||
if t == nil then return false end
|
||||
if table.getn(t) >= 1 then return true end
|
||||
return false
|
||||
end
|
||||
</pre>
|
||||
|
||||
{% include "_monotonerc.html" %}
|
||||
|
||||
</p><p>Agreements:
|
||||
<pre>
|
||||
@ -700,6 +678,48 @@ R2VFZ/114yCNY74KmujA
|
||||
=jfFH
|
||||
-----END PGP SIGNATURE-----
|
||||
|
||||
zab:
|
||||
|
||||
-----BEGIN PGP SIGNED MESSAGE-----
|
||||
Hash: SHA1
|
||||
|
||||
I declare that:
|
||||
|
||||
Unless marked otherwise, all code I commit is implicitly licensed
|
||||
under the component's primary license
|
||||
If specified in the source, the code may be explicitly licensed under
|
||||
one of the component's alternate licenses
|
||||
I have the right to release the code I commit under the terms I am
|
||||
committing it
|
||||
|
||||
zab (topiltzin on irc)
|
||||
|
||||
[pubkey zab@mail.i2p]
|
||||
MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC0H8bP/f8v7KjnyGlZGWQsF5G3ppvJ1Kwt/dUGi7gHbclKPnFAWXmb7YWOhl9Ua2USjQ4YrIeB7/2uVOpe+3FrFgUzIiWsx6I2yiNI3TscDvQsa5wG0Z2G4BbHXjONyiUzzO+j2TWPs3x35r2LCy8plRzPAswCF1GaIEjJCce5zwIDAQAB
|
||||
[end]
|
||||
[pubkey zab-transport@mail.i2p]
|
||||
MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDLI/VD0KtrPPaCSQPHse4p53ze5yi/0CePfbh1YXTJieUzCGpD76IjlpRB8sRYIevWGglOjac6fhAA97VMlSmZHIxtBw3U4Y7kTkdZcsgkKTa756ge5UeURVmBaUZevb8DDRREUQ3ELt6bit9iQhOvsAeUNiB1IVmRRBXrYIQhSQIDAQAB
|
||||
[end]
|
||||
-----BEGIN PGP SIGNATURE-----
|
||||
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
|
||||
Comment: GPGTools - http://gpgtools.org
|
||||
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
|
||||
|
||||
iQIcBAEBAgAGBQJQmQeOAAoJEJkeLHPsdqhZgOUQAIRzuQZ3yF1r+P0iO390r+qy
|
||||
RxU0gQiPJDqDixDn0u8EAb2ljRWHTBfy792hs0nUu2//fNCh6chd7tbmJQn02Rm9
|
||||
nDICr2Lex6a9j498yWnkh0ZHq9yd1CPGT8xo3DW/KzLmqj+8xNUmx9RI3Y32wL9h
|
||||
H/O0VsGN0FhYeLU0vBlNkb+Vs9e0wY3/qCVMo1ldjVPahz6bblYXKVxfRhCThdfS
|
||||
ufUH2wqaDUozKabCeuM0xlll3PuaL2cATjUJuVWvO4Lahf6EZZBUvEgiW95wAL3q
|
||||
dFxZw9hUmFC4p30p0N+fQND/7aGfwujQO++S3D8gizqzSovaFpXxNzoQ6hSUWjI0
|
||||
+KsvbJXu0IguUen2p/Ka8EB0yWokYjIUH4V2kLt9jVJLuoSkejnTrFQuPIR1Qmcr
|
||||
31wqWJMWWbbFBR7KrPaDnBnRej5aIyZnHIyTtgUKhO+paDGQ0IYDirgXP10MtouY
|
||||
4Hl5v2OwhOwv/mPOm74EwJknFPhQThgxO8zG9sTHq5Lteb5SwaPLdZi7CruVU66p
|
||||
uCol/dZqVwrb2iVD19S4MvNQiOVQEWFKeBrxxBkT+qcGIWLMsG/o1qu0+VHpWQmo
|
||||
G4Adgew+7tIkak/71ss1pvUi05WsPP9KyzXrwqcFyoAmMFPtgxUIVYVc1kwYb5h3
|
||||
G58Br6HXTQLV8xAN1ml8
|
||||
=4989
|
||||
-----END PGP SIGNATURE-----
|
||||
|
||||
|
||||
</pre>
|
||||
{% endblock %}
|
||||
|
||||
@ -7,6 +7,9 @@ If you have somthing to discuss, please find the developers on IRC in #i2p-dev.
|
||||
See also <a href="statusnotes.html">the old weekly status notes</a>.
|
||||
</p><div class="underline"></div>
|
||||
<ul class="infolist">
|
||||
<li><a href="meeting210">Meeting 210</a> - November 27, 2012</li>
|
||||
<li><a href="meeting209">Meeting 209</a> - November 20, 2012</li>
|
||||
<li><a href="meeting208">Meeting 208</a> - September 8, 2010</li>
|
||||
<li><a href="meeting207">Meeting 207</a> - February 10, 2009</li>
|
||||
<li><a href="meeting206">Meeting 206</a> - April 10, 2007</li>
|
||||
<li><a href="meeting205">Meeting 205</a> - April 3, 2007</li>
|
||||
|
||||
@ -9,6 +9,8 @@ et #i2p-fr pour les discutions en français.
|
||||
Vous pouvez aussi consulter les notes des <a href="statusnotes.html">anciennes réunions hebdomadaires</a>.
|
||||
</p><div class="underline"></div>
|
||||
<ul class="infolist">
|
||||
<li><a href="meeting210">Meeting 210</a> - 27 novembre 2012</li>
|
||||
<li><a href="meeting209">Meeting 209</a> - 20 novembre 2012</li>
|
||||
<li><a href="meeting208">Rencontre 208</a> - 8 septembre 2010</li>
|
||||
<li><a href="meeting207">Rencontre 207</a> - 10 février 2009</li>
|
||||
<li><a href="meeting206">Rencontre 206</a> - 10 avril 2007</li>
|
||||
|
||||
Reference in New Issue
Block a user