The future of online communications.
Go to file
Coren[m] a0f08839bd Main: Eliminate TOX_ENABLE_IPV6 (then always on), CLIENT_ONETOONE_IP (then always off).
Additionally (besides cleanups):

network.h/tox.h:
- WIN32: fix a strange sa_family_t definition
- WIN32: define EWOULDBLOCK to WSAEWOULDBLOCK
- WIN32: kill macro for an existing function (IN6_ADDR_EQUAL)

network.c:
- use EWOULDBLOCK instead of EAGAIN (same value, but EWOULDBLOCK is more "popular")
- new_networking(): only try to enable IPv4-in-IPv6 if it's not already enabled per default
- inet_ntop()/inet_pton(): WIN32: remove partial initializers in favor of a simple memset()
- ip_equal(): WIN32: use an existing function
- logging: networking_wait_execute(): only dump result if not timeout
- logging: loglogdata(): kill an unused variable

LAN_discovery.c:
- send_broadcasts(): re-enabled, can only support IPv4 by principle, split into fetch_broadcast_info() (to fetch the addresses once) and send_broadcasts() (actual sending)

DHT.c:
- DHT_load_state_callback(): enclosed a fprintf(stderr, ...) into #ifdef DEBUG

Lossless_UDP.c:
- change_handshake(): harden against strange sa_family_t definitions

Messenger.c:
- logging: fix ID to string conversion

util.c:
- logging: eliminate a signed-warning
2013-10-20 16:56:12 +02:00
auto_tests Broken *_wait() into *_wait_prepare() and *_wait_execute() 2013-10-05 12:53:54 +02:00
build tox A/V: integration of A/V code into tox 2013-10-13 16:40:15 +02:00
docs tox A/V: integration of A/V code into tox 2013-10-13 16:40:15 +02:00
m4 tox A/V: integration of A/V code into tox 2013-10-13 16:40:15 +02:00
other Main: Eliminate TOX_ENABLE_IPV6 (then always on), CLIENT_ONETOONE_IP (then always off). 2013-10-20 16:56:12 +02:00
testing Main: Eliminate TOX_ENABLE_IPV6 (then always on), CLIENT_ONETOONE_IP (then always off). 2013-10-20 16:56:12 +02:00
tools tox A/V: integration of A/V code into tox 2013-10-13 16:40:15 +02:00
toxcore Main: Eliminate TOX_ENABLE_IPV6 (then always on), CLIENT_ONETOONE_IP (then always off). 2013-10-20 16:56:12 +02:00
toxmsi Toxmsi build fix 2013-10-14 11:01:54 +04:00
toxrtp tox A/V: RTP/MSI implementation 2013-10-13 16:16:47 +02:00
.gitignore Add .dirstamp to gitignore 2013-09-01 21:43:46 +03:00
.travis.yml tox A/V: integration of A/V code into tox 2013-10-13 16:40:15 +02:00
AUTHORS Implemented autotools based build scripts 2013-08-24 03:25:07 +03:00
autogen.sh Some configuration/build fixes, so building basicaly everything else than the library can be disabled 2013-10-07 02:01:16 +02:00
ChangeLog Implemented autotools based build scripts 2013-08-24 03:25:07 +03:00
configure.ac tox A/V: integration of A/V code into tox 2013-10-13 16:40:15 +02:00
COPYING Licenced the code under the GPL for now. 2013-06-26 15:02:42 -04:00
INSTALL Some configuration/build fixes, so building basicaly everything else than the library can be disabled 2013-10-07 02:01:16 +02:00
INSTALL.md Update INSTALL.md 2013-09-28 09:22:20 +01:00
libtoxcore.pc.in Let clients include <tox/tox.h> 2013-08-24 04:41:35 +03:00
Makefile.am tox A/V: integration of A/V code into tox 2013-10-13 16:40:15 +02:00
NEWS Implemented autotools based build scripts 2013-08-24 03:25:07 +03:00
README Implemented autotools based build scripts 2013-08-24 03:25:07 +03:00
README.md Updated README. 2013-09-08 16:08:33 -04:00

Project Tox 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: Build Status

TODO:

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.

Documentation: