{% extends "sat_website/category.html" %}

{% comment %}
SàT website: Salut à Toi's presentation website
Copyright (C) 2012  Jérôme Poisson (goffi@goffi.org)

This file is part of SàT website.

SàT website is free software: you can redistribute it and/or modify
it under the terms of the GNU Affero General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

Foobar is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU Affero General Public License for more details.

You should have received a copy of the GNU Affero General Public License
along with Foobar.  If not, see <http://www.gnu.org/licenses/>.
{% endcomment %}

{% load i18n %}
{% load staticfiles %}

{% block headline %}{% trans "Principles" %}{% endblock %}
{% block subtext %}{% trans "Some technical words to explain the project." %}{% endblock %}
{% block main_container %}

<div>
    {% trans "We usually present SàT as a multipurpose, multi frontend, free (libre) and decentralised communication tool... Let us explain what we mean:" %}
</div>

<div class="row">
    <h5 class="alert alert-success">
        <a name="multipurpose"></a>{% trans "Multipurpose" %}
    </h5>
    <div class="info">
        <p>
	    {% blocktrans with xmpp="<abbr title=\"eXtensible Messaging and Presence Protocol\">XMPP</abbr>" %}
	    Based on the powerful {{ xmpp }} standard, SàT can obviously be used for instant messaging and much more!
	    Blogging and microblogging, file sharing, games are other possible usage.... Using gateways, you can also communicate with other networks like IRC or StatusNet. It is also possible to redirect your XMPP messages to your email address, or to send an email that would be delivered on XMPP.
	    The "X" of XMPP stands for eXtensible: our features list is also extensible! Check the specifications page for a current status of what we've been doing.
	    {% endblocktrans %}
	    </p>
	    <p><a class="btn btn-default" href="specifications.html" role="button">{% trans "Specifications" %}</a></p>
    </div>
</div>    

<div class="row">
    <h5 class="alert alert-success">
         <a name="multifrontend"></a>{% trans "Multi frontend" %}
    </h5>
    <div class="info">
        <p>
	    {% blocktrans %}
	    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 does 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 develop a new frontend so don't hesitate to contact us!
	    {% endblocktrans %}
	    </p>
	    <p><a class="btn btn-default" href="frontends.html" role="button">{% trans "Frontends" %}</a></p>
    </div>
</div>    

<div class="row">
    <h5 class="alert alert-success">
         <a name="libre"></a>{% trans "Libre" %}
    </h5>
    <div class="info">
        <p>
	    {% blocktrans %}
	    We exclusively use and develop free and open-source software. It is not only free for you to get and run it, but you can also analyse it, modify it or 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 mentioned in the statutes of the association.
	    {% endblocktrans %}
	    </p>
	    <p><a class="btn btn-default" href="social_contract.html" role="button">{% trans "Social contract" %}</a></p>
    </div>
</div>    

<div class="row">
    <h5 class="alert alert-success">
         <a name="decentralised"></a>{% trans "Decentralised" %}
    </h5>
    <div class="info">
	    <p>
		    {% blocktrans with xmpp="<abbr title=\"eXtensible Messaging and Presence Protocol\">XMPP</abbr>" %}
		    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 service provider, and indirectly to all the rest of the world.
		    {% endblocktrans %}
		    <div class="thumbnail">
		        <img class="schema" src="{% static "images/decentralisation/1_physical.svg" %}" ><br/>
		    </div>
	    </p>
	    <p>
		    {% blocktrans %}
		    On the logical layer, you are directly connected to your usual "social network", and since it's centralised, all its users are directly connected to it: it can access and own all the data, it can unilaterally decide to censor or exclude a user. It has too much power.
	        {% endblocktrans %}
		    <div class="thumbnail">
		        <img class="schema" src="{% static "images/decentralisation/2_logical_centralised.svg" %}" ><br/>
		        <div class="caption">
		            {% trans "Centralised communication system on top of the physical layer - note that one user on the right who refuses to use such a system." %}
		        </div>
		    </div>
	    </p>
	    <p>
		    {% blocktrans %}
		    Now what if your usual "social network" is decentralised? The main difference is that there's not a single entity to manage all the connections and all the data, but a lot of them.
	        All the users are connected to the same network, but each of them can decide which server they want to connect to. As a result, the data and the network administration's tasks are shared between all the servers. Is it possible to do that on the Internet? Yes, this is how the email works! That's decentralisation.
		    {% endblocktrans %}
	        <div class="thumbnail">
	            <img class="schema" src="{% static "images/decentralisation/3_logical_decentralised.svg" %}" ><br/>
	            <div class="caption">
	                {% trans "Decentralised communication system on top the physical layer - the user on the right is still resisting." %}
	            </div>
	        </div>
	    </p>
	    <p>
		    {% blocktrans with xmpp="<abbr title=\"eXtensible Messaging and Presence Protocol\">XMPP</abbr>" federation_prefix='<a href="#federated">' federation_suffix='</a>' %}
		    Now what if you don't trust anybody? Then you are free to host your own server at home, via an association or in your work office. Is this possible too?! Yes, this is also how the email works! And this is what we did for our server libervia.org and without asking anybody's permission - the {{ xmpp }} interdomain {{ federation_prefix }}federation{{ federation_suffix }} makes it possible.
		    {% endblocktrans %}
	        <div class="thumbnail">
	            <img class="schema" src="{% static "images/decentralisation/4_logical_decentralised_self_hosting.svg" %}" >
	            <div class="caption">
	                {% trans "Decentralised communication system with self-hosting ability - the dot on the right is still an Internet user, but for the communication service it's both a user and a server." %}
	            </div>
	        </div>
	    </p>
	    <p>
		    {% blocktrans with contact_prefix='<a href="community.html">' contact_suffix='</a>' %}
		    So... in a nutshell: decentralisation is like how the email works. There are many servers, you can use the one you want and if you want to help the decentralisation, you can also add a new server by yourself. It requires some technical knowledge but it doesn't cost much and it allows more freedom. Feel free to {{ contact_prefix }}contact us{{ contact_suffix }} if you need some details!
		    {% endblocktrans %}
	    </p>
        <div class="alert alert-info">
	        {% blocktrans with article='<a href="http://networkcultures.org/unlikeus/resources/articles/what-is-a-federated-network/">Beyond distributed and decentralized: what is a federated network?</a>' %}
                <b>Note:</b> decentralisation, federation, distribution... these terms are not strictly defined. To debate about that is not the goal of this page, but we recommend you the reading of this article: {{ article }} It's not XMPP-specific but it's a good start.
			{% endblocktrans %}
		</div>
    </div>
</div>

<div class="row">
    <h5 class="alert alert-success">
         <a name="standard"></a>{% trans "Standard" %}
    </h5>
    <div class="info">
	    <p>
	        {% 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 %}
	    </p>
	    <p>
	        {% blocktrans with xmpp="<abbr title=\"eXtensible Messaging and Presence Protocol\">XMPP</abbr>" %}
	        As a consequence, SàT communicates with other {{xmpp}} projects and the way we "talk" together is fully documented. For the user, this means you can switch from one {{ xmpp }} client to another using the same account. This is taking the opposite direction to some proprietary and commercial networks which tend to lock their users up. Open your borders!
	        {% endblocktrans %}
	    </p>
    </div>
</div>

<div class="row">
    <h5 class="alert alert-success">
         <a name="multiplatform"></a>{% trans "Multiplatform" %}
    </h5>
    <div class="info">
        <p>
                {% blocktrans %}Since its beginning, the SàT project was made with other platforms in mind. It's only available 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 %}
        </p>
    </div>
</div>

{% endblock %}