Hello everyone! Some of you have requested us to make a status update, so here we go.
Quite a bit has happened with Linux packaging this month.
Packages for Ubuntu Yakkety (16.10) are available. Our packaging team prepared for the new Ubuntu release beforehand, packaging clients for Ubuntu Yakkety while it was still in the beta, so all of our clients were available for Ubuntu Yakkety on the day of its release.
Packages for Ubuntu Vivid (15.04) and Ubuntu Wily (15.10) were removed. We have mentioned in the previous blog post that we would like to remove them at some point, as Ubuntu Vivid and Ubuntu Wily have reached EOL, and addition of packages for the new Ubuntu release served as that point.
Empty package repositories were removed. These repositories existed because we considered packaging for them at one point, but because of cross-compilation complexity and lack of required dependencies on older distribution versions we decided not to package for them. For example, we didn’t have any packages for armel architecture and for Ubuntu Trusty release. This caused some confusion as some Tox users would see these package repositories available and add them, thinking that they contained Tox clients, when in fact they were empty.
qTox packages were removed from all package repositories. In the previous blog post we mentioned that Encrypt was going to take over the maintenance of qTox packages, but because of personal reasons he is not able to volunteer as much of his free time as he hoped he could. We decided that it’s a bad idea to serve unmaintained packages to our users, so we had to remove them. Although there are no more qTox packages in our https://pkg.tox.chat package repository, you can still get qTox packages from the openSUSE Build Service package repository, which qTox developers advertise as the recommended place to get qTox packages, and which is linked on the Download page of our website.
Antidote, the Tox client for iOS developer by dvor, is now on the App Store. Get it, try it out and send your feedback to Antidote’s developer by either writing a review on the App Store or submitting a bug report/feature request to the issue tracker!
Not much has happened with irungentoo/toxcore. Incorrect permissions set by tox-boostrapd and bug in LAN discovery code were fixed. A bug in development branch which resulted in a crash of Toxcore was fixed.
A lot of internal changes were done in TokTok/c-toxcore in order to make it more testable and to improve the code quality in general. Compliance with the C standard was improved. Callbacks thoughout Toxcore have become stateless (ToxAv is comign next), which will help with bindings for the languages with managed memory. ABI backward compatibility support was improved , . Toxcore was made compatible with C++, allowing us to use C++ compiler to catch some type casing issues , . The existing test suite was improved . Group chat API was rewritten to follow the guidelines of the current API. Generally a lot of other code improvements happened.
To allow easier transition of clients from irungentoo/toxcore to TokTok/c-toxcore, 0.0.1 version of TokTok/c-toxcore was released, which would make it possible for clients to support both Toxcores at the same time. µTox nightly has already transitioned to using TokTok/c-toxcore, which means that the next release of µTox will be using TokTok/c-toxcore. Antidote, Antox and qTox also have plans on switching to TokTok/c-toxcore.
Support for UPnP and NAT-PMP is coming to Toxcore soon. UPnP and NAT-PMP are port forwarding mechanisms, they allow programs to automatically setup a port forwarding rules on users’ routers without users having to manually do this. This solves the issue of routers not allowing someone you have not communicated with before to send you data, improving Tox’s networking performance, as the hole punching workaround would not be needed to get around this anymore.
That’s all that has happened during last couple months, until the next update!
Thank you for your hard work.
That’s the right update format! Thanks
Great job as usual :)
I have a question (maybe stupid) do you use (or will used) Rust (mozilla’s new languages) ?
Im not dev at all, but I read I lot of good thinks about it.
Have a good day !
Hello. Thank you.
I also have one more question. The multidevice implementation also gives a new spin to offline messaging problem, does it?
Even if we store a message on DHT, it will only be sent to one client, and the other clients won’t get it until that one client is started, do I understand it correctly?
(I know, this may be no place for technical discussons, but i’m a lazy fsck)
dr.Equivalent :: you do understand it correctly, but we’re aware of this issue, and I already have a tentative solution to this problem. So ideally if everything is done in the order I plan for it to be. It’ll never be an issue.
If you’re interested in the technical solution I have planned, come find me on irc.freenode.net/toktok
>The multidevice implementation also gives a new spin to offline messaging problem, does it?
Yes, it does.
>Even if we store a message on DHT, it will only be sent to one client, and the other clients won’t get it until that one client is started, do I understand it correctly?
There is no offline messaging design spec of any kind yet, so I’m not sure why assume that the message will be sent only to one client. It depends on how offline messages will be designed and how they work with multidevice.
I wanted to (respectfully) share some thoughts I am having as a potential new user, visiting this site and blog for the first time…
The homepage looks awesome.
Showcasing download links to multiple clients is confusing (detox, utox, qtox, ricin, etc). Focusing on one client for the initial download-and-go would help to get me started more easily.
Screenshots of the preferred client for each environment would be terrific.
A comparison chart comparing Tox with similar applications would be great. Based on my own investigation Tox looks superior to Ring, Telegram, WhatsApp and other alternatives…
>Focusing on one client for the initial download-and-go would help to get me started more easily.
Making the website focus on a single client is a bit problematic as clients are developed by separate groups of developers who often rival between each other, so choosing one client over another would put one client in a big advantage while others at a big disadvantage, removing all the competition between the clients. Having information of how to get started with each of the clients somewhere on the website or the wiki is a good idea though.
Comments are closed.