perv.i2p -> identiguy.i2p (eepstatus site that is up)

i2p2www/pages/site/docs/applications/supported.html

@@ -597,7 +597,7 @@ Source code available.
   </li>
 
   <li>
-    <p><a href="http://{{ i2pconv('perv.i2p') }}/"><strong>{{ i2pconv('perv.i2p') }}</strong></a> —
+    <p><a href="http://{{ i2pconv('identiguy.i2p') }}/"><strong>{{ i2pconv('identiguy.i2p') }}</strong></a> —
     {% trans %}Dynamically updated eepsite index.{% endtrans %}
     <sup><em>[{{ _('service') }}]</em></sup></p>
   </li>

i2p2www/pages/site/faq.html

@@ -373,11 +373,11 @@ If this type of service is required, try <a href="https://www.torproject.org/">T
 
 <h3 id="down">{% trans %}Most of the eepsites within I2P are down?{% endtrans %}
 <span class="permalink">(<a href="#down">{{ _('link') }}</a>)</span></h3>
-<p>{% trans perv=i2pconv('perv.i2p') -%}
+<p>{% trans eepstatus='http://'+i2pconv('identiguy.i2p') -%}
 If you consider every eepsite that has ever been created, yes, most of them are down.
 People and eepsites come and go.
 A good way to get started in I2P is check out a list of eepsites that are currently up.
-<a href="http://{{ perv }}/stats.cgi">{{ perv }}</a> tracks active eepsites.
+<a href="{{ eepstatus }}">{{ eepstatus }}</a> tracks active eepsites.
 {%- endtrans %}</p>
 
 <h3 id="myeepsite">{% trans %}How do I set up my own eepsite?{% endtrans %}