As I’m sure you are all aware, Tox has grown tremendously in terms of UI and usability, yet client sounds are still somewhat lacking.

We are looking for people to help out with creating sounds for clients (ringtones, notification sounds, etc). No programming knowledge is required. Just join us in #tox-dev on Freenode (here is webchat for those of you without an IRC client).

irungentoo (our main toxcore developer) has started a personal fundraising campaign that would allow him to dedicate a month of full time work to Tox development. Although this has already been posted on Twitter, reddit and IRC, we have decided to give it a mention here as well, both in order to support our fellow developer, and to clear up some misunderstandings.

Quite a few people have asked if this is an official Tox fundraising campaign. It is not. This is something that irungentoo is doing on his own, separate from the project; all raised funds will go directly to him to be used however he sees best fit. We mentioned in our previous blog post that we wouldn’t be taking any donations as a project until we have set up a proper organization with an emphasis on transparency and protection of assets. This is still the case, however we also mentioned that individual developers are free to take personal donations, which is what this is.

We apologize if this has caused any confusion, and hope that this has sufficiently cleared up any misunderstandings.

(If you don’t already know, Tox Dev Talks is a series of weekly meetings that bring the Tox developer community together to share ideas, progress, and miscellaneous chatter. They take place every Saturday at 03:00 UTC.)

This week’s Tox Dev Talk turned out exceptionally well, especially as it was the first one. The primary focus was on mobile issues; here is a summary of what was discussed.

How do we deal with doze mode in Android M?

Do we use GCM?

Is a “passive mode” for toxcore so we can reduce battery and data usage possible?

How do we deal with backgrounding restrictions on iOS?

Possible solution: use VoIP sockets.

No concrete decisions as of now.

qTox: as tux3 has been absent for a while, the main repo might be moved to DaSpirit’s fork.

As many of you in the Tox community have likely already heard, a serious situation was brought to our attention which has forced the Tox development team to disassociate itself from the Tox Foundation, along with its sole board member, Sean Qureshi (aka Stqism, aka AlexStraunoff, aka NikolaiToryzin). We learned by Sean’s own admission that he “took a loan against the Tox Foundation”, and used the entirety of the foundation’s funds on personal expenses completely unrelated to the project. He did not inform anyone about his actions prior to taking them, then proceeded to disappear for weeks once we found out, ignoring our attempts to contact him and get an explanation.

The exact amount that he took is unknown due to his having complete control over our finances, but it is in the low-thousands. This fund regrettably included a small amount of donation money, but was primarily made up of money that we received by participating in Google Summer of Code last summer.

First, we want to sincerely apologize to the community and take responsibility. We could not have predicted that something like this would happen, but we certainly could have handled our finances in a more responsible and transparent manner. While our development team consists of many skilled programmers and designers, none of us are experienced in business or financial matters. This led us to put too much trust and power into the hands of a single person, who turned out to be just the sort of person who would take advantage of such a situation. We can blame no one but ourselves for this.

Unfortunately, Sean refuses to take responsibility for what he has done, and seems to carry the attitude that what he did was perfectly acceptable. Despite our having spent a great deal of time and effort trying to engage with him, giving him opportunities to pay us back and redeem himself (which is part of the reason why we have waited this long to make an official post about it), he has shown no remorse for his actions, and continues to hold some of our infrastructure “hostage”. This includes the tox.im, toxme.se, and libtoxcore.so domains. For this reason, we have have also been forced to disassociate ourselves with the aforementioned domains and begin again from scratch with a new domain, tox.chat.

In spite of the damage that has been done—which we do not wish to understate—we’d like to look on the bright side of things and consider this a very expensive lesson learned in project management, and life in general. We’ve lost some money, but we’ve gained a ton of insight. We have also been lucky enough to have a few long-standing members of the community step up and help us out with things like server management, and we should have everything back to normal in a short while, with a stronger and better equipped team than before.

As far as finances go, we are not going to repeat the same mistakes twice. We will not be taking any official donations* until we have set up a proper organization with an emphasis on transparency and protection of assets (more details on this at a future date).

In the mean time, we hope that you will continue to support us, if not financially, then in spirit. Despite all of this drama, we have not lost sight of our vision to provide secure, private communications for everyone. Tox development hasn’t had so much as a hiccup in the midst of all this; our second run at Google Summer of Code is going better than our first, and the number of enthusiastic developers who share our vision continues to grow.

Thank you for your understanding and continued support.

* If you still want to give personal donations to individual developers, most of us have bitcoin wallets or paypal accounts and can be reached in IRC (#tox and #tox-dev @ freenode)