privacyguides.org/i18n/it/advanced/communication-network-types.md

title	icon
Tipi di reti di comunicazione	material/transit-connection-variant

Esistono diverse architetture di rete comunemente usate per trasmettere messaggi tra le persone. Queste reti possono fornire garanzie di privacy diverse, motivo per cui vale la pena considerare il modello di minaccia quando si decide quale app utilizzare.

Messaggistica istantanea consigliata{.md-button}

Reti centralizzate

{ align=left }

I servizi di messaggistica centralizzati sono quelli in cui tutti i partecipanti si trovano sullo stesso server o rete di server controllati dalla stessa organizzazione.

Alcuni servizi di messaggistica self-hosted consentono di configurare il proprio server. Il self-hosting può fornire ulteriori garanzie di privacy, come l'assenza di log o l'accesso limitato ai metadati (dati su chi parla con chi). I servizi centralizzati self-hosted sono isolati e tutti devono essere sullo stesso server per comunicare.

Vantaggi:

• Le nuove funzionalità e le modifiche possono essere implementate più rapidamente.
• È più facile iniziare e trovare contatti.
• Gli ecosistemi con le caratteristiche più mature e stabili sono più facili da programmare in un software centralizzato.
• I problemi di privacy possono essere ridotti quando ci si affida a un server in self-hosting.

Svantaggi:

• Possono includere controllo o accesso limitato. Questo può includere cose come:
• Il divieto di connettere client di terze parti alla rete centralizzata che potrebbero fornire una migliore personalizzazione o esperienza. Spesso definito nei Termini e condizioni d'uso.
• Documentazione scarsa o assente per gli sviluppatori di terze parti.
• La proprietà, la politica sulla privacy e le operazioni del servizio possono cambiare facilmente quando un'unica entità lo controlla, compromettendo potenzialmente il servizio in un secondo momento.
• Il self-hosting richiede impegno e conoscenza di come impostare un servizio.

Reti federate

{ align=left }

Federated messengers use multiple, independent, decentralized servers that are able to talk to each other (email is one example of a federated service). Federation allows system administrators to control their own server and still be a part of the larger communications network.

When self-hosted, members of a federated server can discover and communicate with members of other servers, although some servers may choose to remain private by being non-federated (e.g., work team server).

Vantaggi:

• Allows for greater control over your own data when running your own server.
• Allows you to choose whom to trust your data with by choosing between multiple "public" servers.
• Often allows for third-party clients which can provide a more native, customized, or accessible experience.
• Server software can be verified that it matches public source code, assuming you have access to the server or you trust the person who does (e.g., a family member).

Svantaggi:

• Adding new features is more complex because these features need to be standardized and tested to ensure they work with all servers on the network.
• Due to the previous point, features can be lacking, or incomplete or working in unexpected ways compared to centralized platforms, such as message relay when offline or message deletion.
• Some metadata may be available (e.g., information like "who is talking to whom," but not actual message content if E2EE is used).
• Federated servers generally require trusting your server's administrator. They may be a hobbyist or otherwise not a "security professional," and may not serve standard documents like a privacy policy or terms of service detailing how your data is used.
• Server administrators sometimes choose to block other servers, which are a source of unmoderated abuse or break general rules of accepted behavior. This will hinder your ability to communicate with members of those servers.

Reti peer-to-peer

{ align=left }

P2P messengers connect to a distributed network of nodes to relay a message to the recipient without a third-party server.

Clients (peers) usually find each other through the use of a distributed computing network. Examples of this include Distributed Hash Tables (DHT), used by torrents and IPFS for example. Another approach is proximity based networks, where a connection is established over WiFi or Bluetooth (for example, Briar or the Scuttlebutt social network protocol).

Once a peer has found a route to its contact via any of these methods, a direct connection between them is made. Although messages are usually encrypted, an observer can still deduce the location and identity of the sender and recipient.

P2P networks do not use servers, as peers communicate directly between each other and hence cannot be self-hosted. However, some additional services may rely on centralized servers, such as user discovery or relaying offline messages, which can benefit from self-hosting.

Vantaggi:

• Minimal information is exposed to third-parties.
• Modern P2P platforms implement E2EE by default. There are no servers that could potentially intercept and decrypt your transmissions, unlike centralized and federated models.

Svantaggi:

• Reduced feature set:
• Messages can only be sent when both peers are online, however, your client may store messages locally to wait for the contact to return online.
• Generally increases battery usage on mobile devices, because the client must stay connected to the distributed network to learn about who is online.
• Some common messenger features may not be implemented or incompletely, such as message deletion.
• Your IP address and that of the contacts you're communicating with may be exposed if you do not use the software in conjunction with a VPN or Tor. Many countries have some form of mass surveillance and/or metadata retention.

Instradamento anonimo

{ align=left }

A messenger using anonymous routing hides either the identity of the sender, the receiver, or evidence that they have been communicating. Ideally, a messenger should hide all three.

There are many different ways to implement anonymous routing. One of the most famous is onion routing (i.e. Tor), which communicates encrypted messages through a virtual overlay network that hides the location of each node as well as the recipient and sender of each message. The sender and recipient never interact directly and only meet through a secret rendezvous node so that there is no leak of IP addresses nor physical location. Nodes cannot decrypt messages, nor the final destination; only the recipient can. Each intermediary node can only decrypt a part that indicates where to send the still encrypted message next, until it arrives at the recipient who can fully decrypt it, hence the "onion layers."

Self-hosting a node in an anonymous routing network does not provide the hoster with additional privacy benefits, but rather contributes to the whole network's resilience against identification attacks for everyone's benefit.

Vantaggi:

• Minimal to no information is exposed to other parties.
• Messages can be relayed in a decentralized manner even if one of the parties is offline.

Svantaggi:

• Slow message propagation.
• Often limited to fewer media types, mostly text, since the network is slow.
• Less reliable if nodes are selected by randomized routing, some nodes may be very far from the sender and receiver, adding latency or even failing to transmit messages if one of the nodes goes offline.
• More complex to get started, as the creation and secured backup of a cryptographic private key is required.
• Just like other decentralized platforms, adding features is more complex for developers than on a centralized platform. Hence, features may be lacking or incompletely implemented, such as offline message relaying or message deletion.

--8<-- "includes/abbreviations.it.txt"