Mercurial > sat_legacy_website

comparison templates/sat_website/principles.html @ 53:84c2e20d3de1

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
include some corrections suggested by Goffi
author souliane <souliane@mailoo.org>
date Tue, 05 May 2015 09:47:55 +0200
parents 10cdc1fbc4c7
children 0d20fb28c32e
comparison
equal deleted inserted replaced
52:cc099372a9ac 53:84c2e20d3de1
30 <div> 30 <div>
31 {% trans "We usually present SàT as a multipurpose, multi frontend, libre and decentralised communication tool... let us explain what we mean." %} 31 {% trans "We usually present SàT as a multipurpose, multi frontend, libre and decentralised communication tool... let us explain what we mean." %}
32 32
33 <div class="row"> 33 <div class="row">
34 <h5 class="alert alert-success"> 34 <h5 class="alert alert-success">
35 <a name="multipurpose">{% trans "Multipurpose" %}</a> 35 <a name="multipurpose"></a>{% trans "Multipurpose" %}
36 </h5> 36 </h5>
37 <div class="info"> 37 <div class="info">
38 <p> 38 <p>
39 {% blocktrans with xmpp="<abbr title=\"eXtensible Messaging and Presence Protocol\">XMPP</abbr>" %} 39 {% blocktrans with xmpp="<abbr title=\"eXtensible Messaging and Presence Protocol\">XMPP</abbr>" %}
40 Based on the powerful {{ xmpp }} standard, SàT can obviously be used for instant messaging... and much more! 40 Based on the powerful {{ xmpp }} standard, SàT can obviously be used for instant messaging... and much more!
46 </div> 46 </div>
47 </div> 47 </div>
48 48
49 <div class="row"> 49 <div class="row">
50 <h5 class="alert alert-success"> 50 <h5 class="alert alert-success">
51 <a name="multifrontend">{% trans "Multi frontend" %}</a> 51 <a name="multifrontend"></a>{% trans "Multi frontend" %}
52 </h5> 52 </h5>
53 <div class="info"> 53 <div class="info">
54 <p> 54 <p>
55 {% blocktrans %} 55 {% blocktrans %}
56 SàT has been developped since the beginning with an idea in mind: it should be useable from the command line, with a console or desktop interface, from a web browser... The backend of the software manages the communication with your XMPP server and do most of the processing. On top of that, you are free to use the frontend of your choice. If you would like to help the project, a great thing would be to developp a new frontend: don't hesitate to contact us! 56 SàT has been developped since the beginning with an idea in mind: it should be useable from the command line, with a console or desktop interface, from a web browser... The backend of the software manages the communication with your XMPP server and do most of the processing. On top of that, you are free to use the frontend of your choice. If you would like to help the project, a great thing would be to developp a new frontend: don't hesitate to contact us!
60 </div> 60 </div>
61 </div> 61 </div>
62 62
63 <div class="row"> 63 <div class="row">
64 <h5 class="alert alert-success"> 64 <h5 class="alert alert-success">
65 <a name="libre">{% trans "Libre" %}</a> 65 <a name="libre"></a>{% trans "Libre" %}
66 </h5> 66 </h5>
67 <div class="info"> 67 <div class="info">
68 <p> 68 <p>
69 {% blocktrans %} 69 {% blocktrans %}
70 We exclusively use and developp free and open-source software. It is not only free for you to get and run it, but you can analyse it, modify it, redistribute it. Since this is enough to free a program but not the person who uses it, we wrote a social contract - a moral engagement with the user - that is also mentionned in the Statutes of the association. 70 We exclusively use and developp free and open-source software. It is not only free for you to get and run it, but you can analyse it, modify it, redistribute it. Since this is enough to free a program but not the person who uses it, we wrote a social contract - a moral engagement with the user - that is also mentionned in the Statutes of the association.
74 </div> 74 </div>
75 </div> 75 </div>
76 76
77 <div class="row"> 77 <div class="row">
78 <h5 class="alert alert-success"> 78 <h5 class="alert alert-success">
79 <a name="decentralised">{% trans "Decentralised" %}</a> 79 <a name="decentralised"></a>{% trans "Decentralised" %}
80 </h5> 80 </h5>
81 <div class="info"> 81 <div class="info">
82 <p> 82 <p>
83 {% blocktrans with xmpp="<abbr title=\"eXtensible Messaging and Presence Protocol\">XMPP</abbr>" isp="<abbr title=\"Internet Service Provider\">ISP</abbr>"%} 83 {% blocktrans with xmpp="<abbr title=\"eXtensible Messaging and Presence Protocol\">XMPP</abbr>" isp="<abbr title=\"Internet Service Provider\">ISP</abbr>"%}
84 This is the most complicated aspect to understand, yet a crucial one. Being based on {{ xmpp }}, SàT is immediately decentralised (federated). But what does it mean? To get this point, we need to imagine the Internet as a set of layers. To make it easier, let's say there are only two layers: the physical and the logical one. On the physical layer, you are directly connected to your {{ isp }}, and indirectly to all the rest of the world. 84 This is the most complicated aspect to understand, yet a crucial one. Being based on {{ xmpp }}, SàT is immediately decentralised (federated). But what does it mean? To get this point, we need to imagine the Internet as a set of layers. To make it easier, let's say there are only two layers: the physical and the logical one. On the physical layer, you are directly connected to your {{ isp }}, and indirectly to all the rest of the world.
137 </div> 137 </div>
138 </div> 138 </div>
139 139
140 <div class="row"> 140 <div class="row">
141 <h5 class="alert alert-success"> 141 <h5 class="alert alert-success">
142 <a name="standard">{% trans "Standard" %}</a> 142 <a name="standard"></a>{% trans "Standard" %}
143 </h5> 143 </h5>
144 <div class="info"> 144 <div class="info">
145 <p> 145 <p>
146 {% blocktrans with xsf="<abbr title=\"XMPP Standards Foundation\">XSF</abbr>" %}Using a standard protocol is a key point: it's robust, widely used, tested and well documented. Every change is discussed publicly, there are debates on the best way to achieve goals and the {{ xsf }} is the guarantor of the evolution and stability of the protocol.{% endblocktrans %} 146 {% blocktrans with xsf="<abbr title=\"XMPP Standards Foundation\">XSF</abbr>" %}Using a standard protocol is a key point: it's robust, widely used, tested and well documented. Every change is discussed publicly, there are debates on the best way to achieve goals and the {{ xsf }} is the guarantor of the evolution and stability of the protocol.{% endblocktrans %}
147 </p> 147 </p>
153 </div> 153 </div>
154 </div> 154 </div>
155 155
156 <div class="row"> 156 <div class="row">
157 <h5 class="alert alert-success"> 157 <h5 class="alert alert-success">
158 <a name="standard">{% trans "Multiplatform" %}</a> 158 <a name="multiplatform"></a>{% trans "Multiplatform" %}
159 </h5> 159 </h5>
160 <div class="info"> 160 <div class="info">
161 <p> 161 <p>
162 {% blocktrans %}Since its begining, the SàT project was made with other platforms in mind. It's only avaible on GNU/Linux so far (except of course Libervia, the web interface, which is available from any modern browser), but other platforms are planned.{% endblocktrans %} 162 {% blocktrans %}Since its begining, the SàT project was made with other platforms in mind. It's only avaible on GNU/Linux so far (except of course Libervia, the web interface, which is available from any modern browser), but other platforms are planned.{% endblocktrans %}
163 </p> 163 </p>