Sound design!

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).

Thanks!

Tox Dev Talks – #3

(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 Saturdays at 16:00 UTC.)

In this week’s meeting, as usual, we discussed a variety of topics, which have been summarized below.

(Edited 2015/08/30: a few factual corrections were made. Apologies for letting them slip past editing -ak)

  • Binaries
    • Package signing
      • Jenkins will handle it
      • Possibility of making Jenkins push notify on changes
  • Policy
    • #tox-dev
      • We discussed how much off-topic discussion and other noise we are willing to allow on #tox-dev
      • Possibly enabling colors for improved build info
      • nurupo expressed concern of color misuse
    • Social media
      • We reminded the managers of each Tox-related account of their responsibilities
      • Blog
        • Social media will now link to EVERY blog post
        • GSoC mentors should come up with a GSoC blog post
  • Our website
    • installgen2 is working on redesigning tox.chat from scratch, this will take 3-7 days to complete
  • ToxAV
    • Mannol has said there will be more commits this (2015-08-29) weekend
  • New groupchats
    • JFreegman is still waiting on irungentoo to implement the difficult codebase changes
  • Core and client updates
    • qTox
      • Zetok will be tagging qTox issues
    • uTox
      • in-progress UI redesign
      • New groupchats once ToxAV gets merged, and the refactor in that branch gets merged
  • Other developments
    • nurupo is working on fixing bugs and refactoring code in code base of GSoC project he mentored
    • codedust is developing https://github.com/codedust/WebTox – a web based tox client

Tox Dev Talks – #2

(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 Saturdays at 16:00 UTC.)

Tox Dev Talks are back after a week-long hiatus due to scheduling difficulties. As we had irungentoo on hand, we spent a lot of time on core issues. Here’s a bit of what was discussed.

  • Tox core
    • Offline messaging
      • The student who was implementing it disappeared. irungentoo will be taking over if he has time.
    • Friendly names / DNS replacement?
      • No real solution was brought up that would be better than what we have now. That said, DNS will remain optional for clients and not a Tox core feature.
    • irungentoo’s to-do list
      • Improve file transfers.
      • Write proper documentation for the code.
      • In general, fix bugs and/or finish some features that aren’t done.
    • New groupchats
      • Currently stalled due to requiring some significant core changes.
    • A/V revamp
      • Currently waiting on client support and some important bug fixes.
  • Packaging
    • qTox binaries are finally available again (Windows and Linux static)
    • An APT repository will be coming soon.
  • Client news
    • µTox
      • New A/V is complete and waiting on aforementioned bug fixes.
      • grayhatter is currently working to improve the UI.
    • qTox
      • New A/V is almost done, audio works, webcam works, streaming desktop doesn’t work and the button functionality still needs to be implemented.
      • tux3 is no longer dead, and has given access to the main repository to DaSpirit and others while he catches up on things.
    • Antox
      • There is currently a naming dispute with the original author.
        • The current developer, subliun, will continue using the Antox name.
  • Other things worth mentioning
    • As some people aren’t happy with the design of tox.chat, installgen2 is going to redesign the site. He will show what he came up with at the next meeting.

If you want to participate in the next Tox Dev Talk, feel free to drop in next week. We hope to keep a stable schedule, but if that doesn’t happen, we will let you know on the calendar.

Regarding irungentoo’s Indiegogo Campaign

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.

 

Tox Dev Talks – #1

(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.

Progress updates and to-do:

  • installgen2 (Web)
    • ToxKek – Fix connection and crash bugs, add mobile frontend design, add avatars, add file transfers, add ToxDNS support, add groupchat support, add memes, and add remote server support. (ToxKek is an early-stage HTML/JS Tox client.)
    • Tox.Party – Add Tox3 support and get https certificate.
    • Tox Wiki – Add missing pages and clean up mess
  • chuongv (iOS)
    • Antidote: Implement video calls for this week.
  • subliun (Android)
    • Antox: working on encrypted profile support, fixing some bugs, and getting ready for av support.
    • New ToxDNS host is toxme.io
  • Impyy (C#/Windows)
    • SharpTox – finish new groupchat bindings, write documentation for both new av api and new groupchat api.
  • oranges (Build infrastructure)
    • Jenkins is up and building libraries, some clients are building.
    • Waiting on client devs for some of the other clients.

We hope to see more of the same kind of constructive discussion, and more developers in attendance next week!

Current Situation

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)