130 lines
4.9 KiB
ReStructuredText
130 lines
4.9 KiB
ReStructuredText
{% trans -%}
|
|
=========
|
|
CCC Recap
|
|
=========
|
|
{%- endtrans %}
|
|
.. meta::
|
|
:author: lazygravy
|
|
:date: 2016-01-23
|
|
:category: ccc
|
|
:excerpt: {% trans %}CCC!{% endtrans %}
|
|
|
|
{% trans -%}
|
|
Attending: Sadie, Colin, lazygravy, zzz, hottuna, kytv, cacapo, and eche|on.
|
|
{%- endtrans %}
|
|
|
|
{% trans -%}
|
|
Start
|
|
=====
|
|
The project has had another successful year at CCC.
|
|
We would like to thank the volunteers at `32C3`_ for all of their help in organizing this event and for being accommodating hosts for us.
|
|
Many I2P contributors were able to attend this year's Congress due to many of the generous donations from supporters like you to the project.
|
|
If you would like to fund I2P, please see `our donation page`_ for more information.
|
|
{%- endtrans %}
|
|
|
|
.. _{% trans %}`32C3`{% endtrans %}: https://events.ccc.de/congress/2015/wiki/Static:Main_Page
|
|
.. _{% trans %}`our donation page`{% endtrans %}: {{ site_url() }}get-involved/donate
|
|
|
|
{% trans -%}
|
|
Just like previous years we were located in Noisy Square, located near the EFF's table.
|
|
This proved to be an ideal spot for us as our table was almost always busy with current and new users who were interested in I2P, many of whom we wouldn't have otherwise had the ability to talk to.
|
|
{%- endtrans %}
|
|
|
|
{#
|
|
|
|
{% trans -%}
|
|
The Year of Usability
|
|
=====================
|
|
{%- endtrans %}
|
|
|
|
{% trans -%}
|
|
A common discussion point at the table was the usability of the router console, and how it can be better improved for all I2P users, with a specific focus on new users.
|
|
Many (both developers and users) have mentioned to us that their best experience with I2P was through `Vuze`_ and the `I2PBote Android app`_.
|
|
Currently there are vague discussions of redoing the current router console since it is difficult for many users to understand.
|
|
{%- endtrans %}
|
|
|
|
.. _{% trans %}`Vuze`{% endtrans %}: https://wiki.vuze.com/w/I2PHelper_HowTo
|
|
.. _{% trans %}`I2PBote Android app`{% endtrans %}: https://play.google.com/store/apps/details?id=i2p.bote.android
|
|
|
|
{% trans -%}
|
|
{%- endtrans %}
|
|
|
|
{% trans -%}
|
|
We need your feedback!
|
|
Even if you don't use I2P often, we want to know what you think.
|
|
Please `get in touch with us`_ and let us know what improvements or ideas you have!
|
|
{%- endtrans %}
|
|
|
|
.. _{% trans %}`get in touch with us`{% endtrans %}: {{ site_url() }}contact
|
|
|
|
#}
|
|
|
|
{% trans -%}
|
|
Reseed Status
|
|
=============
|
|
{%- endtrans %}
|
|
|
|
{% trans -%}
|
|
Let's get more reseeds!
|
|
{%- endtrans %}
|
|
|
|
{% trans -%}
|
|
If you don't know what a reseed server is, it is first the connection new routers use to find peers.
|
|
There was a lot of discussion around the current status of the reseed network right now.
|
|
As always, more reseed operators are needed!
|
|
If you would like to strengthen the reseed infrastructure, (or if you're talented with Go) email `backup -at- i2pmail.org`_.
|
|
{%- endtrans %}
|
|
|
|
.. _{% trans %}`backup -at- i2pmail.org`{% endtrans %}: mailto:backup -at- i2pmail.org?subject=How%20Do%20I%20Run%20a%20Reseed%20Node?
|
|
|
|
{% trans -%}
|
|
Sybil Detection (beta)
|
|
======================
|
|
{%- endtrans %}
|
|
|
|
{% trans -%}
|
|
Due to the decentralized nature of I2P detecting Sybil attacks is not as straight forward as on other networks (i.e. Tor).
|
|
To mitigate this zzz has been working on a new router-based Sybil detection tool.
|
|
To be brief, the tool runs in the router, and collects information on floodfills your router is currently aware of.
|
|
Currently the tool is mainly collecting a baseline and does not act on any of the information it is collecting.
|
|
Expect to see a writeup on this more as 0.9.25 or 0.9.26 approaches, as it is still in active development
|
|
{%- endtrans %}
|
|
|
|
{% trans -%}
|
|
Development Meeting
|
|
===================
|
|
{%- endtrans %}
|
|
|
|
{% trans -%}
|
|
On the 30th we held an in person `meeting`_ at our table.
|
|
The meeting focused on organizationally preparing for more project management, and public relations (both from Sadie).
|
|
{%- endtrans %}
|
|
|
|
.. _{% trans %}`meeting`{% endtrans %}: {{ site_url() }}meetings/241
|
|
|
|
{% trans -%}
|
|
We discussed how much of the work done on I2P is lost in the commits and there is not much to see for our users.
|
|
To remedy this lazygravy plans on preparing a series of posts explaining some technical topics in I2P.
|
|
The initial ideas that we discussed writing posts on are what encrypted lease sets are, why different tunnel types are needed, and some observations seen in `I2Spy`_.
|
|
But these are just the start and we would like to hear feedback on topics we should write about!
|
|
{%- endtrans %}
|
|
|
|
.. _{% trans %}`i2spy`{% endtrans %}: https://github.com/chris-barry/i2spy
|
|
|
|
{% trans -%}
|
|
Meeting (Future)
|
|
================
|
|
{%- endtrans %}
|
|
|
|
{% trans -%}
|
|
There will be a `another meeting`_ on 2 Feburary 2016 to discuss:
|
|
{%- endtrans %}
|
|
|
|
- {% trans -%}Review of assigned tasks from 30 December meeting{% endtrans %}
|
|
- {% trans -%}Project meeting plan for 2016{% endtrans %}
|
|
- {% trans -%}GMP 6 readiness{% endtrans %}
|
|
- {% trans -%}A proposal for a code of conduct{% endtrans %}
|
|
|
|
.. _{% trans %}`another meeting`{% endtrans %}: http://{{ i2pconv('zzz.i2p') }}/topics/2014-meeting-tues-feb-2-8-pm-utc
|
|
|