| auto_tests | ||
| build | ||
| dist-build | ||
| docs | ||
| m4 | ||
| other | ||
| super_donators | ||
| testing | ||
| toxav | ||
| toxcore | ||
| toxdns | ||
| toxencryptsave | ||
| .gitignore | ||
| .travis.yml | ||
| autogen.sh | ||
| configure.ac | ||
| COPYING | ||
| DONATORS | ||
| INSTALL.md | ||
| libtoxav.pc.in | ||
| libtoxcore.pc.in | ||
| Makefile.am | ||
| README.md | ||
| tox.spec.in | ||
With the rise of government surveillance programs, Tox, a FOSS initiative, aims to be an easy to use, all-in-one communication platform that ensures full privacy and secure message delivery.
Website | Wiki | Blog | FAQ | Binaries/Downloads | Clients | Compiling
IRC Channels: #tox@freenode, #tox-dev@freenode
The Complex Stuff:
UDP vs. TCP
Tox must use UDP simply because hole punching with TCP is not as reliable. However, Tox does use TCP relays as a fallback if it encounters a firewall that prevents UDP hole punching.
Connecting & Communicating
Every peer is represented as a byte string (the public key [Tox ID] of the peer). By using torrent-style DHT, peers can find the IP of other peers by using their Tox ID. Once the IP is obtained, peers can initiate a secure connection with each other. Once the connection is made, peers can exchange messages, send files, start video chats, etc. using encrypted communications.
Current build status: 
Q&A:
What are your goals with Tox?
We want Tox to be as simple as possible while remaining as secure as possible.
Why are you doing this? There are already a bunch of free Skype alternatives.
The goal of this project is to create a configuration-free P2P Skype replacement. “Configuration-free” means that the user will simply have to open the program and will be capable of adding people and communicating with them without having to set up an account. There are many so-called Skype replacements, but all of them are either hard to configure for the normal user or suffer from being way too centralized.