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 %}
{%- endtrans %}
{% trans -%}
{% trans -%}
There was a lot of talk about the usability of the router console.
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 people noted that their best experience with I2P was through Vuze/I2PBote-Android.
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 a bit abrasive for new users to understand.
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 %}
{%- endtrans %}
{% trans -%}
{% trans -%}
We need your feedback!
We need your feedback!
Even if you don't use I2P often, we want to know what you think.
Even if you don't use I2P often, we want to know what you think.
There are lots of ways to contact us, Twitter, or email.
Please `get in touch with us`_ and let us know what improvements or ideas you have!
See the `contacts page`_.
{%- endtrans %}
{%- endtrans %}
.. _{% trans %}`contacts page`{% endtrans %}: {{ site_url() }}contact
.. _{% trans %}`get in touch with us`{% endtrans %}: {{ site_url() }}contact
#}
{% trans -%}
{% trans -%}
Reseed Status
Reseed Status
=============
=============
{%- endtrans %}
{%- endtrans %}
{% trans -%}
Let's get more reseeds!
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.
There was a lot of discussion around the current status of the reseed network right now.
As always, more reseed operators are needed!
As always, more reseed operators are needed!
If you don't know, a reseed server is the server new routers contact to find peers.
If you would like to strengthen the reseed infrastructure, (or if you're talented with Go) email `backup -at- i2pmail.org`_.
If you have the resources to run a reseed, (or if you're talented in Go) email backup -at- i2pmail.i2p.
Due to the decentralized nature of I2P, detecting Sybil attacks is not as straight forward as on other networks (i.e. tor).
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 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 using.
To be brief, the tool runs in the router, and collects information on floodfills your router is currently aware of.
Right now, the tool is mainly collecting a baseline, and does not act on any of the information it is collecting.
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!
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 %}
{%- endtrans %}
{% trans -%}
{% trans -%}
...
@@ -82,19 +103,21 @@ The meeting focused on organizationally preparing for more project management, a
...
@@ -82,19 +103,21 @@ The meeting focused on organizationally preparing for more project management, a
.. _{% trans %}`meeting`{% endtrans %}: {{ site_url() }}meetings/241
.. _{% trans %}`meeting`{% endtrans %}: {{ site_url() }}meetings/241
{% trans -%}
{% trans -%}
We discussed how much of the awesome work done on I2P is lost in the commits.
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.
Meaning that to non-developers, there is nothing to see.
To remedy this lazygravy plans on preparing a series of posts explaining some technical topics in I2P.
To remedy this lazygravy plans on preparing a series of technical 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`_.
For example, but not limited to, encrypted lease sets, why different tunnel types are needed, some observations seen in [i2spy](GITHUB LINK).
But these are just the start and we would like to hear feedback on topics we should write about!
{%- endtrans %}
{%- endtrans %}
.. _{% trans %}`i2spy`{% endtrans %}: https://github.com/chris-barry/i2spy
{% trans -%}
{% trans -%}
Meeting (Future)
Meeting (Future)
================
================
{%- endtrans %}
{%- endtrans %}
{% trans -%}
{% trans -%}
There will be a `another meeting`_ on 2 Feburary 2016 to discuss...
There will be a `another meeting`_ on 2 Feburary 2016 to discuss:
{%- endtrans %}
{%- endtrans %}
- {% trans -%}Review of assigned tasks from 30 December meeting{% endtrans %}
- {% trans -%}Review of assigned tasks from 30 December meeting{% endtrans %}
...
@@ -102,5 +125,5 @@ There will be a `another meeting`_ on 2 Feburary 2016 to discuss...
...
@@ -102,5 +125,5 @@ There will be a `another meeting`_ on 2 Feburary 2016 to discuss...
- {% trans -%}GMP 6 readiness{% endtrans %}
- {% trans -%}GMP 6 readiness{% endtrans %}
- {% trans -%}A proposal for a code of conduct{% endtrans %}
- {% trans -%}A proposal for a code of conduct{% endtrans %}
.. _{% trans %}`another meeting`{% endtrans %}: http://zzz.i2p/topics/2014-meeting-tues-feb-2-8-pm-utc
.. _{% trans %}`another meeting`{% endtrans %}: http://{{ i2pconv('zzz.i2p') }}/topics/2014-meeting-tues-feb-2-8-pm-utc
