What is Reddit's opinion of qTox?

From 3.5 billion Reddit comments

Not sure if compiling Windows applications in Wine counts as cross-compiling.

In any case, I'm have been cross-compiling Windows Qt5 applications on Linux nativly, without using Wine, just fine for many years now, since Qt5's release probably. Here is a build script I wrote for cross-compiling qTox project and all of its dependencies, including QtBase part of Qt5.

Are you absolutely positive that you can't build your app without using Wine? Do you want to specifically use MSVC compiler or your app depends on QtWebEngine, which is probably a pain to cross-compile?

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.

> Tox is practically abandonware which is not surprising from a 4chan project.

If you look at the repositories (e.g. https://github.com/qTox/qTox or https://github.com/TokTok/c-toxcore) you cannot really speak of abandonware.

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.

I wouldn't mind helping and/or learning exercises, but I feel incapable of doing challenges at this point. Very much a C++ noob and haven't completed the ebook. My biggest achievement so far is getting basic voids to work in FLTK, and I'm struggling with callbacks between voids.

I also know some python and some bash. If you'd still be interested, I can help with what little I know. I prefer qTox for communication, can PM you my ID.

This is where qTox packaging is being worked on by myself and /u/sudden6: https://build.opensuse.org/package/show/home:qTox/qtox. Those packages you found looks like they're all generated from here, but I'm not sure if that's a guarantee in the future, or if the site is just finding all packages named "qtox-alpha". The build scripts are forked from Aantonbatenev's repo, and are currently hosted at http://github.com/anthonybilinski/tox.pkg/ but will hopefully be moved into the qTox project in the near future. Aantonbatenev was the previous package maintainer that I mentioned in my first comment, who had stopped updating the releases in his repo for a while. There's a few github issues regarding packages, a recent one here: https://github.com/qTox/qTox/issues/4816 which will probably have more frequent updates and more info than reddit.

Note that those packages you found are currently very unstable. I wouldn't install them outside of a test environment until there's an official announcement that they're ready.

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!

Qtox does all that, even if screen sharing was a bit obscure years ago. Qtox won't work on iOS but there is an Android release. Big advantages: no server required, easy to use, secure, open source.

It would depend on your client. For qTox, see the avoiding censorship part of our user manual. Custom bootstrap nodes was only (re-)added since the last release, so to get that editable json file you would need to update to a nightly build. If you want to stick with the same version, you could update the json file yourself in the source directory and recompile.

To run a bootstrap node, see the instructions for the bootstrap daemon.

Note that your bootstrap node will need to connect to other nodes, so if it's being blocked from connecting as well it won't be much help.

After you connect once, DHT nodes will automatically be saved in your Tox profile, so you should be able to connect again without using your custom bootstrap node. Those nodes are just regular other users, so if you wait long enough between uses they might have all restarted their clients or gone offline, in which case you'll need the bootstrap daemon again.

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

Good news is there hasn't been any major CVE or vulnerabilities that we know of and it uses NaCl which is historically pretty solid and hard to get wrong. The bad news is the creator of wireguard posted a drama thread explaining a theoretical KCI vunerability to the protocol. (Though WireGuard has also not been formally audited and is not eligible for government use).

It's weakest link was centralized services such as Toxme.io which was used to shorten user IDs in qTox, however that service has since been shutdown and the network runs fine using the normal user IDs.

That said, it's a great decentralized IM software and I still use it. I consider it superior to XMPP which requires servers, and we all know servers log and are prone to a central point of failure, even in federated models.

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

https://github.com/qTox/qTox/issues/5520

qTox is a fully distributed chat/voice/video cross platform C++ program, using the Qt framework. We could use your help and have a small helpful group of maintainers.

​

If you want to test it out you can contact me at tox:AC18841E56CCDEE16E93E10E6AB2765BE54277D67F1372921B5B418A6B330D3D3FAFA60B0931

qTox is a fully distributed chat/voice/video cross platform program, using the Qt framework. We could use your help and have a small helpful group of maintainers.

If you want to test it out you can contact me at tox:AC18841E56CCDEE16E93E10E6AB2765BE54277D67F1372921B5B418A6B330D3D3FAFA60B0931

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.

I think the GitHub instructions are written for Fedora 25, but they worked for me on 26.

You probably already did all of this, but here's what I did. I hope that it might help. (I'm using Fedora 26 with XFCE4.)

Install free and nonfree repositories.

qtox dependencies

dnf install ffmpeg-devel \ gtk2-devel \ libXScrnSaver-devel \ libtool \ openal-soft-devel \ openssl-devel \ qrencode-devel \ qt-creator \ qt-devel \ qt-doc \ qt5-linguist \ qt5-qtsvg \ qt5-qtsvg-devel \ qtsingleapplication \ sqlcipher \ sqlcipher-devel \ libsq3-devel

toxcore dependencies

dnf install libtool \ autoconf \ automake \ check \ check-devel \ libsodium-devel \ opus-devel \ libvpx-devel

Download toxcore

wget https://github.com/TokTok/c-toxcore/archive/master.zip

Download qTox

wget https://github.com/qTox/qTox/archive/master.zip

Compile and install toxcore

unzip toxcore and cd into directory.

autoreconf -if ./configure make -j$(nproc) sudo make install echo '/usr/local/lib/' | sudo tee -a /etc/ld.so.conf.d/locallib.conf sudo ldconfig

Compile qtox

unzip qtox and cd into directory.

export PKG_CONFIG_PATH="$PKG_CONFIG_PATH:/usr/local/lib/pkgconfig" cmake . make

After it's finished, take the newly created "qtox" binary and move it into /home/$USER/bin

Create the bin directory if necessary. After this you're done.

Well, the toxcore still in development and clients as qTox and uTox still in development too. But they give a warn that the core wasn't audited yet.

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.