toxcore

e proof of work needed to calculate for each message is not optimized. Attackers have written clients in C to take advantage of Python's weakness to flood the network. Until the main client is also written in C, and the PoW algorithm is designed to take advantage of it, I'm sure there will be other network flooding problems on the Bitmessage network. uTox and Venom seem to be the most used Tox clients, but I have had trouble getting uTox and Venom to actually work with video. Further, when both parties are using uTox, in some situations, while my video and audio testing work fine, the other party cannot see me or cannot hear me. I use uTox for signing PGP keys, so I've used it a number of times, and it's probably 50% at this point when it Just Works. Both Bitmessage and Tox, however, have not had a security audit of the code. Also, OTR and PGP have proven to be reliable, stable, secure, and enjoy large communities. With PGP, you can end-to-end encrypt your email, and with OTR, you can end-to-end encrypt your live chat, although video and audio are not supported. It doesn't matter about your email or chat provider either, and software exists for Windows, Mac OS X, GNU/Linux, and BSD for both. Freenode also offers TLS-supported IRC servers, including hidden servers on Tor. Although Tor has been getting some press lately of the FBI successfully taking down pedophiles and drug markets, these are all due to mistakes by the end users, and not insecurities with Tor itself. So, Freenode on Tor might be a good one-off solution, where you just need to chat quickly, without registering for accounts, and staying hidden. See https://freenode.net/irc_servers.shtml#tor Finally, if you're not familiar with the EFF Secure Messaging Scorecard, you might want to take a look at it: https://www.eff.org/secure-messaging-scorecard. There are a lot of clients there, including the various security margins of each, so that might be of interest.

orks, "works without license" are considered copyrighted work of the author (e.g. anonymous user on linked /gd/ board). 3. Creative Commons licenses are also incompatible with their choice of software licensing, GPLv3+,[4] which means they cannot legally redistribute current logos under the current licenses with Tox software even if they were copyright holders to those logos.[5] As far as I know, the logos are already being redistributed with the software. 4. The documentation also cannot be legally redistributed with the software, and in theory nobody outside the project has practical freedoms to modify the documentation.[6] "I'm le troll! :-)" was most likely added by the developers. 5. Because of the above mentioned issues, Tox cannot be accepted to Debian GNU/Linux repositories because of DSFG guidelines. 6. The above mentioned issues also create false advertising; "Tox is both free for you to use, and free for you to change. You are completely free to both use and modify Tox."[7] 7. A developer quit the project because of other serious issues in the project.[8][9] The developer criticized the design of DHT (distributed hash table) used to find users, which leaked a lot of data about users. There's a large reddit thread about these DHT issues somewhere too, but I seem to be unable to find it myself right now. Fortunately, the leak was patched a long time ago. Unfortunately, the patch was a large hack which the Tox developers solved by reinventing the wheel and reimplementing Tor onion routing. 8. I haven't verified this (so don't count on me), but the Tox core (or core + clients?) is now ~100k lines of code. It's not entirely lightweight per se, which was one of the initial goals as far as I remember. 9. Another minor thing that upset me was that during Tox's conference talk (forgot which conference, but it was related to YouBrokeTheInternet), the speaker forgot to introduce himself and what he was doing. This probably led to some confusion. 10. Possibly controversial too, but the first radio talk show Tox was introduced in was... could I say, maybe slightly cringeworthy. Or something. See it for yourself.[10] Sorry if I went a little bit too political, knowing the rules. I wanted to point out these issues to let you know how everyone involved in the project can be a help. [1]: https://rbt.asia/g/thread/40445107#p40449131 - you can scroll down and read the replies too [2]: https://commons.wikimedia.org/wiki/Commons:Deletion_requests... [3]: https://commons.wikimedia.org/wiki/Commons:Undeletion_reques... [4]: https://github.com/irungentoo/toxcore/blob/master/COPYING [5]: https://www.gnu.org/licenses/license-list.html#ccbysa [6]: https://github.com/Tox/Docs/issues/7 [7]: https://tox.im/ [8]: http://www.tox-chat.com/2013/08/tox-developer-fed-up-quits.h... [9]: https://github.com/irungentoo/toxcore/issues/493 [10]: https://www.youtube.com/watch?v=IdR3SVcBbq0 Disclaimer: I'm not the author of any of the links above. It's what I have gathered from numerous discussion threads Tox has had on 4chan.

ux_i686.tar.xz If you use an operating system other than windows or linux (OSX or android) or want to try other Tox clients, see this page: https://wiki.tox.im/Binaries Project links: Official Tox website: https://tox.im uTox Github: https://github.com/notsecure/uTox toxcore Github: https://github.com/irungentoo/toxcore Other links: qTox Github: https://github.com/tux3/qTox Antox Github: https://github.com/Astonex/Antox Note about adding friends in Tox: in the settings area of uTox you can find your Tox ID, and you give that out to your friends so that they can add you. To solve the inconvenience of sharing long IDs, Tox also supports "DNS names", for example "groupbot@toxme.se". You can register your own @toxme.se name on toxme.se Tox is alpha software, bugs are expected. Feel free to post any questions or feedback or visit us on IRC: #tox on freenode.

//github.com/Jman012/Toxicity) • an Android client (https://github.com/Astonex/Antox) • an ncurses-based terminal client for Unix-likes ( https://github.com/Tox/toxic ) The Tox core has been shared all over the internet by inspired enthusiasts, and has drawn the attention of many developers. However, the clients haven't received nearly the same amount of publicity, and their developers need help to bring easy, secure communication to the masses. And since the core is a simple protocol library with an API (and with bindings available for many other languages), you can start your own client too. If you fancy yourself more of a low-level programmer, help with the core is always appreciated: https://github.com/irungentoo/ProjectTox-Core Developers are always present over at #tox-dev on freenode. For the API: http://api.libtoxcore.so/ Thank you for your time, - https://tox.im/