template/faq.html.j2


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65

{% extends "common/base.j2" %}
{% block body_content %}
<div class="container-fluid">
  <div class="container text-center">
    <h1>FAQs<h1>
    <h2><i>This page is a work-in-progress</i></h2>
  </div>
  </div>
<div class="container">
  <article>
    <section>
      <h3>{{ _("Is GNUnet ready for use on production systems?") }}</h3>
      <p>
	{% trans %}
	A: GNUnet is still undergoing major development. It is largely not yet ready
  for usage beyond developers. Your mileage will vary depending on the
  functionality you use, but you will always likely run into issues with
  our current low-level transport system. We are currently in the process of
  rewriting it (Project &quot;Transport Next Generation [TNG]&quot;)
	{% endtrans %}
      </p>
    </section>
    <section>
      <h3>{{ _("Is GNUnet build using distributed ledger technologies?") }}</h3>
      <p>
	{% trans %}
	A: No. GNUnet is a new network protocol stack for building secure,
  distributed, and privacy-preserving applications.
  While a ledger could be built using GNUnet, we currently have no plans in
  doing so.
	{% endtrans %}
      </p>
    </section>
    <section>
      <h3>{{ _("I receive many &quot;WARNING Calculated flow delay for X at Y for Z&quot;. Should I worry?") }}</h3>
      <p>
	{% trans %}
	A: Right now, this is expected and a known cause for high
	latency in GNUnet.  We have started a major rewrite to address
	this and other problems, but until the Transport Next
	Generation (TNG) is ready, these warnings are expected.
	{% endtrans %}
      </p>
    </section>
    <section>
      <h3>{{ _("Is there a graphical user interface?") }}</h3>
      <p>
	{% trans %}
	A: gnunet-gtk is a separate download. The package
	contains various GTK+ based graphical interfaces, including a
	graphical tool for configuration.
	{% endtrans %}
      </p>
    </section>
  </article>
<!--
<h2>{{ ("Q?") }}</h2>

<h2>{{ ("Q?") }}</h2>

<h2>{{ ("Q?") }}</h2>
-->

</div>
{% endblock body_content %}