vikarti.anatra/safing-web
1
0
Fork 0
mirror of https://github.com/safing/web synced 2025-09-02 02:59:03 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Clarify we mean plain Tor in a passage of the comparison blog

Browse source
This commit is contained in:
davegson 2021-04-13 19:34:10 +02:00
parent 32ecad9942
commit 28f6e1f8fc
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
_publications/2020-01-22-how-the-spn-compares-to-tor.md
View file

@ -38,7 +38,7 @@ This is achieved by routing connections through a circuit. This splits the full
![SPN core](https://safing.io/assets/img/spn/spn-core-web.png)
When the connection arrives at the last server of the circuit it still has to travel to the desired website. With Tor, this may lead to a slower Internet experience. As an example, a person located in Europe loading a European website may receive a circuit exiting in the US. This means the connection has to cross the Atlantic twice (EU -> US -> EU). After a circuit with Tor is established all your other connection will use the same route. A circuit change normally occurs every 10 minutes.
When the connection arrives at the last server of the circuit it still has to travel to the desired website. With Tor, this may lead to a slower Internet experience. As an example, a person located in Europe loading a European website may receive a circuit exiting in the US. This means the connection has to cross the Atlantic twice (EU -> US -> EU). After a circuit with plain Tor is established all your other connection will use the same route. A circuit change normally occurs every 10 minutes.
With the SPN however, every connection is calculated individually and leaves the network as near to the destination as possible. This means: