2ba967d078
Previously, toxcore would send a kill control to the friend only if the file control was valid. Determining which file transfer is used does not depend on the specific file control. We can always kill it in that case. Also, added some logging for file control logic, since there is no other feedback on error (failure of the file control handler is swallowed). |
||
|---|---|---|
| auto_tests | ||
| build | ||
| cmake | ||
| dist-build | ||
| docs | ||
| m4 | ||
| other | ||
| super_donators | ||
| testing | ||
| toxav | ||
| toxcore | ||
| toxdns | ||
| toxencryptsave | ||
| .gitignore | ||
| .travis.yml | ||
| autogen.sh | ||
| circle.yml | ||
| CMakeLists.txt | ||
| configure.ac | ||
| COPYING | ||
| DONATORS | ||
| INSTALL.md | ||
| libtoxav.pc.in | ||
| libtoxcore.pc.in | ||
| Makefile.am | ||
| README.md | ||
| tox.spec.in | ||
Current build status: 
Current Coverage: 
Website | Wiki | Blog | FAQ | Binaries/Downloads | Clients | Compiling
IRC Channels: Users: #tox@freenode, Developers: #toktok@freenode
Toxcore Development Roadmap
This Roadmap is somewhat tentative, but should give you a good idea of where we're going, and where we've been.
Currently unsorted, the following is intended to function as a discussion guide to developers/contributors.
In Progress
- Toxcore
- 100% unit testing
- Make ToxAV stateless
- Allow a single toxcore instance to handle multiple keypairs (or 'clients')
- Consistent naming scheme throughout toxcore
- Make toxcore stateless
- Messenger
- Improve group chat implementation
- Improve A/V implementation
- Multiple device support
Done
- Create Toxcore
- Create DHT
- Create Onion
- Implement Crypto
- Create Messenger
Q&A:
What is Tox?
Tox is a fully encrypted, censor resistant, private, distributed network library with a focus on personal communications.
No, really, what's Tox?
It's a VERY secure Instant Messenger that supports Text, Audio/Video calls, group chats, audio group chats, and file transfers. There's dozens, but our advantage is we put security first, from day 1. We didn't decide to add it in after.
What are your goals with Tox?
We want Tox to be as simple as possible while remaining as secure as possible.
Documentation:
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.