Adding 32C3 post.

i2p2www/blog/2016/01/23/32C3.draft.rst

@@ -0,0 +1,106 @@
+{% 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
+=====
+Wooo! Another successful year at CCC.
+A huge shoutout to the angels and organizers at `32C3`_.
+Just like previous years, we were located in Noisy Square to the right of the EFF's table.
+Many were able to attend due to the generous donations.
+As always, there was a lot of interest in I2P, and we were able to talk to many people who we otherwise would not have had the ability to.
+{%- endtrans %}
+
+.. _{% trans %}`32C3`{% endtrans %}: https://events.ccc.de/congress/2015/wiki/Static:Main_Page
+
+{% trans -%}
+The Year of Usability!
+======================
+{%- endtrans %}
+
+{% trans -%}
+There was a lot of talk about the usability of the router console.
+Many people noted that their best experience with I2P was through Vuze/I2PBote-Android.
+Currently there are vague discussions of redoing the current router console since it is a bit abrasive for new users to understand.
+{%- endtrans %}
+
+{% trans -%}
+We need your feedback!
+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.
+See the `contacts page`_.
+{%- endtrans %}
+
+.. _{% trans %}`contacts page`{% endtrans %}: {{ site_url() }}contact
+
+{% trans -%}
+Reseed Status
+=============
+{%- endtrans %}
+
+Let's get more reseeds!
+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 don't know, a reseed server is the server new routers contact to find peers.
+If you have the resources to run a reseed, (or if you're talented in Go) email backup -at- i2pmail.i2p.
+
+{% 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 using.
+Right now, 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 awesome work done on I2P is lost in the commits.
+Meaning that to non-developers, there is nothing to see.
+To remedy this lazygravy plans on preparing a series of technical posts explaining some technical topics in I2P.
+For example, but not limited to, encrypted lease sets, why different tunnel types are needed, some observations seen in [i2spy](GITHUB LINK).
+{%- endtrans %}
+
+{% 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://zzz.i2p/topics/2014-meeting-tues-feb-2-8-pm-utc
+