Recommend "Tox" over "qTox" #1569
@ -178,17 +178,22 @@
|
||||
|
||||
{%
|
||||
include cardv2.html
|
||||
title="qTox"
|
||||
title="Tox"
|
||||
image="/assets/img/svg/3rd-party/tox.svg"
|
||||
image-dark="/assets/img/svg/3rd-party/tox-dark.svg"
|
||||
description='Encrypted instant messaging and video calling software. Uses its <a href="https://toktok.ltd/spec.html"> own encryption protocol</a> that has not yet been officially audited by cryptographers.'
|
||||
|
||||
labels="warning:<a href=//tox.chat/download.html#warning>Experimental</a>:Encryption has not been audited by professional cryptographers|success:VoIP"
|
||||
website="https://tox.chat"
|
||||
forum="https://forum.privacytools.io/t/discussion-tox/2115"
|
||||
github="https://github.com/qTox/qTox"
|
||||
windows="https://tox.chat/download.html#oses"
|
||||
mac="https://tox.chat/download.html#oses"
|
||||
linux="https://tox.chat/download.html#oses"
|
||||
![]() Fair enough, I blame @dawidpotocki for his suggestion. Fair enough, I blame @dawidpotocki for his suggestion.
![]() I have reconsidered, we do provide information about support for when Netbsd and Openbsd has packages for other things so I don't see why not here. I have reconsidered, we do provide information about support for when Netbsd and Openbsd has packages for other things so I don't see why not here.
|
||||
freebsd="https://tox.chat/download.html#oses"
|
||||
openbsd="http://openports.se/search.php?so=tox"
|
||||
netbsd="http://pkgsrc.se/search.php?so=tox"
|
||||
fdroid="https://tox.chat/download.html#oses"
|
||||
googleplay="https://tox.chat/download.html#oses"
|
||||
![]() http? http?
![]() As @dawidpotocki said, it's not ideal, but there isn't really much of an alternative besides linking to CVS ie: https://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/net/toxcore/ Then if we do that we can't really link to more than one thing: https://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/net/utox/ Looks like OpenBSD doesn't have qtox packaged, guess we could link to utox, toxic is a command line client. https://wip.pkgsrc.org/cgi-bin/gitweb.cgi?p=pkgsrc-wip.git;a=tree;f=uTox-git As @dawidpotocki said, it's not ideal, but there isn't really much of an alternative besides linking to CVS ie:
https://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/net/toxcore/
http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/chat/toxcore/
Then if we do that we can't really link to more than one thing:
https://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/net/utox/
http://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/net/toxic
Looks like OpenBSD doesn't have qtox packaged, guess we could link to utox, toxic is a command line client.
https://wip.pkgsrc.org/cgi-bin/gitweb.cgi?p=pkgsrc-wip.git;a=tree;f=uTox-git
|
||||
ios="https://tox.chat/download.html#oses"
|
||||
%}
|
||||
|
||||
<h4>Worth Mentioning</h4>
|
||||
|
It seems qtox has their own organization though https://github.com/qTox should we link to both?
Uh. I would say no since we’re no longer recommending qTox specifically?
Yes, but qtox and utox are both "official" clients on https://tox.chat/download.html
That is why i removed the Github link, because we're linking to the downloads page anyway.
For Matrix’s GitHub link we list Riot for Web so I’m wondering if for consistency we stay with linking qTox here?
But in Matrix case, we only recommend Riot, in Tox case, we don't only recommend qTox.