What are
/r/projecttox's
favorite Products & Services?
From 3.5 billion Reddit comments
The most popular Services mentioned in /r/projecttox:
qTox
Tox
Protox
Antox
Matrix.org
uTox
F-Droid
Toxygen
Syncthing
Liberapay
Fossil
Bitmessage
Ricochet
PRISM Break
telehash
The most popular Android Apps mentioned in /r/projecttox:
The most popular reviews in /r/projecttox:
> I've commented/write-a-code/report-issue many things to Tox client development. One years had passed, and I decide to dump Tox from my clients.
Because you didn't publish your github account, I can't check if this is true. But I just assume what you are saying is wrong, because I haven't seen your username in any tox repo.
> This isn't a toxcore issue... find a different place to spread FUD (Quoting grayhatter)
This is the most important thing about it. The software has a clear purpose, a clear direction. You are encouraged to participate, but nobody is entitled to solve anything. This is open source. Your help is appreciated, your suggestions and criticism are noticed, but complaints and "I am dumping this shit!" are not intimidating anybody. They don't matter in the long run.
> Let's face it. One year passed and you still didn't solve: "Contacts know your IP address(not anonymous)." "If you disable UDP and use TCP, middle node know 'who you are' and 'who you are talking to'." "If you use 'offline message', your message will save to node server, allowing it to know from, to, and what." "Tox client never reconnect itself; other clients show offline while they're actually online." et cetra.
Software evolves slowly if not enough people are working on it. Tox seems to continue evolving. If that's not fast enough for you, I encourage you to watch the rust compiler progress. It's quite refrehsing.
> Tox is NOT a decentralized software like https://tox.chat/ claim which is a biggest lie on earth.
In fact, the first issue you linked to provides much better arguments for and against your claims than I could ever make.
So, TL; DR: criticism is okay, but nobody is entitled to act because of it.
Edit: fixed simple spelling errors.
That list kind of sucks though.
Not enough focus on the code being open or not.
That the code was audited or the security design is documented doesn't mean anything if you can't check if the code that was audited is actually the code being used or if it's even a proper implementation of what is documented.
What does "Encrypted" mean, does rot13 count as encryption? what about 256bit RSA?
Does paying someone random 10$ who doesn't know programming to look at my code and say he audited it enough to get a green checkmark on the audit column?
I think https://prism-break.org does a much better job than that eff list.
Are you saying that just the fact that there was recently a blacklist feature added (https://github.com/qTox/qTox/pull/4610), that allows an end-user to stop messages from a different user in a group chat somehow aids in government censorship? This blacklist is not managed by qTox and is purely defined by the end user. It is shipped empty and not updateable from network. If you think that a user being able to chose to not receive messages is censorship, the same thing could be achieved by them just leaving the group and removing the contact as a friend. Someone being able to voluntarily chose to not communicate with someone else is not censorship.
If you think there's a problem is either design or implementation in this feature or any other, please point it out and it will be addressed (that's the beauty of open-source code), but accusing developers of being government shills with no evidence isn't productive.
I assume you are referring to one of the social network share buttons on https://tox.chat ? If so feel free to make an issue on the Website Issue Tracker and a developer will get back to you.
It wouldn't really be reverse engineering since the code is freely availably.
It looks like Toxygen is using something to load the native library, maybe research the CDLL thing a bit
We are not. The current problem is that we do not have a non-profit organisation, which would allow us to handle donations in a transparent way. Because of that we don't accept donations. As you can read on https://tox.chat/about.html:
> Tox is developed by volunteer developers who spend their free time on it, believing in the idea of the project. Tox is not a company or any other legal organization. Currently we don't accept donations as a project, but you are welcome to reach out to developers individually.
We definitely need financial support though. If we had enough money we could use it to hire part time developers to work on important features like: offline messaging, multi device support, improved group chats. Maybe Liberapay could be a solution to this?
Not necessarily, deterministic key generation is useful for doing things like this -> https://bitmessage.org/wiki/Decentralized_Mailing_List
Or even this -> https://en.bitcoin.it/wiki/Deterministic_wallet
Although I've come to realize the goals in Tox versus other decentralized communication platforms are very different, so it wouldn't be of much value on the Tox platform.
The issue with stuff like Pidgin and Instabird is that you're making insecure protocols an option, basically forcing a mess of options and protocols at users who ideally wouldn't know a thing or two about security or protocols.
This results in a complicated initial setup procedure that scares away people, and a cluttered UI that confuses others.
With Tox it's just run and you're in, secure, easy to use, and good looking.
And besides, we have a default client.
I don't know what client you are using. If you are talking about qTox it doesn't have a dark theme at the moment and it has been requested in the past (https://github.com/qTox/qTox/issues/1639). I managed to change it in the code, but it requires editing of a lot of files. I'm planning to work on this in the future and add a dark theme to qTox.
qTox lost our package maintainer ~8 months ago. I'm slowly restarting packaging, but I don't think it's stable enough to recommend yet.
For now, compiling qTox is your best option. There are instructions here: https://github.com/qTox/qTox/blob/master/INSTALL.md
I'll update once packaging is ready.
To immediately get it working, I would suggest disabling all of your antivirus software simultaneously.
Long term, it would be very helpful if you would contact the developers of each of your antivirus programs and let them know they're wrongly flagging qTox. Most antivirus providers have a way to do this.
A qTox-specific list of problematic antivirus software and contact links is maintained here:
https://github.com/qTox/qTox/wiki/Problematic-antiviruses
Thanks for reporting your issue!
Other Tox clients can work in those conditions, but reconnecting isn't very fast (at least for me). It might be a problem with Antox. You could post your issue here and see if they fix it: https://github.com/Antox/Antox/issues
Antox works well from what I have heard. Your issue sounds like a problem with internet connection. You get disconnected from the network, so it shows your friends as offline (because you can't connect to them). It might also have something to do with this bug: https://github.com/Antox/Antox/issues/477. You can try TRIfA too, but it's not an official client.
try this, i'm not sure as i have not done it myself: download https://www.archlinux.org/packages/core/i686/gcc/ extract and run
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/your/custom/path/
pointing to the lib folder you extracted.
No. Even the Tor guys have been fighting the great firewall of china for years and will probably never truly win. And, unlike Tox, they actively try to hide their traffic instead of just encrypting it.
Tor is currently your best bet. Look into https://ricochet.im/
Well... in my tests, Tox used a lot of battery & data on the phone and wasn't 100% reliable with message delivery or Video/Voice Chat. Add relliable (semi) offline messages to that and I'd call Tox a viable replacement for other messengers. That is the requirement to be taken seriously. After that is done, I see a lot of nice applications.
There are a lot of other nice applications besides those I already listed. Basically everything that currently uses a server to connect a few people together could be replaced with something tox-based. Examples like Teamviewer without a central server. Dropbox like file syncing (more like syncthing without the need for the central server). Clouldless contact and calendar sync from phone to PC. Do you use DynDNS to get the IP of your home router (for VPN or whatever)? Connect via Tox instead. Everything IOT does with a central server, replace with Tox.
I'm not sure if the Tox devs share that vision, but it'd be awesome. Some services are looking into solving similar problems. Integrate Tox as a service into the OS, so all those apps don't have to solve the problems themselves. Also saves a lot of bandwith & battery if all apps can use the same DHT connection.
Actually ratox was a step into that direction, but it's not very active. I know some problems are not easily solvable and IOT over Tox will probably need some kind of gateway for energy reasons. Maybe Tox is not the best solution for all those problems. It'd just be awesome if one DHT+Hole-punching protocol could be used for close to all purposes.
You could make a LIberapay team. Users can donate to the team, and individual devs can receive money from them. But Tox never actually needs to hold the money.
https://liberapay.com/about/teams
See https://liberapay.com/F-Droid-Data/ for an example.
I take donations for developing Android Tox client.
I don't understand how c-toxcore funding works but it should have donations so we can have active developers. That's my opinion.
> Is it Tox? It's off Google Play and the iOS reviews look botted af
Tok is a chinese Tox client which uses custom toxcore with patches which add questionable centralized features. Tok doesn't publish its patched version of toxcore and Tok developers hide that Tok is a Tox client.
from Wikipedia: >Active (violates GPLv3, uses unmaintained fork of c-toxcore, potentially unsafe to use)
I'm developing a new Tox client: https://gitlab.com/Monsterovich/protox
Toxygen seems have alpha state implementation client.
https://github.com/toxygen-project/toxygen/releases
​
use Join Group Chat to try join Public Tox Chat (ID: 6ED792C73729B93AA24F8C0044CD527ED048A26444F4418C8CE18CA85742EB1A)
Well there is another problem in such case. As I understand mobile app is going to consume battery and network bandwidth a lot since there is no support for push notification. Some details: https://github.com/Antox/Antox/issues/6 https://github.com/irungentoo/toxcore/issues/1251
One of the neatest ways of using Tox on the command line would be to run Weechat, and use the Tox plugin for it. Run it yourself and decided; Weechat is pretty lightweight.
When you add a friend, they will appear as offline in your friends list (little red circle next to name) until they accept the friend request. You can currently only send a file to them when you see them online, but text message will allow you to queue them locally, and will sit with a little spinner on the right side, which will be delivered when you see them come online. This is probably what you're seeing.
If you want to test, you can try adding me AC18841E56CCDEE16E93E10E6AB2765BE54277D67F1372921B5B418A6B330D3D3FAFA60B0931
We have a FAQ as part of the qTox Wiki, but neither seem to cover the general use case like this. It would be good to add some general "first use" kind of documentation.
>I have been concerned lately that tox development has been lagging since qtox has not had an update release since July 2018.
qTox just released https://github.com/qTox/qTox/releases/tag/v1.17.2
qTox had spell checking added since its last release in https://github.com/qTox/qTox/pull/5149, but only for osx and Linux, so nightlies on those systems should have spell checking. Note that nightlies are generally not recommended for general use, and especially unstable at the moment.
Windows spellchecking is being introduced in https://github.com/qTox/qTox/pull/5319, but ran into some problems.
My recommendation is to wait for release 1.17.0 for spellchecking on osx/Linux or maybe 1.18.0 for Windows.
It is not currently possible to do anything toxme.io related besides registration from qTox. I'm not aware of anyone currently working on the issue https://github.com/qTox/qTox/issues/5014 - so it's not likely it will be implemented very soon. It's not implemented because there are 580 qTox issues, most of which have higher user impact and there is limited dev effort.
> if its already a key feature of the android (antox) client
I honestly can't find it in Antox, but if it's there it's because of different project priorities.
additional: its better to always keep your debian package clean:
​
Fix qTox Package Errors in Debian Buster
As far as I know, all the Tox projects use github.
The primary and currently most popular implementation of the core protocol, implemented in C:
toxcore: https://github.com/TokTok/c-toxcore/
One of the most popular clients for desktop:
qTox: https://github.com/qTox/qTox/
I don't think there are any, but most clients will sign their source packages, and verifying the signature is both an authenticity as well as integrity check.
qTox, for eg. : https://github.com/qTox/qTox/releases
1) did you try to run simple_make.sh? https://github.com/qTox/qTox/blob/master/simple_make.sh
2) you seem to install from source, but have you already built and installed toxcore successfully? Instructions are further down the file
qTox v1.15.0 is released you can download it from github. It includes the latest toxcore (v0.2.2) with the security patch, so make sure to update.
> I can not get the code they submitted. qTox is open source. Any code submitted is freely available, including this change. You can get all of the source submitted, and see the entire review process here: https://github.com/qTox/qTox/pull/4610.
The dot does become green after the period of idle activity ends. If not, that is a bug and it should be reported to qTox's issue tracker preferably with a log file attached.
Yeah. It's kinda hard with people like /u/GrayHatter who prefer to hide code for multiple devices that other people possibly could help with.
With that being said..
>I really wish devs would make multi device a bigger priority (…)
I really with there were more people helping, rather that trying to tell other people what their priorities should be.
https://github.com/qTox/qtox-irc-logs/blob/master/2016/06/%23qtox_20160603.log.txt#L122,L123
In other words, if you're interested in feature X, please, do help with feature X. And yes, there are plenty of things one could do aside from code to help.
Jami works in a P2P manner, and is able to send/forward messages and history between users, online and offline. It uses swarms, though, and has some sort of server component (not sure how much work this does). Swarms probably work something like torrenting, with Alice and Bob's encrypted conversation, or even Bob's DMs to Emma, being held by nearby IPs (i.e. Nicole, and a bunch of randos), and forwarded to Emma when she reconnects.
A friend of mine has a bot project that runs on a raspberry pi and receives and forwards messages on his behalf, giving him pseudo-offline messaging capabilities.
Such capabilities will probably come after multiple-devices-per-account, as Tox seems to care about who can hold the encrypted message data for forwarding (e.g. you don't want Hackerman McHackerface to built a special bot that dumps encrypted conversation data he receives for forwarding for mining through later; this is a possible risk with Jami).
I think the solution for Tox is 1) multi-device accounts. 2) a simple routing server mode for the Tox client, so you can install tox on an RPi or always-online machine and use it purely for blindly forwarding conversations for you. These could also be integrated into the DHT or custom DHT lists (currently, Tox depends on a handful of often-hardcoded "initial connection" servers, which aren't easy to run yourself, or easy to add to clients if you do run one yourself) 3) A way of marking devices/contacts as "trusted" to route conversation data for you. Your own devices, using the same account, are automatically "trusted" to forward conversation data whenever they're online. Trusting other people's devices could be automatic, e.g. when you accept someone's "friend request", that marks them as "trusted" to forward your encrypted messaging data (even to other people).
I've never used TAILS, but I think the easiest way might be to click on the link for the "qTox AppImage", from the Tox downloads page:
https://tox.chat/download.html
Then just double click.
But the more correct way might be to use the repositories. But you will have to look into this yourself. AFAIK, tails is based on Debian, and it does have qTox in it's repositories, but then again, not in 'stable'.
https://tracker.debian.org/pkg/qtox
Imagine it as working similar to teamspeak, irc, discord, or slack. You dont need any technical knowledge to setup a room.
Its decentralized, sure it isnt pure p2p, but its not one server to rule them all.
Just look at the main page for a small diagram and explanation.
Also, this