The future of online communications.
Go to file
iphydf 15cb426166
Make toxcore code C++ compatible.
It is still C code, so still compatible with C compilers as well. This
change lets us see more clearly where implicit conversions occur by
making them explicit.
2016-09-24 21:53:50 +01:00
auto_tests Make toxcore code C++ compatible. 2016-09-24 21:53:50 +01:00
build Fix include paths 2016-01-01 20:28:48 -05:00
cmake Make toxcore code C++ compatible. 2016-09-24 21:53:50 +01:00
dist-build Removed unnecessary parameters 2014-08-25 10:00:09 +04:00
docs Ensure that all TODOs have an owner. 2016-09-16 12:06:02 +01:00
m4
other Make toxcore code C++ compatible. 2016-09-24 21:53:50 +01:00
super_donators Added my pixfile! 2015-12-12 20:40:57 +01:00
testing Make toxcore code C++ compatible. 2016-09-24 21:53:50 +01:00
toxav Make toxcore code C++ compatible. 2016-09-24 21:53:50 +01:00
toxcore Make toxcore code C++ compatible. 2016-09-24 21:53:50 +01:00
toxdns Make toxcore code C++ compatible. 2016-09-24 21:53:50 +01:00
toxencryptsave Do not use else after return. 2016-09-02 11:02:56 +01:00
.gitignore Add and use CMake build script 2016-08-12 01:13:11 +01:00
.travis.yml Allow the OSX build to fail on travis. 2016-09-22 14:46:51 +01:00
autogen.sh
CMakeLists.txt Make toxcore code C++ compatible. 2016-09-24 21:53:50 +01:00
configure.ac Add debugging option to autotools configuration 2016-09-07 17:25:48 -04:00
COPYING Removed the unused autotools files 2015-10-05 15:18:55 -07:00
DONATORS If we receive a packet from a node we are searching for, ping it. 2015-12-08 15:43:03 -05:00
INSTALL.md docs(INSTALL.md): update instructions for Gentoo 2016-08-20 19:44:50 +01:00
libtoxav.pc.in
libtoxcore.pc.in Build system fixes. 2014-12-18 10:04:31 -05:00
Makefile.am Fixed make dist. 2015-06-24 21:03:16 -04:00
README.md Update readme with tentative roadmap, removed old todo.md 2016-08-14 12:03:26 -07:00
tox.spec.in

Project Tox


Current build status: Build Status Current Coverage: Coverage Status

Website | Wiki | Blog | FAQ | Binaries/Downloads | Clients | Compiling

IRC Channels: #tox@freenode, #toktok@freenode

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.

What are your goals with Tox?

We want Tox to be as simple as possible while remaining as secure as possible.

Toxcore 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

  • 100% unit testing
  • Make toxcore stateless
  • Allow a single toxcore instance to handle multiple keypairs
  • Implement usable group chats
  • Improve A/V implementation
  • Multiple device support
  • Consistent naming scheme throughout toxcore

Done

  • Create Toxcore
  • Create DHT
  • Create Onion
  • Implement Crypto
  • Create Messenger

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.