{% extends "global/layout.html" %}
{% block title %}{{ _('Contact') }}{% endblock %}
{% block content %}
<h2>{{ _('Email') }}</h2>
<p>{% trans -%}
Please do not use these email addresses for support requests.
These are not public email lists.
We do not provide help via email.
{%- endtrans %}</p>
<ul>
<li>press _at_ geti2p.net - Press contact
<br>
GPG Key fingerprint: <tt>8736 C702 E83E E8A6 D2F1  6CF3 7EB8 9548 0027 B05F</tt>
<br>
</li>
<li>security _at_ geti2p.net - Vulnerability disclosure
<br>
GPG Key fingerprint: <tt>EA27 06D6 14F5 28DB 764B  F47E CFCD C461 75E6 694A</tt>
<br>
<a href="get-involved/develop/security-key">Public key</a>
</li>
</ul>

<h2>IRC</h2>
<p>{% trans -%}
  Our primary IRC network is the Irc2P network within I2P; a default tunnel to this network is set up with new router installs.
  We are also present on multiple standard networks like <a href="http://www.oftc.net/oftc/OFTC">OFTC</a>,
  <a href="http://www.einirc.de/">EIN</a> and <a href="http://freenode.net/">Freenode</a>.
  All I2P-related channels on all these network are linked to the main channels on Irc2P via relay bots.
{%- endtrans %}</p>
<pre>
{% filter escape %}
{{ _('Channel list:') }}

#i2p       {{ _('General i2p discussion and help channel') }}
#i2p-chat  {{ _('Offtopic') }}
#i2p-dev   {{ _('Development talk') }}
#i2pd-dev  {{ _('Purple I2P (I2Pd) Development talk') }}
#Abscond   {{ _('Abscond browser bundle discussion and development') }}
{% endfilter %}
</pre>

<h2>{{ _('Forums') }}</h2>
<p>{% trans -%}Please visit our I2P user forum, which is frequented by developers/contributors too - {%- endtrans %} <a href="http://{{ i2pconv('i2pforum.i2p') }}/">{{ i2pconv('i2pforum.i2p') }}</a> ({% trans -%}available on clearnet at https://i2pforum.net and on I2P at http://i2pforum.i2p{%- endtrans %})</p>

<p>{% trans zzz=i2pconv('zzz.i2p') -%}
  Most of the discussion about I2P's development happens on the <a href="http://{{ zzz }}">I2P developer forum</a> (only reachable from within I2P network). This is usually the best place to start with inquiries, if the dev IRC channel is inactive.
{%- endtrans %}</p>

<h2>{{ _('Mailing lists') }}</h2>
<p>{% trans -%}
  I2P does have a mailing list, but it is rarely used as the current small team of developers prefer to communicate via IRC or the developer forum. This may change in future.
{%- endtrans %}</p>


<h3>{{ _('Subscribing') }}</h3>
<p>{% trans -%}
  To subscribe to a mailing list, go to the list information page (linked below) and fill out the form. I2P-internal email addresses (foobar@mail.i2p) can be used.
{%- endtrans %}</p>

<h3>{{ _('Unsubscribing') }}</h3>
<p>{% trans -%}
  To unsubscribe from a mailing list or edit your subscription options, go to the list information page (linked below) and enter your subscription email address.
{%- endtrans %}</p>

<h3>{{ _('Lists') }}</h3>
<ul>
  <li>
  <a href="http://{{ i2pconv('lists.i2p2.i2p') }}/mailman/listinfo/i2p-dev">i2p-dev</a> (<a href="http://{{ i2pconv('lists.i2p2.i2p') }}/pipermail/i2p-dev/">{{ _('Archive') }}</a>)<br/>
    {% trans %}I2P developer discussions - anything related to development of I2P{% endtrans %}
  </li>
  <li>
  <a href="http://{{ i2pconv('lists.i2p2.i2p') }}/mailman/listinfo/i2p-general">i2p-general</a> (<a href="http://{{ i2pconv('lists.i2p2.i2p') }}/pipermail/i2p-general/">{{ _('Archive') }}</a>)<br/>
    {% trans %}General I2P discussion - anything that doesn't fit in a different list goes here{% endtrans %}
  </li>
</ul>
{% endblock %}