4330bfbf87
Crypto requests packets are packets that can be routed by nodes in the DHT. In this pull request I have merged both Natping requests and friend requests into one common packet (Crypto request packets). Both these packets should now only be distinguishable by the size of the data in them to an outside observer for an example on how to send and recieve data with these packets see: friend_requests.c Note that these packets are prefixed with id 32 (friend request packets) which means this change is compatible with the currently running DHT bootstrap servers. Also changed small thing in DHT_test.c |
||
|---|---|---|
| auto_tests | ||
| cmake | ||
| core | ||
| docs | ||
| other | ||
| testing | ||
| .gitignore | ||
| .travis.yml | ||
| CMakeLists.txt | ||
| COPYING | ||
| INSTALL.md | ||
| README.md | ||
Project Tox, also known as Tox, is a FOSS (Free and Open Source Software) instant messaging application aimed to replace Skype.
With the rise of governmental monitoring programs, Tox aims to be an easy to use, all-in-one communication platform (including audio, and videochats in the future) that ensures their users full privacy and secure message delivery.
IRC: #tox on freenode, alternatively, you can use the webchat.
Website: http://tox.im
Developer Blog: http://dev.tox.im
Website translations: here
Qt GUI: see nurupo's repository
How to build Tox on Linux: YouTube video
How to use Tox on Windows: YouTube video
For Mac OSX read INSTALL.md
Objectives:
Keep everything really simple.
The Complex Stuff:
- Tox must use UDP simply because hole punching with TCP is not as reliable.
- Every peer is represented as a byte string (the public key of the peer [client ID]).
- We're using torrent-style DHT so that peers can find the IP of the other peers when they have their ID.
- Once the client has the IP of that peer, they start initiating a secure connection with each other. (See Crypto)
- When both peers are securely connected, they can exchange messages, initiate a video chat, send files, etc, all using encrypted communications.
- Current build status:
Roadmap:
- Get our DHT working perfectly. (Done, needs large scale testing though)
- Reliable connection (See Lossless UDP protocol) to other peers according to client ID. (Done, see
DHT_sendfiletest.cfor an example) - Encryption. (Done)
- [ ] Get a simple text only IM client working perfectly. (This is where we are)
- [ ] Streaming media
- [ ] ???
For further information, check our To-do list
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 without any account configuration will be capable of adding people to his friends list and start conversing with them. There are many so-called skype replacements and all of them are either hard to configure for the normal user or suffer from being way too centralized.