merge of '387adb565814aa1d31385605b099239d2cecdbc4'
and '90e9ef1d0273dbc956caccfe46d907a27c28ca46'
This commit is contained in:
178
i2p2www/meetings/logs/269.log
Normal file
178
i2p2www/meetings/logs/269.log
Normal file
@ -0,0 +1,178 @@
|
||||
20:00:01 <zzz> 0) Hi
|
||||
20:00:01 <zzz> 1) 0.9.34 update (zzz)
|
||||
20:00:01 <zzz> 2) 0.9.34 blocker tickets (str4d)
|
||||
20:00:01 <zzz> 3) 0.9.34 Android/Maven build and release roles and schedule (str4d/meeh)
|
||||
20:00:01 <zzz> 4) Proposed removal of open4you.i2p and git.repo.i2p from console home page (anonymousmaybe)
|
||||
20:00:01 <zzz> 5) 0.9.35 plan (zzz)
|
||||
20:00:01 <zzz> 6) NTCP2 plan (zzz)
|
||||
20:00:01 <zzz> 7) Status scrum (zab)
|
||||
20:00:05 <zzz> 0) Hi
|
||||
20:00:07 <zzz> Hi
|
||||
20:00:30 <zzz> welcome to meeting 269, spanning almost 16 years
|
||||
20:00:33 <manas> Hey
|
||||
20:00:43 <zlatinb> hi
|
||||
20:00:44 <zzz> 1) 0.9.34 update (zzz)
|
||||
20:00:55 <zzz> ok, translation and checkin deadline is in 3 days
|
||||
20:01:20 <zzz> not much for recent bug reports
|
||||
20:01:36 <zzz> so we are looking good, pending item 2)
|
||||
20:01:56 <zzz> I've been working on .35 and beyond the last couple of weeks
|
||||
20:02:04 <zzz> anything else on 1) ?
|
||||
20:03:00 <zzz> 2) 0.9.34 blocker tickets (str4d)
|
||||
20:03:25 <i2pr> [Slack/str4d] Hi :B
|
||||
20:03:32 <zzz> str4d has several blocker tickets dating back several months, and have been pushed past a couple of releases already
|
||||
20:03:38 <manas> hey there str4d
|
||||
20:03:38 <zzz> str4d, what's your plan for these?
|
||||
20:04:10 <i2pr> [Slack/str4d] I see two blocker tickets.
|
||||
20:04:19 <i2pr> [Slack/str4d] One is reseeding on older Androids
|
||||
20:04:39 <zzz> ok good, 2 is better than 'several'
|
||||
20:04:45 <i2pr> [Slack/str4d] For that one, we narrowed down the problem window, but could not at the time identify a fix (the one we tried didn't work)
|
||||
20:05:07 <i2pr> [Slack/str4d] I do not have time at the moment to work on it, and the older versions are slowly becoming less-used
|
||||
20:05:24 <i2pr> [Slack/str4d] So I'm thinking that we should just deprecate the older Android versions
|
||||
20:05:59 <i2pr> [Slack/str4d] Note that Google Play Store has put in requirements that new app uploads start conforming to newer APIs, so we may in that sense have our hand forced if we want to continue to push through GPlay
|
||||
20:07:02 <zzz> and the other one?
|
||||
20:07:16 <i2pr> [Slack/str4d] Dropping support for older APIs should be relatively simple to do as part of the next update, if we agree on it.
|
||||
20:08:03 <i2pr> [Slack/str4d] The other is translated string fixes from 0.9.31 (in OP says "minor, but classing as a blocker")
|
||||
20:09:19 <i2pr> [Slack/str4d] Some of this I have fixed locally, but have not had time to extract and push out.
|
||||
20:09:41 <zzz> I guess the question is whether you intend to do any UI bug fixes at all. Last fix we saw from you was 5 months ago. I highlighted about 10 tickets a month ago I wanted to see fixed for .34. Do you intend to do any UI work going forward or should we find a replacement?
|
||||
20:09:58 <i2pr> [Slack/str4d] Realistically, if left to me, it will keep slipping, as my priorities are elsewhere at present.
|
||||
20:10:39 <i2pr> [Slack/str4d] I do plan to push more of the UI patches, but I do not have time to make it a sufficiently-short timescale.
|
||||
20:11:05 <zzz> ok so we shouldn't expect any UI work, including even simple fixes, at all from you, either for .34 or later?
|
||||
20:11:31 <i2pr> [Slack/str4d] The problem is that the word "simple" is doing a lot of heavy lifting there :stuck_out_tongue:
|
||||
20:12:11 <i2pr> [Slack/str4d] For .34, correct, don't expect any UI work from me.
|
||||
20:12:15 <zzz> ok. I wish we knew this months ago. We've lost an awful lot of time. We'll start reassigning the work and looking for replacements.
|
||||
20:12:22 <zzz> anything else for 2) ?
|
||||
20:13:01 <i2pr> [Slack/str4d] I am happy to pass patchsets to others for extracting the "simple" fixes - maybe they will have better luck than I wrangling monotone+git
|
||||
20:13:23 <zzz> 3) 0.9.34 Android/Maven build and release roles and schedule (str4d/meeh)
|
||||
20:14:03 <zzz> I'd like to know if str4d and meeh have figured out who is doing what for the .34 maven/fdroid/android releases, so I know who to hold to account and when it's going to happen
|
||||
20:15:37 <i2pr> [Slack/str4d] Meeh has the signing keys for Android and FDroid
|
||||
20:15:51 <meeh> We can figure it out now. What do you think str4d , do you got time for it, or should I?
|
||||
20:16:16 <i2pr> [Slack/str4d] I'd be happy for you to do it with me in your ear :slightly_smiling_face:
|
||||
20:16:31 <i2pr> [Slack/str4d] (because I want to build out our release capabilities)
|
||||
20:16:47 <zzz> meeh that ok with you?
|
||||
20:17:00 <i2pr> [Slack/str4d] We can set up a time to pair on it.
|
||||
20:17:16 <meeh> Yea, we can do that. That's the best option so far, so you can get me up to date on how, and what to do
|
||||
20:17:29 <zzz> what about maven central?
|
||||
20:17:45 <i2pr> [Slack/str4d] I'm currently the only one with credentials for it.
|
||||
20:18:08 <meeh> Yea, I don't have maven access
|
||||
20:18:22 <i2pr> [Slack/str4d] There's a few hoops that need to be jumped through with Sonatype to change that
|
||||
20:18:29 <zzz> so are you doing it or giving meeh the privs? I need to know who is responsible and when it's going to happen
|
||||
20:18:39 <i2pr> [Slack/str4d] (vaguely recalling what I had to do in order to set it up in the first place)
|
||||
20:18:52 <i2pr> [Slack/str4d] I will do that for .34
|
||||
20:19:21 <i2pr> [Slack/str4d] (probably in the same pairing with meeh)
|
||||
20:19:57 <zzz> ok can I hold you two to a two-week deadline to get it all released? If I get mine cut by April 10, that would be April 24. ok?
|
||||
20:20:41 <i2pr> [Slack/str4d] Okay.
|
||||
20:20:51 <zzz> ok meeh?
|
||||
20:20:56 <i2pr> [Slack/str4d] I'm in Denver week of 9th, then back in UK following week
|
||||
20:21:09 <i2pr> [Slack/str4d] So whichever week works better timezone-wise for meeh
|
||||
20:21:11 <meeh> Yepp
|
||||
20:21:39 <zzz> ok. meeh you also owe me an ack that you checked the gplay crash report
|
||||
20:21:45 <zzz> anything else on 3) ?
|
||||
20:21:49 <meeh> I should be able to adjust to something that fits for str4d in that timeline
|
||||
20:22:27 <zzz> 4) Proposed removal of open4you.i2p and git.repo.i2p from console home page (anonymousmaybe)
|
||||
20:22:48 <zzz> ok anonymousmaybe reports that those two sites have been down for weeks or months and recommends that they be removed from the router console
|
||||
20:22:55 <zzz> any objections?
|
||||
20:23:28 <i2pr> [Slack/str4d] git.repo.i2p has been down for a while primarily because I have not had time to go in and get it running again.
|
||||
20:23:53 <zzz> so I don't hear you objecting :)
|
||||
20:23:55 <i2pr> [Slack/str4d] If it is desired that it be running again, I can make time to do that. But I would also not object to it being removed.
|
||||
20:24:06 <zzz> if not, I'll remove them both for .34
|
||||
20:24:31 <i2pr> [Slack/str4d] No objections from me on open4you.i2p
|
||||
20:24:33 <zzz> you may apply for reinclusion following our normal processes once it's up and stable
|
||||
20:25:00 <zzz> it's a terrible user experience to have dead links on our console home page, and we owe it to our users to keep them up or remove them
|
||||
20:25:06 <i2pr> [Slack/str4d] ACK (I followed that process the first time IIRC :D)
|
||||
20:25:15 <zzz> ok anything else on 4) ?
|
||||
20:25:54 <zzz> 5) 0.9.35 plan (zzz)
|
||||
20:26:11 <zzz> ok we had a roadmap meeting a week or two ago, and the roadmap on our website reflects the results
|
||||
20:26:22 <zzz> everything else has been pushed to 36/37
|
||||
20:26:35 <zzz> we've been hard at work on 35 features for a couple of weeks already
|
||||
20:26:55 <zzz> this is the way I want to work for every release, where the work is done in advance and then merged in early in the cycle
|
||||
20:27:13 <i2pr> [Slack/str4d] +1
|
||||
20:27:13 <zzz> the schedule is for a .35 release in mid-late June, standard 10-week cycle
|
||||
20:27:34 <manas> There will be a meeting similar to the last one prior to the .35 release?
|
||||
20:27:57 <zzz> yeah, I'd like to do a roadmap meeting for the next one a few weeks before each release
|
||||
20:28:06 <manas> ok sounds good
|
||||
20:28:20 <zzz> all the anything else on 5) ?
|
||||
20:28:35 <zzz> s/all the//
|
||||
20:29:08 <i2pr> [Slack/str4d] .35 roadmap looks reasonable to me
|
||||
20:29:24 <i2pr> [Slack/str4d] +1 on private testnet setup improvements :smile:
|
||||
20:30:01 <zzz> 6) NTCP2 plan (zzz)
|
||||
20:30:09 <manas> I had posted on the forums a little late but would like to have a meeting (or discuss at next meeting) to discuss specifics about the private test net
|
||||
20:30:30 <zzz> ok we've convened a team with reps from all 3 projects. We've had two meetings so far and have a new version of the proposal posted
|
||||
20:30:39 <meeh> manas I'll contact you in a day or so, done some work on the topic as well
|
||||
20:30:43 <zzz> we plan to meet once a week and put out a new draft after each meeting
|
||||
20:30:49 <manas> meeh: alright :)
|
||||
20:31:02 <zzz> the goal is to be done by the end of april and have test implementations by the end of may.
|
||||
20:31:19 <zzz> the next meeting is in #ntcp2 April 9, 4 PM UTC, all welcome.
|
||||
20:31:20 <i2pr> [Slack/str4d] Which proposal is being furthered?
|
||||
20:31:36 <zzz> the version that we posted yesterday.
|
||||
20:31:52 <zlatinb> it’s available on clearnet forum str4d
|
||||
20:32:16 <zzz> actually, it's on the website. proposal 111.
|
||||
20:32:56 <i2pr> [Slack/str4d] Okay, so it's the update I proposed
|
||||
20:33:06 <zzz> comments may be made on i2pforum.i2p, i2pforum.i2p, the trac ticket, the zzz.i2p thread, in #ntcp2, here, you can email me, anyway anybody wants to do it. Clearnet or not. We welcome participation from all.
|
||||
20:33:11 <i2pr> [Slack/str4d] I need to check whether what was pushed to the website matches what I've been working on locally
|
||||
20:33:46 <zzz> as I emailed you a week ago, we do not require a separate proposal from you.
|
||||
20:34:12 <zzz> 111 will be the proposal and we will update it each week after our meeting.\
|
||||
20:34:33 <i2pr> [Slack/str4d] I'll ping you after meeting.
|
||||
20:34:40 <zzz> anything else on 6) ?
|
||||
20:36:00 <zzz> 7) Status scrum (zab)
|
||||
20:36:04 <zzz> over to you zlatinb
|
||||
20:36:30 <zlatinb> Hi. Before we start the scrum, everyone who wants to get paid please fill out the timesheet/request form that zzz posted on his forum
|
||||
20:36:55 <zlatinb> and email the form to me
|
||||
20:36:58 <zlatinb> now off to scrum
|
||||
20:37:01 <zzz> ok I suggest we wait until at least the last week of the month, so people know how much they worked up until then?
|
||||
20:37:42 <i2pr> [Slack/str4d] I agree. My understanding was the quarter started in Feb
|
||||
20:37:43 <zlatinb> sure, but I would need a few days after I receive the form
|
||||
20:38:09 <manas> I believe the post said not before APR 23
|
||||
20:38:29 <zzz> On the post I said earliest to email is April 23 and latest is April 30. But you make the rules and I'll update it.
|
||||
20:38:49 <zlatinb> those dates are fine
|
||||
20:39:07 * zlatinb got caught for not having read the post ;-)
|
||||
20:39:17 <zlatinb> anyway :)
|
||||
20:39:50 <zlatinb> so scrum - we’ll go around the room, when your name is called pls post a short description of
|
||||
20:39:56 <zlatinb> 1) what you’ve been doing since last scrum
|
||||
20:40:02 <zlatinb> 2) what you plan to do next month
|
||||
20:40:21 <zlatinb> 3) are you blocked by anyone or do you need help on anything
|
||||
20:40:40 <zlatinb> pls do so even if you’ve been updating on the video chat, this is for posterity
|
||||
20:41:02 <zlatinb> so, zzz you go first
|
||||
20:41:35 <zzz> thanks zlatinb. In the last month I've done a lot of work on the .34 release, including lots of bug fixes and new features.
|
||||
20:42:13 <zzz> More recently, I have transitioned to 35 features and research, including susimail folders, and the new NTCP2 protocol
|
||||
20:42:53 <zzz> in the next month I plan to review the paper we received a month ago, continue work on NTCP2, get the 34 release out,
|
||||
20:43:05 <zzz> and fix bugs. 3) no blockers. EOT.
|
||||
20:43:18 <zlatinb> thanks
|
||||
20:43:26 <zlatinb> eche|off: are you here by any chance?
|
||||
20:43:39 <zzz> i think not
|
||||
20:43:40 <zlatinb> I know he said he wouldn’t be but just in case...
|
||||
20:44:03 <zlatinb> alright. Next full-timer- meeh, go
|
||||
20:44:22 <meeh> Highlights
|
||||
20:44:22 <meeh> I've soon done with an MVP for a new OSX launcher, improved outproxy service and tuning it for better performance. I've done some few scala tests, more to come. And I've setup test systems I need for both Android and OSX dev/test. Also used some time to get known with the codebases again. Also somewhat read me up on proposals.
|
||||
20:44:40 <meeh> Misc: Much I can't really recall at the moment.
|
||||
20:45:23 <meeh> For next round: Have the MVP for OSX ready. Mindblow you with a nice browser bundle. Focus more on scalatests, android and contribution documentation
|
||||
20:45:51 <meeh> Blockers; mja.. being more secure on dns changes as discussed on last video
|
||||
20:46:12 <zlatinb> yes indeed, I’ll have to get more serious chasing welt
|
||||
20:46:34 <zlatinb> anything else meeh ?
|
||||
20:46:51 <meeh> Cause once we can be sure of changes and when, I can deprecate some old services with fresh servers and software (cleanup, and such)
|
||||
20:46:59 <meeh> Improve my services for i2p
|
||||
20:47:04 <meeh> Done now :)
|
||||
20:47:19 <zlatinb> cool
|
||||
20:47:35 <zlatinb> manas: it must be very late where you are, good to see you, Your update pls?
|
||||
20:47:56 <manas> hey, everyone. good to see all again
|
||||
20:47:57 <manas> to summarize: I have studied up to chapter 4, which is on java syntax, of the book which I am using to study Java. will be continuing with chapter 5 this month, objects in java. have written some java code which was reviewed by zzz (thank you, zzz). will be continuing to study crypto as well. reading up on ant and gradle. thinking about the test net, planning on acquiring some hardware for
|
||||
20:47:58 <manas> this. continuing to maintain services which I run and staying on top of security disclosures. reading/responding to trac and forum posts regularly.
|
||||
20:48:19 <manas> meeh, if you have any writeups/documentation to share about running an outproxy I would be interested in reading it :)
|
||||
20:48:21 <manas> eot
|
||||
20:48:57 <zlatinb> good stuff - I want to talk about the outproxy business in light of OTF “soon”
|
||||
20:49:08 <meeh> Sure, we can talk about that later. Mainly it's a tunnel without anything in the domain field
|
||||
20:49:09 <zlatinb> but now back to scrum - str4d your tunr
|
||||
20:49:11 <zlatinb> turn
|
||||
20:49:18 <i2pr> [Slack/str4d] In the last month I worked on our current crypto specs, started the process for migrating proposals to the new forum, attended the Tor developer meeting in Rome (for Zcash, but had various I2P-relevant discussions), worked with Elio/Ura on website mockups, worked on Ire in preparation for NTCP2 draft implementation, and generally thought
|
||||
20:49:19 <i2pr> about NTCP2 crypto primitives.
|
||||
20:50:20 <i2pr> [Slack/str4d] In the next month I plan to check my email XD, pair w/ meeh on .34 Android/Maven, schedule into my calendar these meetings I seem to be missing, review the paper, start a draft implementation of NTCP2 in order to figure out some of the Noise library issues, and work on specifying the Elligator-esque ephemeral key blinding.
|
||||
20:50:50 <i2pr> [Slack/str4d] Only blocker is email-related, will ping people after about it.
|
||||
20:50:57 <i2pr> [Slack/str4d] EOT
|
||||
20:51:38 <zlatinb> i2pr: str4d ping ping
|
||||
20:52:35 <zlatinb> thanks
|
||||
20:52:46 <zlatinb> is sadie around on slack?
|
||||
20:53:40 <zlatinb> if not I think this is everyone / everything for 7)
|
||||
20:54:03 <zzz> ok, thanks zlatinb, anybody have anything else for the meeting?
|
||||
20:54:38 <i2pr> [Slack/str4d] I don't think she's here
|
||||
20:54:55 <meeh> no, just announcement that I will setup more resources for outproxy and improve it
|
||||
20:55:03 * zzz grabs the baffer
|
||||
20:56:00 * zzz *baffs* the meeting closed
|
||||
13
i2p2www/meetings/logs/269.rst
Normal file
13
i2p2www/meetings/logs/269.rst
Normal file
@ -0,0 +1,13 @@
|
||||
I2P dev meeting, April 3, 2018 @ 20:00 UTC
|
||||
==========================================
|
||||
|
||||
Quick recap
|
||||
-----------
|
||||
|
||||
* **Present:**
|
||||
|
||||
manas,
|
||||
meeh,
|
||||
str4d,
|
||||
zlatinb,
|
||||
zzz
|
||||
@ -8,7 +8,7 @@
|
||||
|
||||
{% set i2p_android_version = '0.9.33' %}
|
||||
{% set i2p_android_version_kytv = '0.9.22' %}
|
||||
{% set i2p_android_version_fdroid = '0.9.32' %}
|
||||
{% set i2p_android_version_fdroid = '0.9.33' %}
|
||||
|
||||
|
||||
{% macro package_outer(type, name, icon) -%}
|
||||
|
||||
@ -70,6 +70,22 @@ networks; Tor, JonDonym, and I2P.}},
|
||||
www_section = traffic,
|
||||
}
|
||||
|
||||
@article{bazli2017-the-dark-side-of-i2p,
|
||||
title = {The Dark side of I2P, a forensic analysis case study},
|
||||
author = {Bazli, Wilson and Hurst},
|
||||
journal = {System Science & Control Engeneering},
|
||||
year = {2017},
|
||||
month = June,
|
||||
volume = {2017},
|
||||
number = {5},
|
||||
pages = {278--286},
|
||||
doi = {10.1080/21642583.2017.1331770},
|
||||
url= {https://doi.org/10.1080/21642583.2017.1331770},
|
||||
www_section = traffic,
|
||||
}
|
||||
|
||||
|
||||
|
||||
@techreport{shahbar2017-measuring-anonymity-services,
|
||||
title = {Weighted Factors for Measuring Anonymity Services: A Case Study on Tor, JonDonym, and I2P},
|
||||
author = {Shahbar, Khalid and Zincir-Heywood, A. Nur},
|
||||
|
||||
@ -1,13 +1,13 @@
|
||||
{% extends "global/layout.html" %}
|
||||
{% block title %}{{ _('Hall Of Fame') }}{% endblock %}
|
||||
{% block content %}
|
||||
<!-- file version 2017.11.04.01 -->
|
||||
<b>{% trans date='2017-11-04' -%}
|
||||
<!-- file version 2018.03.25.01 -->
|
||||
<b>{% trans date='2018-03-25' -%}
|
||||
Current balance: as of {{ date }}
|
||||
{%- endtrans %}</b><br />
|
||||
<b>{{ _('General fund') }}:
|
||||
{% trans euroval='60124,69', btcval='471,62589208' %}{{ euroval }} € and {{ btcval }} BTC{% endtrans %}</b><br />
|
||||
{% trans bchval='473,8293343', xmzval='1356,4438549658' %}{{ bchval }} BCH; and {{ xmzval }} XMR{% endtrans %}</b><br />
|
||||
{% trans euroval='56081,34', btcval='482,59366632' %}{{ euroval }} € and {{ btcval }} BTC{% endtrans %}</b><br />
|
||||
{% trans bchval='323,8293343', xmrval='1156,4438549658' %}{{ bchval }} BCH; and {{ xmrval }} XMR{% endtrans %}</b><br />
|
||||
<b><a href="{{ site_url('get-involved/bounties/datastore') }}">{{ _('Datastorage bounty') }}</a>:
|
||||
{% trans euroval='145.0', btcval='2' %}{{ euroval }} € and {{ btcval }} BTC{% endtrans %}</b><br />
|
||||
<b><a href="{{ site_url('get-involved/bounties/i2phex') }}">{{ _('I2PHex bounty') }}</a>:
|
||||
@ -44,6 +44,40 @@ with your name or nick (and optionally homepage) so we can list you here.
|
||||
</table>
|
||||
<br />
|
||||
|
||||
<b>{{ _('2018 donations and costs:') }}</b><br />
|
||||
<table border="1">
|
||||
<tr><td>date</td><td>who</td><td>income</td><td>outgoing</td><td>account</td></tr>
|
||||
<tr><td>Jan, 2018</td><td>donation</td><td>10 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Jan, 2018</td><td>donation</td><td>5 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Jan, 2018</td><td>donation</td><td>10 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Jan, 2018</td><td>donation</td><td>10 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Jan, 2018</td><td>donation</td><td>10 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Jan, 2018</td><td>I2P root server</td><td></td><td>660 €</td><td>General fund</td></tr>
|
||||
<tr><td>Jan, 2018</td><td>34C3 support 2</td><td></td><td>880 €</td><td>General fund</td></tr>
|
||||
<tr><td>Jan, 20178/td><td>PayPal fees 2017/2</td><td></td><td>38,66 €</td><td>General fund</td></tr>
|
||||
<tr><td>Jan, 2018</td><td>sell XMR</td><td>3.45 BTC</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Jan, 2018</td><td>donation</td><td>0.0015 BTC</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Jan, 2018</td><td>sell XMR</td><td></td><td>200 XMR</td><td>general fund</td></tr>
|
||||
|
||||
<tr><td>Feb, 2018</td><td>donation</td><td>10 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Feb, 2018</td><td>donation</td><td>1 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Feb, 2018</td><td>donation</td><td>20 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Feb, 2018</td><td>donation</td><td>10 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Feb, 2018</td><td>donation</td><td>3,54 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Feb, 2018</td><td>donation</td><td>10 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Feb, 2018</td><td>Reseed server support</td><td></td><td>100 €</td><td>General fund</td></tr>
|
||||
<tr><td>Feb, 2018</td><td>I2P domains</td><td></td><td>128,40 €</td><td>General fund</td></tr>
|
||||
<tr><td>Feb, 2018</td><td>I2P domain 2</td><td></td><td>23,80 €</td><td>General fund</td></tr>
|
||||
<tr><td>Feb, 2018</td><td>donation</td><td>0.07990134 BTC</td><td></td><td>general fund</td></tr>
|
||||
|
||||
<tr><td>Mar, 2018</td><td>donation</td><td>10 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Mar, 2018</td><td>donation</td><td>10 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Mar, 2018</td><td>donation</td><td>10 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Mar, 2018</td><td>I2P dev team laptop</td><td></td><td>0.34444 BTC</td><td>general fund</td></tr>
|
||||
|
||||
</table>
|
||||
|
||||
|
||||
<b>{{ _('2017 donations and costs:') }}</b><br />
|
||||
<table border="1">
|
||||
<tr><td>date</td><td>who</td><td>income</td><td>outgoing</td><td>account</td></tr>
|
||||
@ -136,6 +170,33 @@ with your name or nick (and optionally homepage) so we can list you here.
|
||||
<tr><td>Oct, 2017</td><td>Loss of BTCe seizure</td><td></td><td>4.543200000 BTC</td><td>General fund</td></tr>
|
||||
|
||||
<tr><td>Nov, 2017</td><td>anonymous</td><td>10 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Nov, 2017</td><td>anonymous</td><td>20 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Nov, 2017</td><td>anonymous</td><td>10 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Nov, 2017</td><td>anonymous</td><td>10 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Nov, 2017</td><td>anonymous</td><td>10 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Nov, 2017</td><td>anonymous</td><td>10 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Nov, 2017</td><td>Donation stickers</td><td>0.00212000 BTC</td><td></td><td>General fund</td></tr>
|
||||
<tr><td>Nov, 2017</td><td>sell BCH</td><td>6.21000000 BTC</td><td></td><td>General fund</td></tr>
|
||||
<tr><td>Nov, 2017</td><td>sell BCH</td><td></td><td>150 BCH</td><td>General fund</td></tr>
|
||||
|
||||
<tr><td>Dec, 2017</td><td>anonymous</td><td>10 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Dec, 2017</td><td>anonymous</td><td>10 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Dec, 2017</td><td>anonymous</td><td>2 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Dec, 2017</td><td>anonymous</td><td>1 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Dec, 2017</td><td>anonymous</td><td>1 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Dec, 2017</td><td>anonymous</td><td>1 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Dec, 2017</td><td>anonymous</td><td>10 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Dec, 2017</td><td>anonymous</td><td>10 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Dec, 2017</td><td>Sell leftover 34C3 ticket</td><td>120 €</td><td></td><td>general fund</td></tr>
|
||||
<tr><td>Dec, 2017</td><td>34C3 tram tickets</td><td></td><td>133,60 €</td><td>General fund</td></tr>
|
||||
<tr><td>Dec, 2017</td><td>34C3 sweets</td><td></td><td>63,43 €</td><td>General fund</td></tr>
|
||||
<tr><td>Dec, 2017</td><td>34C3 travel support</td><td></td><td>1200 €</td><td>General fund</td></tr>
|
||||
<tr><td>Dec, 2017</td><td>34C3 misc expenses</td><td></td><td>560 €</td><td>General fund</td></tr>
|
||||
<tr><td>Dec, 2017</td><td>34C3 dev team support</td><td></td><td>600 €</td><td>General fund</td></tr>
|
||||
<tr><td>Dec, 2017</td><td>Donation</td><td>1.91869290</td><td></td><td>General fund</td></tr>
|
||||
<tr><td>Dec, 2017</td><td>Donation to TAILS</td><td></td><td>0.100000000 BTC</td><td>General fund</td></tr>
|
||||
<tr><td>Dec, 2017</td><td>34C3 support</td><td></td><td>0.100000000 BTC</td><td>General fund</td></tr>
|
||||
<tr><td>Dec, 2017</td><td>I2P dev team support</td><td></td><td>0.06000000 BTC</td><td>General fund</td></tr>
|
||||
|
||||
</table>
|
||||
|
||||
|
||||
@ -62,7 +62,7 @@ forward them towards a specific TCP/IP address.
|
||||
|
||||
<p>{% trans bittorrent='http://www.bittorrent.com/',
|
||||
freenet='https://freenetproject.org/',
|
||||
mnet='http://www.livejournal.com/',
|
||||
mnet='https://en.wikipedia.org/wiki/Mnet_%28Computer_program%29',
|
||||
livejournal='http://www.livejournal.com/' -%}
|
||||
I2PTunnel is currently used to let people run their own anonymous website
|
||||
("eepsite") by running a normal webserver and pointing an I2PTunnel 'server'
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
{% extends "global/layout.html" %}
|
||||
{% block title %}{{ _('I2P Project Members') }}{% endblock %}
|
||||
{% block lastupdated %}January 2016{% endblock %}
|
||||
{% block lastupdated %}March 2018{% endblock %}
|
||||
{% block content %}
|
||||
<p>{% trans volunteer=site_url('get-involved') -%}
|
||||
We are a small group of people spread around several continents, working to
|
||||
@ -32,18 +32,18 @@ network.
|
||||
<td valign="top"><i>{{ _('Public speaking, public relations assistance') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{{ _('Technical PR advisor') }}</b></td>
|
||||
<td valign="top">psi</td>
|
||||
<td valign="top"><b>{{ _('Assistant PR manager') }}</b></td>
|
||||
<td valign="top">eche|on</td>
|
||||
<td valign="top"><i>{{ _('Public relations assistance') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{% trans forum=i2pconv('forum.i2p') %}<a href="http://{{ forum }}/">Forum</a> admin{% endtrans %}</b></td>
|
||||
<td valign="top">cervantes</td>
|
||||
<td valign="top"><b>{% trans forum=i2pconv('i2pforum.i2p') %}<a href="http://{{ forum }}/">Forum</a> admin{% endtrans %}</b></td>
|
||||
<td valign="top">eche|on</td>
|
||||
<td valign="top"><i>{{ _('manage the public user forum') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{{ _('Download mirrors admin') }}</b></td>
|
||||
<td valign="top">welterde</td>
|
||||
<td valign="top">Meeh</td>
|
||||
<td valign="top"><i>{{ _('manage the mirrors for the download files') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -53,7 +53,7 @@ network.
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{% trans monotone=site_url('get-involved/guides/monotone') %}<a href="{{ monotone }}">Monotone</a> guru{% endtrans %}</b></td>
|
||||
<td valign="top">eche|on, kytv, Meeh</td>
|
||||
<td valign="top">eche|on</td>
|
||||
<td valign="top"><i>{{ _('manage the public monotone repositories') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -66,6 +66,11 @@ network.
|
||||
<td valign="top">zzz</td>
|
||||
<td valign="top"><i>{{ _('Windows installer packager') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{{ _('Packager; OSX') }}</b></td>
|
||||
<td valign="top">Meeh</td>
|
||||
<td valign="top"><i>{{ _('OSX installer packager') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{{ _('Release Manager') }}</b></td>
|
||||
<td valign="top">zzz</td>
|
||||
@ -73,7 +78,7 @@ network.
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{{ _('Release Manager Alternates') }}</b></td>
|
||||
<td valign="top">eche|on, kytv, str4d</td>
|
||||
<td valign="top">eche|on, str4d</td>
|
||||
<td valign="top"><i>{{ _('Backup release managers') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -83,14 +88,9 @@ network.
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{{ _('CI admin') }}</b></td>
|
||||
<td valign="top" class="blue">[{{ _('vacant') }}]</td>
|
||||
<td valign="top">Manas</td>
|
||||
<td valign="top"><i>{{ _('Maintain the Continuous Integration infrastructure') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{{ _('Update admin') }}</b></td>
|
||||
<td valign="top" class="blue">[{{ _('vacant') }}]</td>
|
||||
<td valign="top"><i>{{ _('Monitors and recruits in-network update hosts') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{{ _('Reseed admin') }}</b></td>
|
||||
<td valign="top">backup</td>
|
||||
@ -143,7 +143,7 @@ network.
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{{ _('Backup News Admin') }}</b></td>
|
||||
<td valign="top">psi</td>
|
||||
<td valign="top">str4d</td>
|
||||
<td valign="top"><i>{{ _('manage the backup news feed') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -168,7 +168,7 @@ network.
|
||||
</tr>
|
||||
<tr><td colspan="4"><hr /></td></tr>
|
||||
<tr>
|
||||
<td valign="top" rowspan="25"><b>{{ _('Dev') }}</b></td>
|
||||
<td valign="top" rowspan="17"><b>{{ _('Dev') }}</b></td>
|
||||
<td valign="top"><b>{{ _('Core Lead') }}</b></td>
|
||||
<td valign="top">zzz</td>
|
||||
<td valign="top"><i>{{ _('lead dev for the SDK and router') }}</i></td>
|
||||
@ -179,48 +179,28 @@ network.
|
||||
<td valign="top"><i>{{ _('organize and develop the i2p mail system') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{% trans i2host=i2pconv('i2host.i2p') %}<a href="http://{{ i2host }}/">I2Host</a> lead{% endtrans %}</b></td>
|
||||
<td valign="top" class="blue">[{{ _('vacant') }}]</td>
|
||||
<td valign="top"><i>{{ _('I2Host addressbook application') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{% trans bob=i2pconv('bob.i2p') %}<a href="http://{{ bob }}/">BOB</a> lead{% endtrans %}</b></td>
|
||||
<td valign="top" class="blue">[{{ _('vacant') }}]</td>
|
||||
<td valign="top"><i>{{ _('Basic Open Bridge') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{% trans bote=i2pconv('i2pbote.i2p') %}<a href="http://{{ bote }}/">I2P-Bote</a> lead{% endtrans %}</b></td>
|
||||
<td valign="top"><b>{% trans bote=i2pconv('bote.i2p') %}<a href="http://{{ bote }}/">I2P-Bote</a> lead{% endtrans %}</b></td>
|
||||
<td valign="top">str4d</td>
|
||||
<td valign="top"><i>{{ _('I2P-Bote plugin') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{% trans bob=i2pconv('bob.i2p') %}<a href="http://{{ bob }}/">Robert</a> lead{% endtrans %}</b></td>
|
||||
<td valign="top" class="blue">[{{ _('vacant') }}]</td>
|
||||
<td valign="top"><i>{{ _('Robert BitTorrent client') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{% trans forum=i2pconv('forum.i2p') %}<a href="http://{{ forum }}/viewforum?f=25">I2Phex</a> lead{% endtrans %}</b></td>
|
||||
<td valign="top"><b>{% trans forum=i2pconv('i2pforum.i2p') %}<a href="http://{{ forum }}/">I2Phex</a> lead{% endtrans %}</b></td>
|
||||
<td valign="top" class="blue">[{{ _('vacant') }}]</td>
|
||||
<td valign="top"><i>{{ _('I2Phex Gnutella client') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{% trans forum=i2pconv('forum.i2p') %}<a href="http://{{ forum }}/viewforum?f=21">I2PSnark</a> lead{% endtrans %}</b></td>
|
||||
<td valign="top"><b>{% trans forum=i2pconv('i2pforum.i2p') %}<a href="http://{{ forum }}/viewforum.php?f=12">I2PSnark</a> lead{% endtrans %}</b></td>
|
||||
<td valign="top">zzz</td>
|
||||
<td valign="top"><i>{{ _('Maintains the integrated Bittorrent client') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{% trans forum=i2pconv('forum.i2p') %}<a href="http://{{ forum }}/viewforum?f=30">iMule</a> lead{% endtrans %}</b></td>
|
||||
<td valign="top" class="blue">[{{ _('vacant') }}]</td>
|
||||
<td valign="top"><i>{{ _('eMule client over I2P') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{% trans forum=i2pconv('forum.i2p') %}<a href="http://{{ forum }}/viewforum?f=29">Syndie</a> lead{% endtrans %}</b></td>
|
||||
<td valign="top"><b>{% trans forum=i2pconv('i2pforum.i2p') %}<a href="http://{{ forum }}/viewforum.php?f=25">Syndie</a> lead{% endtrans %}</b></td>
|
||||
<td valign="top" class="blue">[{{ _('vacant') }}]</td>
|
||||
<td valign="top"><i>{{ _('Syndie development') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{{ _('Susimail lead') }}</b></td>
|
||||
<td valign="top" class="blue">[{{ _('vacant') }}]</td>
|
||||
<td valign="top">zzz</td>
|
||||
<td valign="top"><i>{{ _('Susimail development') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -235,19 +215,9 @@ network.
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{{ _('SAM') }}</b></td>
|
||||
<td valign="top" class="blue">[{{ _('vacant') }}]</td>
|
||||
<td valign="top">zzz</td>
|
||||
<td valign="top"><i>{{ _('SAM maintainer') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{{ _('I2Pd lead') }}</b></td>
|
||||
<td valign="top">orignal</td>
|
||||
<td valign="top"><i>{{ _('C++ Router') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{{ _('I2Pd Assistant lead') }}</b></td>
|
||||
<td valign="top">Meeh</td>
|
||||
<td valign="top"><i>{{ _('C++ Router') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top"><b>{{ _('Translators') }}</b></td>
|
||||
<td valign="top">{{ _('many many people!') }}</td>
|
||||
@ -271,15 +241,6 @@ network.
|
||||
<td valign="top">str4d</td>
|
||||
<td valign="top"><i>{{ _('Routerconsole backend and UI work, website revamp, unit tests work') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top">sindu</td>
|
||||
<td valign="top"><i>{{ _('The improved WSGI reseed script') }}</i></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top">Marielle</td>
|
||||
<td valign="top"><i>{{ _('The ICToopie twist of itoopie (the new color mix for
|
||||
Purple I2P)') }}</i></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td valign="top" class="blue">[{{ _('vacant') }}]</td>
|
||||
|
||||
@ -23,7 +23,7 @@ either protocol may be carried by either transport.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<h2>{% trans %}Application Guide{% endtrans %}</h2>
|
||||
<p>{% trans url='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/datagram/package-summary.html',
|
||||
<p>{% trans url='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/datagram/package-summary.html',
|
||||
sam= site_url('docs/api/sam'),
|
||||
socks=site_url('docs/api/socks') -%}
|
||||
Applications written in Java may use the
|
||||
@ -70,7 +70,7 @@ Applications may add 'from' and 'to' ports to the I2CP (gzip) header as describe
|
||||
the <a href="{{ i2cp }}#format">I2CP page</a>.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans i2psession='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/I2PSession.html' -%}
|
||||
<p>{% trans i2psession='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/I2PSession.html' -%}
|
||||
There is no method within the datagram API to specify whether it is non-repliable (raw)
|
||||
or repliable. The application should be designed to expect the appropriate type.
|
||||
The I2CP protocol number or port should be used by the application to
|
||||
@ -82,8 +82,8 @@ use signed datagrams for a request which includes a nonce, and use a raw datagra
|
||||
for the reply, returning the nonce from the request.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans i2psession='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/I2PSession.html',
|
||||
i2psessionmuxed='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/I2PSessionMuxedImpl.html' -%}
|
||||
<p>{% trans i2psession='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/I2PSession.html',
|
||||
i2psessionmuxed='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/I2PSessionMuxedImpl.html' -%}
|
||||
The protocols and ports may be set in I2CP's
|
||||
<a href="{{ i2psession }}">I2PSession API</a>,
|
||||
as implemented in
|
||||
|
||||
@ -4,7 +4,7 @@
|
||||
|
||||
<h2>{% trans %}Note{% endtrans %}</h2>
|
||||
|
||||
<p>{% trans streaming=site_url('docs/api/streaming'), api='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/streaming/package-summary.html' -%}
|
||||
<p>{% trans streaming=site_url('docs/api/streaming'), api='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/streaming/package-summary.html' -%}
|
||||
The ministreaming library has been enhanced and extended by the
|
||||
"full" <a href="{{ streaming }}">streaming library</a>.
|
||||
Ministreaming is deprecated and is incompatible with today's applications.
|
||||
@ -42,7 +42,7 @@ messages sent (or include any application level ACK or SACK), so it must wait
|
||||
on average twice the time it takes to send a message before sending another.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans api='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/streaming/package-summary.html',
|
||||
<p>{% trans api='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/streaming/package-summary.html',
|
||||
samv3=site_url('docs/api/samv3') -%}
|
||||
Even with those issues, the ministreaming library performs quite well in many
|
||||
situations, and its <a href="{{ api }}">API</a>
|
||||
|
||||
@ -389,7 +389,7 @@ followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_Priv
|
||||
followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_SigningPrivateKey">Signing Private Key</a>,
|
||||
which is 884 or more base 64 characters (663 or more bytes in binary),
|
||||
depending on signature type.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
|
||||
----------------------------------------------------------------------
|
||||
RESULT values
|
||||
|
||||
@ -446,7 +446,7 @@ followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_Priv
|
||||
followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_SigningPrivateKey">Signing Private Key</a>,
|
||||
which is 884 or more base 64 characters (663 or more bytes in binary),
|
||||
depending on signature type.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
|
||||
----------------------------------------------------------------------
|
||||
RESULT values
|
||||
|
||||
@ -342,7 +342,7 @@ followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_Priv
|
||||
followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_SigningPrivateKey">Signing Private Key</a>,
|
||||
which is 663 or more bytes in binary and 884 or more bytes in base 64,
|
||||
depending on signature type.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
|
||||
</p><p>
|
||||
If the destination is specified as TRANSIENT, the SAM bridge creates a new destination.
|
||||
@ -384,7 +384,7 @@ followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_Priv
|
||||
followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_SigningPrivateKey">Signing Private Key</a>,
|
||||
which is 663 or more bytes in binary and 884 or more bytes in base 64,
|
||||
depending on signature type.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
|
||||
</p><p>
|
||||
If the nickname is already associated with a session:
|
||||
@ -827,7 +827,7 @@ CREATE command with PORT and HOST options:
|
||||
followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_SigningPrivateKey">Signing Private Key</a>,
|
||||
which is 884 or more base 64 characters (663 or more bytes in binary),
|
||||
depending on signature type.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
|
||||
</p><p>
|
||||
$host is the hostname or IP address of the datagram server to
|
||||
@ -1202,7 +1202,7 @@ followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_Priv
|
||||
followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_SigningPrivateKey">Signing Private Key</a>,
|
||||
which is 884 or more base 64 characters (663 or more bytes in binary),
|
||||
depending on signature type.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
|
||||
</p><p>
|
||||
DEST GENERATE does not require that a session has been created first.
|
||||
|
||||
@ -65,11 +65,11 @@ streaming library, to be interpreted by I2CP.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans i2cp=site_url('docs/protocol/i2cp'),
|
||||
i2psktmf='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/streaming/I2PSocketManagerFactory.html',
|
||||
i2psktm='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/streaming/I2PSocketManager.html',
|
||||
i2psess='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/I2PSession.html',
|
||||
i2pskt='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/streaming/I2PSocket.html',
|
||||
i2psskt='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/streaming/I2PServerSocket.html' -%}
|
||||
i2psktmf='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/streaming/I2PSocketManagerFactory.html',
|
||||
i2psktm='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/streaming/I2PSocketManager.html',
|
||||
i2psess='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/I2PSession.html',
|
||||
i2pskt='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/streaming/I2PSocket.html',
|
||||
i2psskt='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/streaming/I2PServerSocket.html' -%}
|
||||
The standard interface to the streaming lib is for the application to use the
|
||||
<a href="{{ i2psktmf }}">I2PSocketManagerFactory</a> to create an
|
||||
<a href="{{ i2psktm }}">I2PSocketManager</a>. The application then asks the
|
||||
@ -79,7 +79,7 @@ can then setup connections with an <a href="{{ i2pskt }}">I2PSocket</a> or
|
||||
receive connections with an <a href="{{ i2psskt }}">I2PServerSocket</a>.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans url='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/streaming/package-summary.html' -%}
|
||||
<p>{% trans url='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/streaming/package-summary.html' -%}
|
||||
Here are the <a href="{{ url }}">full streaming library Javadocs</a>.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
@ -89,7 +89,7 @@ For a good example of usage, see the i2psnark code.
|
||||
|
||||
|
||||
<h3 id="options">{% trans %}Options and Defaults{% endtrans %}</h3>
|
||||
<p>{% trans i2psktmf='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/streaming/I2PSocketManagerFactory.html' -%}
|
||||
<p>{% trans i2psktmf='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/streaming/I2PSocketManagerFactory.html' -%}
|
||||
The options and current default values are listed below.
|
||||
Options are case-sensitive and may be set for the whole router, for a particular client, or for an individual socket on a
|
||||
per-connection basis.
|
||||
|
||||
@ -363,7 +363,7 @@ as is done in our Java packages.
|
||||
As always, state management is the difficult part.
|
||||
{%- endtrans %}</p>
|
||||
<p>
|
||||
See also: <a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/router/Router.html">the Router javadocs</a>.
|
||||
See also: <a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/router/Router.html">the Router javadocs</a>.
|
||||
</p>
|
||||
|
||||
{% endblock %}
|
||||
|
||||
@ -105,7 +105,7 @@ some of I2P's more useful capabilities.
|
||||
<dt><em>{{ _('plugin') }}</em></dt>
|
||||
|
||||
<dd>
|
||||
<p>{% trans plugins=i2pconv('plugins.i2p') -%}
|
||||
<p>{% trans plugins=('stats.i2p/i2p/plugins/') -%}
|
||||
<em>Third-party plugin</em> — I2P's plugin system provides convenient
|
||||
deployment of I2P-enabled applications and allows tighter integration
|
||||
with the router. Plugins are [reviewed by the community](<a href=
|
||||
@ -217,7 +217,7 @@ shortcuts.
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<p><a href="http://syndie.i2p2.de/"><strong>Syndie</strong></a> —
|
||||
<p><a href="http://syndie.de/"><strong>Syndie</strong></a> —
|
||||
{% trans %}Distributed forums software, originally developed by jrandom.{% endtrans %}
|
||||
<sup><em>[{{ _('plugin') }}, {{ _('standalone') }}, {{ _('unmaintained') }}]</em></sup></p>
|
||||
</li>
|
||||
@ -234,7 +234,7 @@ Plugin available <a href="http://{{ plugins }}/plugins/jamwiki">here</a>.
|
||||
<h3 id="decentralized-file-storage"><a href="#TOC">{% trans %}Decentralized File Storage{% endtrans %}</a></h3>
|
||||
|
||||
<ul>
|
||||
<li><a href="http://{{ i2pconv('killyourtv.i2p') }}/tahoe-lafs/"><strong>Tahoe-LAFS-I2P</strong></a> —
|
||||
<li><a href="http://echelon.i2p/tahoelafs/"><strong>Tahoe-LAFS-I2P</strong></a> —
|
||||
{% trans stats=i2pconv('stats.i2p') -%}
|
||||
Port of the <a href="http://tahoe-lafs.org/"><strong>Tahoe-LAFS</strong></a>
|
||||
distributed file system to the I2P network. Controller plugin <a href=
|
||||
@ -339,8 +339,9 @@ and configuration settings for
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<p><a href="http://{{ i2pconv('forum.i2p') }}/viewtopic.php?t=4532"><strong>I2PSnarkXL</strong></a> —
|
||||
{% trans %}Modified version of I2PSnark.{% endtrans %}
|
||||
<p><a href="http://echelon.i2p/i2psnarkxl"><strong>I2PSnarkXL</strong></a> —
|
||||
{% trans %}Modified version of I2PSnark, no more supported neither
|
||||
functional.{% endtrans %}
|
||||
<sup><em>[{{ _('standalone') }}]</em></sup></p>
|
||||
</li>
|
||||
|
||||
@ -411,7 +412,7 @@ branch of the <a href="{{ newdevs }}">I2P Monotone repository</a>.
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<a href="http://{{ i2pconv('forum.i2p') }}/viewtopic.php?t=2213"><strong>iMule</strong></a> —
|
||||
<a href="http://www.imule.i2p"><strong>iMule</strong></a> —
|
||||
{% trans %}I2P port of the aMule ED2K client.{% endtrans %}
|
||||
<sup><em>[{{ _('standalone') }}]</em></sup></li>
|
||||
</ul>
|
||||
@ -420,7 +421,7 @@ branch of the <a href="{{ newdevs }}">I2P Monotone repository</a>.
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p><a href="http://{{ i2pconv('forum.i2p') }}/viewforum.php?f=25"><strong>I2Phex</strong></a> —
|
||||
<p><a href="http://echelon.i2p/i2phex"><strong>I2Phex</strong></a> —
|
||||
{% trans stats=i2pconv('stats.i2p') -%}
|
||||
Port of the <a href="http://www.phex.org/mambo/">Phex</a> Gnutella client. Website
|
||||
for plugin version <a href="http://{{ stats }}/i2p/plugins/">here</a>.
|
||||
@ -429,7 +430,7 @@ for plugin version <a href="http://{{ stats }}/i2p/plugins/">here</a>.
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<p><a href="http://{{ i2pconv('forum.i2p') }}/viewtopic.php?p=9486#9486"><strong>jwebcache</strong></a> —
|
||||
<p><a href="http://echelon.i2p/jwebcache"><strong>jwebcache</strong></a> —
|
||||
{% trans stats=i2pconv('stats.i2p') -%}
|
||||
Cache for Gnutella peers on I2P. Website for plugin version
|
||||
<a href="http://{{ stats }}/i2p/plugins/">here</a>.
|
||||
@ -487,8 +488,8 @@ have appeared over the years.
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<a href="http://{{ i2pconv('forum.i2p') }}/viewtopic.php?t=2474"><strong>I2P Messenger</strong></a> —
|
||||
{% trans %}IM client with multiple incarnations.{% endtrans %}
|
||||
<a href="http://echelon.i2p/qti2pmessenger"><strong>I2P Messenger</strong></a> —
|
||||
{% trans %}IM client with multiple incarnations, unsuported.{% endtrans %}
|
||||
<sup><em>[{{ _('standalone') }}]</em></sup>
|
||||
</li>
|
||||
</ul>
|
||||
@ -646,12 +647,13 @@ Gateways allowing users on the public Internet to access eepsites.
|
||||
<li>
|
||||
<a href="http://i2p.to/"><strong>i2p.to</strong></a> —
|
||||
{% trans tino=i2pconv('tino.i2p') -%}
|
||||
<a href="http://{{ tino }}/">tino's</a> inproxy on the public Internet.
|
||||
<a href="http://{{ tino }}/">tino's</a> inproxy on the public Internet,
|
||||
currently out of service,
|
||||
{%- endtrans %}
|
||||
<sup><em>[{{ _('service') }}]</em></sup>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<!-- <li>
|
||||
<a href="http://i2p.us/"><strong>i2p.us</strong></a> —
|
||||
{% trans -%}
|
||||
Another inproxy on the public Internet.
|
||||
@ -661,7 +663,7 @@ Another inproxy on the public Internet.
|
||||
|
||||
<li>
|
||||
<a href="http://i2p.me/"><strong>i2p.me</strong></a> —
|
||||
<!--
|
||||
|
||||
{% trans -%}
|
||||
Another inproxy on the public Internet.
|
||||
{%- endtrans %}
|
||||
|
||||
@ -186,7 +186,7 @@ RouterInfos are periodically written to disk so that they are available after a
|
||||
<a href="{{ site_url('docs/spec/common-structures') }}#struct_RouterInfo">{% trans %}RouterInfo specification{% endtrans %}</a>
|
||||
</p>
|
||||
<p>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/router/RouterInfo.html">{% trans %}RouterInfo Javadoc{% endtrans %}</a>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/router/RouterInfo.html">{% trans %}RouterInfo Javadoc{% endtrans %}</a>
|
||||
</p>
|
||||
|
||||
<h2 id="leaseSet">LeaseSet</h2>
|
||||
@ -222,9 +222,9 @@ In addition to these leases, the LeaseSet includes:
|
||||
<a href="{{ site_url('docs/spec/common-structures') }}#struct_LeaseSet">{% trans %}LeaseSet specification{% endtrans %}</a>
|
||||
</p>
|
||||
<p>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/Lease.html">{% trans %}Lease Javadoc{% endtrans %}</a>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/Lease.html">{% trans %}Lease Javadoc{% endtrans %}</a>
|
||||
<br />
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/LeaseSet.html">{% trans %}LeaseSet Javadoc{% endtrans %}</a>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/LeaseSet.html">{% trans %}LeaseSet Javadoc{% endtrans %}</a>
|
||||
</p>
|
||||
|
||||
|
||||
@ -234,7 +234,7 @@ A LeaseSet for a destination used only for outgoing connections is <i>unpublishe
|
||||
It is never sent for publication to a floodfill router.
|
||||
"Client" tunnels, such as those for web browsing and IRC clients, are unpublished.
|
||||
Servers will still be able to send messages back to those unpublished destinations,
|
||||
because of <a href="#leaseset_storage_peers">I2NP storage messages</a>.
|
||||
because of <a href="#lsp">I2NP storage messages</a>.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
|
||||
@ -293,7 +293,7 @@ for the entry to be sent, verifying its proper insertion / distribution. If the
|
||||
verification peer doesn't reply, or they don't have the entry, the sender
|
||||
repeats the process. When the peer in the floodfill netDb receives a netDb
|
||||
store from a peer not in the floodfill netDb, they send it to a subset of the floodfill netDb-peers.
|
||||
The peers selected are the ones closest (according to the <a href="#kademlia_closeness">XOR-metric</a>) to a specific key.
|
||||
The peers selected are the ones closest (according to the <a href="#kad">XOR-metric</a>) to a specific key.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans -%}
|
||||
@ -357,7 +357,7 @@ Since they are generally high-bandwidth, they are more likely to participate in
|
||||
{%- endtrans %}</p>
|
||||
|
||||
|
||||
<a name="kademlia_closeness"><h2 id="kad">{% trans %}Kademlia Closeness Metric{% endtrans %}</h2></a>
|
||||
<h2 id="kad">{% trans %}Kademlia Closeness Metric{% endtrans %}</h2>
|
||||
<p>{% trans -%}
|
||||
The netDb uses a simple Kademlia-style XOR metric to determine closeness.
|
||||
The SHA256 hash of the key being looked up or stored is XOR-ed with
|
||||
@ -388,7 +388,7 @@ or <a href="{{ ssu }}">SSU</a> transport connection.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
|
||||
<a name="leaseset_storage_peers"><h3>{% trans %}LeaseSet Storage to Peers{% endtrans %}</h3></a>
|
||||
<h3 id="lsp">{% trans %}LeaseSet Storage to Peers{% endtrans %}</h3>
|
||||
<p>{% trans i2np=site_url('docs/protocol/i2np') -%}
|
||||
<a href="{{ i2np }}">I2NP</a> DatabaseStoreMessages containing the local LeaseSet are periodically exchanged with peers
|
||||
by bundling them in a garlic message along with normal traffic from the related Destination.
|
||||
|
||||
@ -63,7 +63,7 @@ See <a href="#notes">below</a> for notes on minor changes since the paper was pu
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<h2>{% trans %}Profiles{% endtrans %}</h2>
|
||||
<p>{% trans url='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/router/peermanager/PeerProfile.html' -%}
|
||||
<p>{% trans url='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/router/peermanager/PeerProfile.html' -%}
|
||||
Each peer has a set of data points collected about them, including statistics
|
||||
about how long it takes for them to reply to a network database query, how
|
||||
often their tunnels fail, and how many new peers they are able to introduce
|
||||
@ -142,7 +142,7 @@ speed calculation meets or exceeds the median of all peers.
|
||||
<li>{% trans %}A peer is considered "standard" if it is not "high capacity"{% endtrans %}</li>
|
||||
</ul>
|
||||
|
||||
<p>{% trans url='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/router/peermanager/ProfileOrganizer.html' -%}
|
||||
<p>{% trans url='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/router/peermanager/ProfileOrganizer.html' -%}
|
||||
These groupings are implemented in the router's
|
||||
<a href="{{ url }}">ProfileOrganizer</a>.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
{% extends "global/layout.html" %}
|
||||
{% block title %}{% trans %}Index to Technical Documentation{% endtrans %}{% endblock %}
|
||||
{% block lastupdated %}{% trans %}January 2016{% endtrans %}{% endblock %}
|
||||
{% block accuratefor %}0.9.24{% endblock %}
|
||||
{% block lastupdated %}{% trans %}April 2018{% endtrans %}{% endblock %}
|
||||
{% block accuratefor %}0.9.34{% endblock %}
|
||||
{% block content %}
|
||||
<p>{% trans -%}
|
||||
Following is an index to the technical documentation for I2P.
|
||||
@ -88,11 +88,11 @@ HTTP Bidir Proxy
|
||||
</li><li>
|
||||
<a href="{{ spec_url('streaming') }}">{{ _('Streaming Protocol Specification') }}</a>
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/client/streaming/package-summary.html">{{ _('Streaming Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/client/streaming/package-summary.html">{{ _('Streaming Javadoc') }}</a>
|
||||
</li><li>
|
||||
<a href="{{ spec_url('datagrams') }}">{{ _('Datagrams') }}</a>
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/client/datagram/package-summary.html">{{ _('Datagram Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/client/datagram/package-summary.html">{{ _('Datagram Javadoc') }}</a>
|
||||
</li></ul>
|
||||
|
||||
<h3>{% trans %}Client-to-Router Interface API and Protocol{% endtrans %}</h3>
|
||||
@ -105,11 +105,11 @@ Traditionally used only by Java applications and higher-level APIs.
|
||||
</li><li>
|
||||
<a href="{{ spec_url('i2cp') }}">{{ _('I2CP Specification') }}</a>
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/client/package-summary.html">{{ _('I2CP API Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/client/package-summary.html">{{ _('I2CP API Javadoc') }}</a>
|
||||
</li><li>
|
||||
<a href="{{ spec_url('common-structures') }}">{{ _('Common data structures specification') }}</a>
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/package-summary.html">{{ _('Data Structures Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/package-summary.html">{{ _('Data Structures Javadoc') }}</a>
|
||||
</li></ul>
|
||||
|
||||
<h3>{% trans %}End-to-End Encryption{% endtrans %}</h3>
|
||||
@ -135,11 +135,11 @@ Traditionally used only by Java applications and higher-level APIs.
|
||||
</li><li>
|
||||
<a href="{{ spec_url('i2np') }}">{{ _('I2NP Specification') }}</a>
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/i2np/package-summary.html">{{ _('I2NP Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/i2np/package-summary.html">{{ _('I2NP Javadoc') }}</a>
|
||||
</li><li>
|
||||
<a href="{{ spec_url('common-structures') }}">{{ _('Common data structures specification') }}</a>
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/package-summary.html">{{ _('Data Structures Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/package-summary.html">{{ _('Data Structures Javadoc') }}</a>
|
||||
</li></ul>
|
||||
|
||||
<h3>{% trans %}Tunnels{% endtrans %}</h3>
|
||||
@ -173,11 +173,11 @@ Traditionally used only by Java applications and higher-level APIs.
|
||||
</li><li>
|
||||
<a href="{{ site_url('docs/how/cryptography') }}#udp">{{ _('SSU transport encryption') }}</a>
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/router/transport/package-summary.html">{{ _('Transport Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/router/transport/package-summary.html">{{ _('Transport Javadoc') }}</a>
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/router/transport/ntcp/package-summary.html">{{ _('NTCP Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/router/transport/ntcp/package-summary.html">{{ _('NTCP Javadoc') }}</a>
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/router/transport/udp/package-summary.html">{{ _('SSU Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/router/transport/udp/package-summary.html">{{ _('SSU Javadoc') }}</a>
|
||||
</li></ul>
|
||||
|
||||
<h3>{% trans %}Other Router Topics{% endtrans %}</h3>
|
||||
@ -212,31 +212,39 @@ Traditionally used only by Java applications and higher-level APIs.
|
||||
{% trans %}Note: always verify that javadocs are current by checking the release number.{% endtrans %}
|
||||
</li><li>
|
||||
{% trans %}Javadocs inside I2P:{% endtrans %}
|
||||
<!--
|
||||
down (kytv)
|
||||
<a href="http://{{ i2pconv('i2p-javadocs.i2p') }}">{% trans num=1 %}Server {{ num }}{% endtrans %}</a>
|
||||
ancient (str4d)
|
||||
<a href="http://{{ i2pconv('i2pdocs.str4d.i2p') }}/i2p.i2p/javadoc/">{% trans num=2 %}Server {{ num }}{% endtrans %}</a>
|
||||
-->
|
||||
<a href="http://{{ i2pconv('echelon.i2p') }}/javadoc/">{% trans num=3 %}Server {{ num }}{% endtrans %}</a>
|
||||
<!--
|
||||
<a href="http://{{ i2pconv('docs.i2p2.i2p') }}/javadoc/">Server 4 - out of date, incomplete</a>
|
||||
-->
|
||||
{% trans %}Note: always verify that javadocs are current by checking the release number.{% endtrans %}
|
||||
</li><li>
|
||||
<a href="{{ site_url('spec/proposals') }}">{{ _('Proposals') }}</a>
|
||||
</li><li>
|
||||
<a href="{{ site_url('docs/applications/embedding') }}">{{ _('Embedding the router in your application') }}</a>
|
||||
</li><li>
|
||||
<a href="{{ site_url('get-involved/guides/reseed') }}">{{ _('How to Set up a Reseed Server') }}</a>
|
||||
</li><li>
|
||||
<a href="{{ site_url('docs/ports') }}">{{ _('Ports used by I2P') }}</a>
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('update.killyourtv.i2p') }}/mtn/">{{ _('Automatic updates to development builds inside I2P') }}</a>
|
||||
<a href="http://{{ i2pconv('bobthebuilder.i2p') }}/mtn/">{{ _('Automatic updates to development builds inside I2P') }}</a>
|
||||
</li><li>
|
||||
<a href="{{ site_url('misc/manual-wrapper') }}">{{ _('Updating the wrapper manually') }}</a>
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('forum.i2p') }}">{{ _('User forum') }}</a>
|
||||
<a href="http://{{ i2pconv('i2pforum.i2p') }}">{{ _('User forum') }}</a>
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('zzz.i2p') }}/">{{ _('Developer forum inside I2P') }}</a>
|
||||
</li><li>
|
||||
<a href="https://trac.i2p2.de/report/1">{{ _('Bug tracker') }}</a>
|
||||
<!--
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('killyourtv.i2p') }}/viewmtn/">{{ _('Viewmtn inside I2P') }}</a>.
|
||||
-->
|
||||
</li><li>
|
||||
<a href="https://github.com/i2p/i2p.i2p">{{ _('I2P Source exported to GitHub') }}</a>
|
||||
</li><li>
|
||||
|
||||
@ -140,7 +140,7 @@ It also maintains a reverse-lookup map to implement rapid reverse lookups.
|
||||
|
||||
<h3>{{ _('Other Naming Service Facilities') }}</h3>
|
||||
|
||||
<p>{% trans nsjavadocs='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/naming/package-summary.html' -%}
|
||||
<p>{% trans nsjavadocs='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/naming/package-summary.html' -%}
|
||||
The lookup is case-insensitive.
|
||||
The first match is used, and conflicts are not detected.
|
||||
There is no enforcement of naming rules in lookups.
|
||||
|
||||
@ -15,7 +15,7 @@ I2CP to tell the client when any messages have arrived, and to request authoriza
|
||||
for some tunnels to be used.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans url='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/client/package-summary.html',
|
||||
<p>{% trans url='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/package-summary.html',
|
||||
libi2cp='http://git.repo.i2p/w/libi2cp.git',
|
||||
streaming=site_url('docs/api/streaming') -%}
|
||||
The protocol itself is implemented in Java, to provide the
|
||||
|
||||
@ -19,7 +19,7 @@ through multiple hops to the ultimate destination.
|
||||
Priority is only used locally at the origin, i.e. when queuing for outbound delivery.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans outnetmessage='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/router/OutNetMessage.html' -%}
|
||||
<p>{% trans outnetmessage='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/router/OutNetMessage.html' -%}
|
||||
The priorities listed below may not be current and are subject to change.
|
||||
See the <a href="{{ outnetmessage }}">OutNetMessage Javadocs</a>
|
||||
for the current priority settings.
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
{% extends "global/layout.html" %}
|
||||
{% block title %}{{ _('Roadmap') }}{% endblock %}
|
||||
{% block lastupdated %}{% trans %}February 2018{% endtrans %}{% endblock %}
|
||||
{% block lastupdated %}{% trans %}March 2018{% endtrans %}{% endblock %}
|
||||
{% block content %}
|
||||
|
||||
<p>
|
||||
@ -248,9 +248,11 @@ Pluginization of current apps
|
||||
</li><li>
|
||||
App improvements
|
||||
</li><li>
|
||||
Susimail and I2P-Bote stabilisation
|
||||
Susimail and I2P-Bote stabilization
|
||||
</li><li>
|
||||
Ticket triage
|
||||
Android stabilization and fixes
|
||||
</li><li>
|
||||
Bug fixes
|
||||
</li><li>
|
||||
User support
|
||||
</li></ul>
|
||||
@ -258,17 +260,71 @@ User support
|
||||
|
||||
|
||||
<h2 id="0.9.34">0.9.34</h2>
|
||||
<p><b>Target release date: Mid-April 2018</b></p>
|
||||
<p><b>Target release date: Week of April 9, 2018</b></p>
|
||||
<ul><li>
|
||||
Susimail fixes, improvements, refactoring part 2
|
||||
</li><li>
|
||||
I2PControl plugin fixed
|
||||
</li><li>
|
||||
UPnP support for IGD 2
|
||||
</li><li>
|
||||
IPv6 address selection improvements
|
||||
</li><li>
|
||||
Better tunnel peer selection for hidden and IPv6-only modes
|
||||
</li><li>
|
||||
Prep for HTTPS console and eepsite by default
|
||||
</li><li>
|
||||
Prep for splitting up Debian package
|
||||
</li><li>
|
||||
Mac OS X installer, dock, tray enhancements (research and initial work)
|
||||
</li><li>
|
||||
Bug fixes, translation updates, geoip updates
|
||||
</li></ul>
|
||||
|
||||
<p><b>Note: To be updated below here</b></p>
|
||||
|
||||
<h2 id="0.9.35">0.9.35</h2>
|
||||
<p><b>Target release date: Mid-late June 2018</b></p>
|
||||
<ul><li>
|
||||
Versioning/caps props 136/137/TBD?
|
||||
Jetty 9.2.23
|
||||
</li><li>
|
||||
Tomcat 8.5.29
|
||||
</li><li>
|
||||
Susimail folders, background sending
|
||||
</li><li>
|
||||
Improved support for SSL console and eepsite
|
||||
</li><li>
|
||||
Bug fixes, translation updates, geoip updates
|
||||
</li><li>
|
||||
Progress on proposal #111 (NTCP2)
|
||||
</li><li>
|
||||
Mac OS X installer, dock, tray enhancements
|
||||
</li><li>
|
||||
Android GMP 6 and 64-bit jbigi
|
||||
</li><li>
|
||||
Android fixes
|
||||
</li><li>
|
||||
Bote fixes
|
||||
</li><li>
|
||||
Private test net setup improvements (Docker, BSD Jails, VMs)
|
||||
</li><li>
|
||||
Unit test improvements
|
||||
</li><li>
|
||||
<b>Note: Website items TBD.</b>
|
||||
New CSS for website front page
|
||||
</li><li>
|
||||
New CSS for website inner pages
|
||||
</li><li>
|
||||
Redesigned website home page
|
||||
</li><li>
|
||||
Restructure website
|
||||
</li></ul>
|
||||
|
||||
|
||||
|
||||
|
||||
<h2 id="2h2018">0.9.36 - 0.9.37 Late 2018</h2>
|
||||
<p><b>Note: To be updated June 2018</b></p>
|
||||
<ul><li>
|
||||
Debian packaging changes and improvements
|
||||
</li><li>
|
||||
Ready indication for Tails
|
||||
@ -277,124 +333,74 @@ EdDSA updates
|
||||
</li><li>
|
||||
ElGamal speedups
|
||||
</li><li>
|
||||
Fix and enable linux tray app
|
||||
</li><li>
|
||||
Private test net setup improvements
|
||||
</li><li>
|
||||
Progress on proposal #123 (NTCP2)
|
||||
</li><li>
|
||||
Progress on proposal #111
|
||||
(LS2 with multi-destination support)
|
||||
</li><li>
|
||||
Mac OS X installer, dock, tray enhancements (partial)
|
||||
</li><li>
|
||||
Review ElGamal website docs
|
||||
</li><li>
|
||||
Initial research on ElGamal replacement ("new crypto")
|
||||
Progress on proposal #123
|
||||
(LS2 with multi-destination support)
|
||||
</li><li>
|
||||
New CSS for website front page
|
||||
Initial research on ElGamal replacement ("new crypto" / proposal #142)
|
||||
</li><li>
|
||||
Capacity improvements: discussions and research
|
||||
Versioning/caps props 136/137/142/TBD
|
||||
</li><li>
|
||||
Create proposal and research multipath and path-awareness via I2CP
|
||||
</li><li>
|
||||
Tahoe site
|
||||
</li><li>
|
||||
Android gather user feedback
|
||||
</li><li>
|
||||
Android UI enhancements
|
||||
</li><li>
|
||||
Android GMP 6 and 64-bit jbigi
|
||||
</li><li>
|
||||
Android router service as a library
|
||||
</li><li>
|
||||
Android logging improvements
|
||||
</li><li>
|
||||
Android wakelock fix
|
||||
</li><li>
|
||||
Unit test improvements
|
||||
</li><li>
|
||||
GMP 6.1.1 (ticket #1869), possibly partial
|
||||
</li><li>
|
||||
New CSS for website inner pages
|
||||
</li><li>
|
||||
Android fixes
|
||||
</li><li>
|
||||
Bote fixes
|
||||
</li><li>
|
||||
Android tunnel settings
|
||||
</li><li>
|
||||
Android profiles
|
||||
</li><li>
|
||||
Setup wizard
|
||||
</li><li>
|
||||
Further work on pluggable transports: obfs4 as a plugin
|
||||
</li><li>
|
||||
Bug fixes, translation updates, geoip updates
|
||||
</li></ul>
|
||||
|
||||
|
||||
<h2 id="0.9.35">0.9.35</h2>
|
||||
<p><b>Target release date: Early June 2018</b></p>
|
||||
<p><b>Note: To be updated</b></p>
|
||||
<ul><li>
|
||||
Susimail fixes, improvements, refactoring part 3
|
||||
</li><li>
|
||||
Continue research on ElGamal replacement ("new crypto")
|
||||
</li><li>
|
||||
Continue research on New netdb
|
||||
</li><li>
|
||||
Full support for massively popular hidden services
|
||||
</li><li>
|
||||
Initial work on new naming system, make sense of alternatives, kbuckets
|
||||
</li><li>
|
||||
Console redesign phase 2
|
||||
</li><li>
|
||||
Console UI refactor
|
||||
</li><li>
|
||||
Capacity improvements: discussions and research
|
||||
</li><li>
|
||||
Streaming improvements
|
||||
</li><li>
|
||||
Performance improvements
|
||||
</li><li>
|
||||
Bundle (un-pluginize) I2PControl
|
||||
</li><li>
|
||||
Continue work on ElGamal replacement ("new crypto" / proposal #142)
|
||||
</li><li>
|
||||
Integrated chat client?
|
||||
</li><li>
|
||||
Full support for massively popular hidden services (LS2 / prop 123)
|
||||
</li><li>
|
||||
Capacity improvements
|
||||
</li><li>
|
||||
NTCP Pumper redesign
|
||||
</li><li>
|
||||
I2PTunnel socket-side NIO
|
||||
</li><li>
|
||||
Android profiles
|
||||
</li><li>
|
||||
Redesigned website home page
|
||||
</li><li>
|
||||
Restructure website
|
||||
</li><li>
|
||||
Android fixes
|
||||
</li><li>
|
||||
Bote fixes
|
||||
</li>
|
||||
<li>
|
||||
Integrated chat client?
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
|
||||
|
||||
|
||||
<h2 id="2h2018">0.9.36 - 0.9.37 Late 2018</h2>
|
||||
<p><b>Note: To be updated</b></p>
|
||||
<ul><li>
|
||||
Complete I2PControl API 2 spec, implement in plugin (proposal #118)
|
||||
</li><li>
|
||||
Bundle (un-pluginize) I2PControl with API 2 (proposal #118)
|
||||
</li><li>
|
||||
Continue work on ElGamal replacement ("new crypto")
|
||||
</li>
|
||||
</ul>
|
||||
GMP 6.1.2 (ticket #1869), possibly partial
|
||||
</li></ul>
|
||||
|
||||
|
||||
<h2 id="2019">2019</h2>
|
||||
<ul><li>
|
||||
NTCP2 including new DH, AEAD (proposal #123)
|
||||
NTCP2 including new DH, AEAD (proposal #111)
|
||||
</li><li>
|
||||
LS2 with multi-destination support (proposal #111)
|
||||
LS2 with multi-destination support (proposal #123)
|
||||
</li><li>
|
||||
{% trans todo=site_url('get-involved/todo') -%}
|
||||
Reachability Mapping / handle peers partially reachable / enhanced <a href="{{ todo }}#fullRestrictedRoutes">restricted routes</a>
|
||||
|
||||
@ -22,7 +22,7 @@ as a replacement for the
|
||||
As modPow() is a significant computational portion of many crypto operations, this is of significant benefit.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans nativebigint='http://'+i2pconv('i2p-javadocs.i2p')+'/net/i2p/util/NativeBigInteger.html',
|
||||
<p>{% trans nativebigint='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/util/NativeBigInteger.html',
|
||||
bigint='http://download.oracle.com/javase/1.5.0/docs/api/java/math/BigInteger.html#modPow%28java.math.BigInteger,%20java.math.BigInteger%29' -%}
|
||||
The standard I2P installation includes about 20 versions of the library for different platforms,
|
||||
each about 50KB, inside the jbigi.jar file.
|
||||
|
||||
@ -92,7 +92,7 @@ Contents
|
||||
````````
|
||||
256 bytes
|
||||
|
||||
JavaDoc: http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/PublicKey.html
|
||||
JavaDoc: http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/PublicKey.html
|
||||
|
||||
.. _type-PrivateKey:
|
||||
|
||||
@ -109,7 +109,7 @@ Contents
|
||||
````````
|
||||
256 bytes
|
||||
|
||||
JavaDoc: http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/PrivateKey.html
|
||||
JavaDoc: http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/PrivateKey.html
|
||||
|
||||
.. _type-SessionKey:
|
||||
|
||||
@ -124,7 +124,7 @@ Contents
|
||||
````````
|
||||
32 bytes
|
||||
|
||||
JavaDoc: http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/SessionKey.html
|
||||
JavaDoc: http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/SessionKey.html
|
||||
|
||||
.. _type-SigningPublicKey:
|
||||
|
||||
@ -164,7 +164,7 @@ Notes
|
||||
* All types are Big Endian, except for EdDSA, which is stored and transmitted
|
||||
in a Little Endian format.
|
||||
|
||||
JavaDoc: http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/SigningPublicKey.html
|
||||
JavaDoc: http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/SigningPublicKey.html
|
||||
|
||||
.. _type-SigningPrivateKey:
|
||||
|
||||
@ -203,7 +203,7 @@ Notes
|
||||
* All types are Big Endian, except for EdDSA, which is stored and transmitted
|
||||
in a Little Endian format.
|
||||
|
||||
JavaDoc: http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/SigningPrivateKey.html
|
||||
JavaDoc: http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/SigningPrivateKey.html
|
||||
|
||||
.. _type-Signature:
|
||||
|
||||
@ -243,7 +243,7 @@ Notes
|
||||
* All types are Big Endian, except for EdDSA, which is stored and transmitted
|
||||
in a Little Endian format.
|
||||
|
||||
JavaDoc: http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/Signature.html
|
||||
JavaDoc: http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/Signature.html
|
||||
|
||||
.. _type-Hash:
|
||||
|
||||
@ -258,7 +258,7 @@ Contents
|
||||
````````
|
||||
32 bytes
|
||||
|
||||
JavaDoc: http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/Hash.html
|
||||
JavaDoc: http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/Hash.html
|
||||
|
||||
.. _type-SessionTag:
|
||||
|
||||
@ -273,7 +273,7 @@ Contents
|
||||
````````
|
||||
32 bytes
|
||||
|
||||
JavaDoc: http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/SessionTag.html
|
||||
JavaDoc: http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/SessionTag.html
|
||||
|
||||
.. _type-TunnelId:
|
||||
|
||||
@ -290,7 +290,7 @@ Contents
|
||||
````````
|
||||
4 byte Integer_
|
||||
|
||||
JavaDoc: http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/TunnelId.html
|
||||
JavaDoc: http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/TunnelId.html
|
||||
|
||||
.. _type-Certificate:
|
||||
|
||||
@ -462,7 +462,7 @@ EdDSA_SHA512_Ed25519 96 0
|
||||
EdDSA_SHA512_Ed25519ph 96 0
|
||||
====================== ============== ===============================
|
||||
|
||||
JavaDoc: http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/Certificate.html
|
||||
JavaDoc: http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/Certificate.html
|
||||
|
||||
Notes
|
||||
`````
|
||||
@ -544,7 +544,7 @@ Notes
|
||||
|
||||
.. _I2CP SessionConfig: {{ site_url('docs/spec/i2cp') }}#struct_SessionConfig
|
||||
|
||||
JavaDoc: http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/DataHelper.html
|
||||
JavaDoc: http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/DataHelper.html
|
||||
|
||||
|
||||
Common structure specification
|
||||
@ -619,7 +619,7 @@ Notes
|
||||
* The Crypto Public Key is aligned at the start and the Signing Public Key is
|
||||
aligned at the end. The padding (if any) is in the middle.
|
||||
|
||||
JavaDoc: http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/KeysAndCert.html
|
||||
JavaDoc: http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/KeysAndCert.html
|
||||
|
||||
.. _struct-RouterIdentity:
|
||||
|
||||
@ -648,7 +648,7 @@ Notes
|
||||
* The Crypto Public Key is aligned at the start and the Signing Public Key is
|
||||
aligned at the end. The padding (if any) is in the middle.
|
||||
|
||||
JavaDoc: http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/router/RouterIdentity.html
|
||||
JavaDoc: http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/router/RouterIdentity.html
|
||||
|
||||
.. _struct-Destination:
|
||||
|
||||
@ -681,7 +681,7 @@ Notes
|
||||
* The Crypto Public Key is aligned at the start and the Signing Public Key is
|
||||
aligned at the end. The padding (if any) is in the middle.
|
||||
|
||||
JavaDoc: http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/Destination.html
|
||||
JavaDoc: http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/Destination.html
|
||||
|
||||
.. _struct-Lease:
|
||||
|
||||
@ -729,7 +729,7 @@ Notes
|
||||
`````
|
||||
* Total size: 44 bytes
|
||||
|
||||
JavaDoc: http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/Lease.html
|
||||
JavaDoc: http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/Lease.html
|
||||
|
||||
.. _struct-LeaseSet:
|
||||
|
||||
@ -865,7 +865,7 @@ Notes
|
||||
publishes the actual lease expiration for each lease. This is an
|
||||
implementation detail and not part of the structures specification.
|
||||
|
||||
JavaDoc: http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/LeaseSet.html
|
||||
JavaDoc: http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/LeaseSet.html
|
||||
|
||||
.. _struct-RouterAddress:
|
||||
|
||||
@ -937,7 +937,7 @@ Notes
|
||||
present in most router addresses: "host" (an IPv4 or IPv6 address or host
|
||||
name) and "port".
|
||||
|
||||
JavaDoc: http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/router/RouterAddress.html
|
||||
JavaDoc: http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/router/RouterAddress.html
|
||||
|
||||
.. _struct-RouterInfo:
|
||||
|
||||
@ -1045,7 +1045,7 @@ Notes
|
||||
so the signature is invariant.
|
||||
This is no longer required, and not worth implementing for backward compatibility.
|
||||
|
||||
JavaDoc: http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/router/RouterInfo.html
|
||||
JavaDoc: http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/router/RouterInfo.html
|
||||
|
||||
.. _struct-DeliveryInstructions:
|
||||
|
||||
|
||||
@ -463,7 +463,7 @@ References
|
||||
==========
|
||||
|
||||
.. [DATAHELPER]
|
||||
http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/DataHelper.html
|
||||
http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/DataHelper.html
|
||||
|
||||
.. [Mapping]
|
||||
{{ ctags_url('Mapping') }}
|
||||
|
||||
@ -1352,7 +1352,7 @@ References
|
||||
{{ site_url('docs/protocol/i2cp', True) }}#options
|
||||
|
||||
.. [I2CP-JAVADOCS]
|
||||
http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/i2cp/package-summary.html
|
||||
http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/i2cp/package-summary.html
|
||||
|
||||
.. [Integer]
|
||||
{{ ctags_url('Integer') }}
|
||||
@ -1368,7 +1368,7 @@ References
|
||||
{{ ctags_url('Mapping') }}
|
||||
|
||||
.. [MSM-JAVADOCS]
|
||||
http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/data/i2cp/MessageStatusMessage.html
|
||||
http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/i2cp/MessageStatusMessage.html
|
||||
|
||||
.. [PrivateKey]
|
||||
{{ ctags_url('PrivateKey') }}
|
||||
|
||||
@ -560,6 +560,7 @@ TunnelBuild_ 21
|
||||
TunnelBuildReply_ 22
|
||||
VariableTunnelBuild_ 23
|
||||
VariableTunnelBuildReply_ 24
|
||||
Reserved 0
|
||||
Reserved for experimental messages 224-254
|
||||
Reserved for future expansion 255
|
||||
================================== =======
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -5,8 +5,8 @@ I2PControl API 2
|
||||
:author: hottuna
|
||||
:created: 2016-01-23
|
||||
:thread: http://zzz.i2p/topics/2030
|
||||
:lastupdated: 2016-02-01
|
||||
:status: Open
|
||||
:lastupdated: 2018-03-22
|
||||
:status: Rejected
|
||||
|
||||
.. contents::
|
||||
|
||||
@ -16,6 +16,8 @@ Overview
|
||||
|
||||
This proposal outlines API2 for I2PControl.
|
||||
|
||||
This proposal was rejected and will not be implemented, because it breaks backwards compatibility.
|
||||
See the discussion thread link for details.
|
||||
|
||||
Developer headsup!
|
||||
------------------
|
||||
|
||||
@ -5,7 +5,7 @@ IPv6 Peer Testing
|
||||
:author: zzz
|
||||
:created: 2016-05-02
|
||||
:thread: http://zzz.i2p/topics/2119
|
||||
:lastupdated: 2016-12-02
|
||||
:lastupdated: 2018-03-19
|
||||
:status: Closed
|
||||
:target: 0.9.27
|
||||
:implementedin: 0.9.27
|
||||
@ -64,7 +64,6 @@ In the Peer Testing sections of the SSU overview and SSU specification, make the
|
||||
|
||||
IPv6 Notes:
|
||||
Through release 0.9.26, only testing of IPv4 addresses is supported.
|
||||
Only testing of IPv4 addresses is supported.
|
||||
Therefore, all Alice-Bob and Alice-Charlie communication must be via IPv4.
|
||||
Bob-Charlie communication, however, may be via IPv4 or IPv6.
|
||||
Alice's address, when specified in the PeerTest message, must be 4 bytes.
|
||||
|
||||
@ -5,7 +5,7 @@ Deprecate hostnames in router addresses
|
||||
:author: zzz
|
||||
:created: 2017-08-03
|
||||
:thread: http://zzz.i2p/topics/2363
|
||||
:lastupdated: 2017-09-02
|
||||
:lastupdated: 2018-03-17
|
||||
:status: Closed
|
||||
:target: 0.9.32
|
||||
:implementedin: 0.9.32
|
||||
@ -121,6 +121,10 @@ Specification
|
||||
Change the NTCP and SSU transport specs to indicate that the "host" parameter must be
|
||||
an IP, not a hostname, and that routers should ignore individual
|
||||
router addresses that contain hostnames.
|
||||
|
||||
This also applies to "ihost0", "ihost1", and "ihost2" parameters in an SSU address.
|
||||
Routers should ignore introducer addresses that contain hostnames.
|
||||
|
||||
The relevant section is "Router Address Specification" in the transport specifications:
|
||||
http://i2p-projekt.i2p/en/docs/transport/ntcp
|
||||
and
|
||||
|
||||
@ -302,7 +302,7 @@ instructions are:
|
||||
total length: 7 bytes
|
||||
{% endhighlight %}
|
||||
|
||||
JavaDoc: http://{{ i2pconv('i2p-javadocs.i2p') }}/net/i2p/router/tunnel/FragmentHandler.html
|
||||
JavaDoc: http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/router/tunnel/FragmentHandler.html
|
||||
|
||||
|
||||
Notes
|
||||
|
||||
@ -23,6 +23,7 @@ I2P_TO_CLEAR = {
|
||||
'mail.i2p': 'i2pmail.org',
|
||||
'lists.i2p2.i2p': 'lists.i2p2.de',
|
||||
'i2p-javadocs.i2p': 'docs.i2p-projekt.de/javadoc', # Hacky to include the path, but it works!
|
||||
'echelon.i2p/javadoc': 'docs.i2p-projekt.de/javadoc', # Hacky to include the path, but it works!
|
||||
'stats.i2p': 'stats.i2p', # Inproxy disabled at request of site owner
|
||||
'zzz.i2p': 'zzz.i2p', # Inproxy disabled at request of site owner
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user