forked from I2P_Developers/i2p.www
Fix .rst syntax errors - 2015
This commit is contained in:
slumlord
@@ -28,15 +28,15 @@ Square and the 31C3 organizers for a great Congress.
|
||||
.. _`Noisy Square`: https://noisysquare.com/
|
||||
|
||||
{% trans -%}
|
||||
We also thank Gabriel Weinberg and his fabulous search engine `DuckDuckGo`_ for
|
||||
their support of open source anonymity tools and their `generous contribution`_
|
||||
We also thank Gabriel Weinberg and his fabulous search engine `DuckDuckGo`__ for
|
||||
their support of open source anonymity tools and their `generous contribution`__
|
||||
to I2P in 2014. Funding from DuckDuckGo and others helped support our attendance
|
||||
at CCC. This is the primary annual meetup for I2P developers and it is critical
|
||||
to our success.
|
||||
{%- endtrans %}
|
||||
|
||||
.. _`DuckDuckGo`: https://duckduckgo.com/
|
||||
.. _{{ _('`generous contribution`') }}: https://geti2p.net/en/blog/post/2014/03/12/press-release-ddg-donation
|
||||
__ https://duckduckgo.com/
|
||||
__ https://geti2p.net/en/blog/post/2014/03/12/press-release-ddg-donation
|
||||
|
||||
{% trans -%}
|
||||
Discussions with others
|
||||
@@ -47,15 +47,15 @@ GNUnet
|
||||
------
|
||||
|
||||
{% trans -%}
|
||||
We spoke at length with Christian Grothoff of `GNUnet`_. He has moved himself
|
||||
and the project from TU Munich to `Inria`_ in France. He has a large number of
|
||||
`open positions`_. This is a great opportunity to get paid to work on open
|
||||
We spoke at length with Christian Grothoff of `GNUnet`__. He has moved himself
|
||||
and the project from TU Munich to `Inria`__ in France. He has a large number of
|
||||
`open positions`__. This is a great opportunity to get paid to work on open
|
||||
source anonymity tools, we encourage everybody to contact him about it.
|
||||
{%- endtrans %}
|
||||
|
||||
.. _`GNUnet`: https://gnunet.org/
|
||||
.. _`Inria`: https://www.inria.fr/en/
|
||||
.. _{{ _('`open positions`') }}: https://gnunet.org/hiring
|
||||
__ https://gnunet.org/
|
||||
__ https://www.inria.fr/en/
|
||||
__ https://gnunet.org/hiring
|
||||
|
||||
{% trans -%}
|
||||
The prospect of an invigorated GNUnet with a large amount of new funding is
|
||||
@@ -67,24 +67,24 @@ the network. We'd definitely be interested in that.
|
||||
{%- endtrans %}
|
||||
|
||||
{% trans -%}
|
||||
We also discussed the `Special-Use Domain Names of Peer-to-Peer Systems draft`_.
|
||||
We also discussed the `Special-Use Domain Names of Peer-to-Peer Systems draft`__.
|
||||
A new, greatly simplified version 3 was posted in December. The prospects for
|
||||
approval remain unclear. The best way to monitor or participate in the
|
||||
discussion is via the `IETF DNSOP WG mailing list`_. We will attempt to do so
|
||||
discussion is via the `IETF DNSOP WG mailing list`__. We will attempt to do so
|
||||
on our side, and also give Hellekin a new point-of-contact for this topic.
|
||||
{%- endtrans %}
|
||||
|
||||
.. _{{ _('`Special-Use Domain Names of Peer-to-Peer Systems draft`') }}: https://datatracker.ietf.org/doc/draft-grothoff-iesg-special-use-p2p-names/
|
||||
.. _{{ _('`IETF DNSOP WG mailing list`') }}: https://www.ietf.org/mail-archive/web/dnsop/current/maillist.html
|
||||
__ https://datatracker.ietf.org/doc/draft-grothoff-iesg-special-use-p2p-names/
|
||||
__ https://www.ietf.org/mail-archive/web/dnsop/current/maillist.html
|
||||
|
||||
{% trans -%}
|
||||
We apologized to Christian for not being organized enough to have a talk at his
|
||||
`We Fix The Net assembly`_. One of our biggest failures as a project is our
|
||||
`We Fix The Net assembly`__. One of our biggest failures as a project is our
|
||||
seeming inability to submit talks at conferences. We'll have to do better in the
|
||||
new year.
|
||||
{%- endtrans %}
|
||||
|
||||
.. _{{ _('`We Fix The Net assembly`') }}: https://events.ccc.de/congress/2014/wiki/Session:WeFixTheNet
|
||||
__ https://events.ccc.de/congress/2014/wiki/Session:WeFixTheNet
|
||||
|
||||
Debian
|
||||
------
|
||||
@@ -93,12 +93,12 @@ Debian
|
||||
Iain Learmonth, a Debian participant, stopped by. He wants to put I2P in with
|
||||
other anonymity tools into this new Debian "superpackage" of some sort, and
|
||||
would love to get I2P into Debian in 2015. He claims the process is now easy,
|
||||
just `follow the instructions`_. We said that's funny, we've been
|
||||
`stuck in the process for over 7 years`_.
|
||||
just `follow the instructions`__. We said that's funny, we've been
|
||||
`stuck in the process for over 7 years`__.
|
||||
{%- endtrans %}
|
||||
|
||||
.. _{{ _('`follow the instructions`') }}: https://mentors.debian.net/
|
||||
.. _{{ _('`stuck in the process for over 7 years`') }}: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=448638
|
||||
__ https://mentors.debian.net/
|
||||
__ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=448638
|
||||
|
||||
{% trans -%}
|
||||
He said, well, try the new process, it works great, should be no problem at all
|
||||
@@ -114,15 +114,15 @@ Tails
|
||||
|
||||
{% trans -%}
|
||||
We had a nice discussion with BitingBird of Tails. They are very happy with our
|
||||
rapid response to the `vulnerability disclosure`_ last summer, resulting in our
|
||||
`0.9.14 release`_. Our vulnerability was initially blamed on Tails, and they
|
||||
took `great offense`_ to that and the lack of private notification. We thanked
|
||||
rapid response to the `vulnerability disclosure`__ last summer, resulting in our
|
||||
`0.9.14 release`__. Our vulnerability was initially blamed on Tails, and they
|
||||
took `great offense`__ to that and the lack of private notification. We thanked
|
||||
them for taking the heat and fighting back.
|
||||
{%- endtrans %}
|
||||
|
||||
.. _{{ _('`vulnerability disclosure`') }}: https://twitter.com/ExodusIntel/status/491247299054428160
|
||||
.. _{{ _('`0.9.14 release`') }}: {{ get_url('blog_post', slug='2014/07/26/0.9.14-Release') }}
|
||||
.. _{{ _('`great offense`') }}: https://tails.boum.org/news/On_0days_exploits_and_disclosure/index.en.html
|
||||
__ https://twitter.com/ExodusIntel/status/491247299054428160
|
||||
__ {{ get_url('blog_post', slug='2014/07/26/0.9.14-Release') }}
|
||||
__ https://tails.boum.org/news/On_0days_exploits_and_disclosure/index.en.html
|
||||
|
||||
{% trans -%}
|
||||
BitingBird also handles support, and she tells us the number one issue is how
|
||||
@@ -138,19 +138,19 @@ Onioncat
|
||||
--------
|
||||
|
||||
{% trans -%}
|
||||
Longtime friend of I2P Bernhard Fischer of `OnionCat`_ stopped by. The upcoming
|
||||
Longtime friend of I2P Bernhard Fischer of `OnionCat`__ stopped by. The upcoming
|
||||
Tor Hidden Services changes mean that their keys will no longer fit into a
|
||||
portion of an IPv6 address, and he was working on a solution. We reminded him
|
||||
that this has always been the case for I2P (with "GarliCat"), that it's not a
|
||||
new problem. He pointed us to `a presentation`_ of his proposal. It involves
|
||||
new problem. He pointed us to `a presentation`__ of his proposal. It involves
|
||||
storing an extra record in the hidden service directory (equivalent of a
|
||||
leaseset I2P's network database). It wasn't completely clear how this would
|
||||
work, or if we would consider it abuse of the netDb. We'll follow up with him
|
||||
as he gets further.
|
||||
{%- endtrans %}
|
||||
|
||||
.. _`OnionCat`: https://www.onioncat.org/
|
||||
.. _{{ _('`a presentation`') }}: https://www.youtube.com/watch?v=Zj4hSx6cW80
|
||||
__ https://www.onioncat.org/
|
||||
__ https://www.youtube.com/watch?v=Zj4hSx6cW80
|
||||
|
||||
{% trans -%}
|
||||
New users
|
||||
@@ -176,103 +176,67 @@ I2P project topics
|
||||
{%- endtrans %}
|
||||
|
||||
{% trans -%}
|
||||
* *Spending money:* We discussed several ways to effectively use our resources
|
||||
in 2015, including more hardware for testing and development. Also, we plan to
|
||||
increase reimbursement levels for conference attendees.
|
||||
* *Spending money:* We discussed several ways to effectively use our resources in 2015, including more hardware for testing and development. Also, we plan to increase reimbursement levels for conference attendees.
|
||||
{%- endtrans %}
|
||||
|
||||
{% trans -%}
|
||||
* *Toronto meetup:* CCC is such a productive time for us, and it seems that a
|
||||
second meetup in the year would be quite helpful. We have proposed it for
|
||||
August 2015 in Toronto, Canada, in conjunction with `Toronto Crypto`_. It
|
||||
would include developer meetings together with presentations and tutorials,
|
||||
all open to the public. We are attempting to gauge interest and research
|
||||
possible venues. If you are considering attending, please let us know by
|
||||
`tweeting @i2p`_ or posting `on the dev forum thread`_.
|
||||
* *Toronto meetup:* CCC is such a productive time for us, and it seems that a second meetup in the year would be quite helpful. We have proposed it for August 2015 in Toronto, Canada, in conjunction with `Toronto Crypto`__. It would include developer meetings together with presentations and tutorials, all open to the public. We are attempting to gauge interest and research possible venues. If you are considering attending, please let us know by `tweeting @i2p`__ or posting `on the dev forum thread`__.
|
||||
{%- endtrans %}
|
||||
|
||||
__ https://torontocrypto.org/
|
||||
__ https://twitter.com/i2p
|
||||
__ http://{{ i2pconv('zzz.i2p') }}/topics/1778
|
||||
|
||||
{% trans -%}
|
||||
* We discussed Meeh's workload and the state of the various services he is running. We made some plans to reduce his load and have some other people help out.
|
||||
{%- endtrans %}
|
||||
|
||||
{% trans -%}
|
||||
* We discussed Meeh's workload and the state of the various services he is
|
||||
running. We made some plans to reduce his load and have some other people help
|
||||
out.
|
||||
* We reviewed our critieria for placing links to `i2pd`__ on our download page. We agreed that the only remaining item is to have a nice page on the `Privacy Solutions web site`__ or elsewhere with binary packages for Windows, Linux, and Mac, and source packages. It's not clear who is responsible for building the packages and where the "official" version is. Once there's an established process for building and signing packages and an official place to put them, we're ready to link to it. If it is not feasible to host it on the Privacy Solutions website, we will discuss alternatives with orignal, including possible migration to our download servers.
|
||||
{%- endtrans %}
|
||||
|
||||
__ https://github.com/PrivacySolutions/i2pd
|
||||
__ https://privacysolutions.no/
|
||||
|
||||
{% trans -%}
|
||||
* Lots of people coming by the table asked if we had a non-Java version. It was great to finally answer "yes" and we're eager to get the word out and get more users, testers, and developers on it.
|
||||
{%- endtrans %}
|
||||
|
||||
{% trans -%}
|
||||
* We reviewed our critieria for placing links to `i2pd`_ on our download page.
|
||||
We agreed that the only remaining item is to have a nice page on the
|
||||
`Privacy Solutions web site`_ or elsewhere with binary packages for Windows,
|
||||
Linux, and Mac, and source packages. It's not clear who is responsible for
|
||||
building the packages and where the "official" version is. Once there's an
|
||||
established process for building and signing packages and an official place to
|
||||
put them, we're ready to link to it. If it is not feasible to host it on the
|
||||
Privacy Solutions website, we will discuss alternatives with orignal,
|
||||
including possible migration to our download servers.
|
||||
* `Vuze`__ continues to make good progress on their I2P integration. We look forward to working with them in the new year on a managed rollout to more users.
|
||||
{%- endtrans %}
|
||||
|
||||
__ https://www.vuze.com/
|
||||
|
||||
{% trans -%}
|
||||
* We discussed the state of Meeh's and Sindu's reseed servers. They made several improvements while at the congress and are investigating migration to `Matt Drollette's Go implementation`__. The security and reliability of our reseed servers is vital to new users and network operation. `User 'backup'`__ is doing a great job monitoring and managing the pool of reseed servers.
|
||||
{%- endtrans %}
|
||||
|
||||
__ https://github.com/MDrollette/i2p-tools
|
||||
__ mailto:backup@mail.i2p
|
||||
|
||||
{% trans -%}
|
||||
* We agreed to purchase a second root server for development, testing, and services. Echelon will be adminstering it. Contact him if you would like a VM.
|
||||
{%- endtrans %}
|
||||
|
||||
{% trans -%}
|
||||
* Lots of people coming by the table asked if we had a non-Java version. It was
|
||||
great to finally answer "yes" and we're eager to get the word out and get more
|
||||
users, testers, and developers on it.
|
||||
* We reiterated that we have funds available to purchase test hardware, especially for Windows and Mac. Talk to echelon for details.
|
||||
{%- endtrans %}
|
||||
|
||||
{% trans -%}
|
||||
* `Vuze`_ continues to make good progress on their I2P integration. We look
|
||||
forward to working with them in the new year on a managed rollout to more
|
||||
users.
|
||||
* We met with Welterde about the state of his services including his `open tracker`__. These services are not being adequately maintained and will soon become inaccessible due to crypto changes if they are not upgraded. He committed to upgrading them soon.
|
||||
{%- endtrans %}
|
||||
|
||||
__ http://{{ i2pconv('tracker.welterde.i2p') }}/stats?mode=peer
|
||||
|
||||
{% trans -%}
|
||||
* We discussed the state of Meeh's and Sindu's reseed servers. They made several
|
||||
improvements while at the congress and are investigating migration to
|
||||
`Matt Drollette's Go implementation`_. The security and reliability of our
|
||||
reseed servers is vital to new users and network operation. `User 'backup'`_
|
||||
is doing a great job monitoring and managing the pool of reseed servers.
|
||||
* We met lots of people interested in our `Android app`__. We passed several ideas and bug reports back to str4d. We plan to make a big push to give the app some development love early in the year.
|
||||
{%- endtrans %}
|
||||
|
||||
__ https://play.google.com/store/apps/details?id=net.i2p.android
|
||||
|
||||
{% trans -%}
|
||||
* We agreed to purchase a second root server for development, testing, and
|
||||
services. Echelon will be adminstering it. Contact him if you would like a VM.
|
||||
* Regrettably, we didn't get to see too many talks at the Congress, as we were so busy meeting with people. We plan to catch up and `watch them online`__. As usual, Tor's "State of the Onion" talk was excellent, and Jacob's talk was great. We hear that the cryptography talks were good as well.
|
||||
{%- endtrans %}
|
||||
|
||||
{% trans -%}
|
||||
* We reiterated that we have funds available to purchase test hardware,
|
||||
especially for Windows and Mac. Talk to echelon for details.
|
||||
{%- endtrans %}
|
||||
|
||||
{% trans -%}
|
||||
* We met with Welterde about the state of his services including his
|
||||
`open tracker`_. These services are not being adequately maintained and will
|
||||
soon become inaccessible due to crypto changes if they are not upgraded. He
|
||||
committed to upgrading them soon.
|
||||
{%- endtrans %}
|
||||
|
||||
{% trans -%}
|
||||
* We met lots of people interested in our `Android app`_. We passed several
|
||||
ideas and bug reports back to str4d. We plan to make a big push to give the
|
||||
app some development love early in the year.
|
||||
{%- endtrans %}
|
||||
|
||||
{% trans -%}
|
||||
* Regrettably, we didn't get to see too many talks at the Congress, as we were
|
||||
so busy meeting with people. We plan to catch up and `watch them online`_. As
|
||||
usual, Tor's "State of the Onion" talk was excellent, and Jacob's talk was
|
||||
great. We hear that the cryptography talks were good as well.
|
||||
{%- endtrans %}
|
||||
|
||||
.. _{{ _('`Toronto Crypto`') }}: https://torontocrypto.org/
|
||||
.. _{{ _('`tweeting @i2p`') }}: https://twitter.com/i2p
|
||||
.. _{{ _('`on the dev forum thread`') }}: http://{{ i2pconv('zzz.i2p') }}/topics/1778
|
||||
|
||||
.. _`i2pd`: https://github.com/PrivacySolutions/i2pd
|
||||
.. _{{ _('`Privacy Solutions web site`') }}: https://privacysolutions.no/
|
||||
|
||||
.. _`Vuze`: https://www.vuze.com/
|
||||
|
||||
.. _{{ _("`Matt Drollette's Go implementation`") }}: https://github.com/MDrollette/i2p-tools
|
||||
.. _{{ _("`User 'backup'`") }}: mailto:backup@mail.i2p
|
||||
|
||||
.. _{{ _('`open tracker`') }}: http://{{ i2pconv('tracker.welterde.i2p') }}/stats?mode=peer
|
||||
|
||||
.. _{{ _('`Android app`') }}: https://play.google.com/store/apps/details?id=net.i2p.android
|
||||
|
||||
.. _{{ _('`watch them online`') }}: https://media.ccc.de/browse/congress/2014/
|
||||
__ https://media.ccc.de/browse/congress/2014/
|
||||
|
||||
@@ -47,13 +47,13 @@ Cost
|
||||
{%- endtrans %}
|
||||
|
||||
{% trans -%}
|
||||
I2PCon is entirely free to attend! We ask you to register `here`_, to give us
|
||||
I2PCon is entirely free to attend! We ask you to register `here`__, to give us
|
||||
an estimate of how many people will be attending. No identifying information has
|
||||
to be given in order to register, but if you have any concerns, please let us
|
||||
know.
|
||||
{%- endtrans %}
|
||||
|
||||
.. _{{ _('`here`') }}: http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466
|
||||
__ http://www.eventbrite.ca/e/i2p-meetup-tickets-17773984466
|
||||
|
||||
{% trans -%}
|
||||
Location
|
||||
|
||||
@@ -19,16 +19,17 @@ If all goes well, we will accelerate the rekeying process in the next release.
|
||||
|
||||
{% trans -%}
|
||||
I2PCon Toronto was a big success!
|
||||
All the presentations and videos are listed on the `I2PCon page`_.
|
||||
All the presentations and videos are listed on the `I2PCon page`__.
|
||||
{%- endtrans %}
|
||||
|
||||
__ /en/about/i2pcon/2015
|
||||
|
||||
{% trans -%}
|
||||
As usual, we recommend that you update to this release. The best way to
|
||||
maintain security and help the network is to run the latest release.
|
||||
{%- endtrans %}
|
||||
|
||||
|
||||
.. _{% trans %}`I2PCon page`{% endtrans %}: /en/about/i2pcon/2015
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -26,14 +26,14 @@ My signing key has been in router updates for over two years (since 0.9.9), so
|
||||
if you are on a recent version of I2P this update should be just as easy as
|
||||
every other update. However, if you are running an older version than 0.9.9, you
|
||||
will first need to manually update to a recent version. Update files for recent
|
||||
versions `can be downloaded here`_, and instructions on how to manually update
|
||||
`are provided here`_. Once you have manually updated, your router will then find
|
||||
versions `can be downloaded here`__, and instructions on how to manually update
|
||||
`are provided here`__. Once you have manually updated, your router will then find
|
||||
and download the 0.9.23 update as usual.
|
||||
{%- endtrans %}
|
||||
|
||||
.. _{% trans %}`can be downloaded here`{% endtrans %}: https://download.i2p2.de/releases/
|
||||
__ https://download.i2p2.de/releases/
|
||||
|
||||
.. _{% trans %}`are provided here`{% endtrans %}: {{ get_url('downloads_list') }}#update
|
||||
__ {{ get_url('downloads_list') }}#update
|
||||
|
||||
{% trans -%}
|
||||
If you installed I2P via a package manager, you are not affected by the change,
|
||||
|
||||
Reference in New Issue
Block a user