tox / tox.chat Goto Github PK

There are several issues with the current Download page

1. When a you open the page, the first thing you see is "Thanks for downloading!", which confuses people as they thing that the download process has already started, when in fact nothing is being downloaded.
2. The page categorizes all clients by a platform, displaying a|long|bar|separated|list|of|downloads|for|each|client|as|well|as|alternative|download|methods under the platform, for example, here is Linux platform
   
3. The Debian/Ubuntu instructions use lsb_release -cs in them, which causes issues for people using Debian-/Ubuntu- derived distributions who don't know what lsb_release -cs does. e.g. on a Linux Mint system, lsb_release -cs would print "sarah", "rosa", "rebecca", "qiana" or "rafaela", on Trisquel it would print "belenos", on Elementary OS "freya", etc. Even on Debian/Ubuntu it could print "wheezy", "precise" and "trusty", depending on what version of Debian/Ubuntu you use. None of these outputs of lsb_release -cs would work though, since the package repo supports only "jessie", "stretch", "sid", "vivid", "wily" and "xenial", as the text on that page says (well, it wasn't updated to mention Xenial yet), but no one reads the small text and just copy-pastes the instructions into the terminal, seeking help later on IRC, GitHub Issues, etc.
4. The .html page and os-detection .js duplicate download links, which means that a link might get fixed in one but forgotten in another.

Proposed ways to resolve the issues

1. Just change "Thanks for downloading!" to something else or remove it. Something along the lines of "We detected your OS as Windows, here are all Windows downloads ... (see downloads for all platforms)" or "We couldn't detect your OS. Here are downloads for all platforms." for when JS is enabled and "Here are downloads for all platforms" for when JS is not enabled would be great.

2. Instead of categorizing by platform, categorize by client and have a list of platforms under each.
   
   This will keep things simple and the bar|list will be very short, as there is a finite number of platforms (in contrast to the number of Tox clients).

3. Well, first of all, every client should have its own modal-view, and for Linux modal-view, each client should list only distributions and versions of distributions the client is available for, to the point that the user has to select specific version of a distribution to get the instructions without lsb_release -cs (lsb_release -cs should be replaced by the appropriate string for the selected distribution) for Debian/Ubuntu. e,g, to get a qTox for Debian Stretch, one would find qTox on the Download page then go though Linux -> Debian -> Debian Stretch menu to finally get the instructions and the instructions will say stretch instead of lsb_release -cs.

   Here are some quality MS Paint mock-ups to get the idea : P

   When user clicks on "Linux" under "qTox", user is presented with distributions this specific client is available at (i.e. different clients can have different list of distributions).

   

   When a user selects Debian, user is presented a choice of specific Debian Release.

   

   When user selects Debian Stretch, user is presented with instructions specific for Debian Stretch

   

   Note the stretch being in place of where we currently have lsb_release -cs. and note the specialized apt-get install instruction for that specific client, i.e. a Linux modal-view for uTox would say apt-get install utox.

   It would be great to be able to utilize the Jinja2 template engine we use for our website and describe a client on Download page as a python dictionary, with a list of supported platforms, list of supported Linux distributions, list of supported versions (assuming the distributions' instructions are version-dependent, otherwise this set is not needed) of each of the supported distributions, specify package name for each distribution, specify kind of downloads available for Windows (32-bit, 64-bit, etc), download links, and so on. Just create a Client python dictionary and have single template generating code which looks at every Client dictionary and generates the appropriate html, e.g. a Linux modal-view for qTox which lists only distributions qTox is available on and only versions of distributions it's available on, etc.
   Just an example of such a Client dictionary list to get the idea across

   clients =
   [
       {
           'name' : 'qTox',
           'platforms' : ['Windows', 'Linux', 'OS X'],
           'Windows' :
           {
               'stable' :
               {
                   '32-bit' : 'https://example.org/qtox-stable-32.exe',
                   '64-bit' : 'https://example.org/qtox-stable-64.exe'
               },
               'nightly' :
               {
                   '32-bit' : 'https://example.org/qtox-stable-32.exe',
                   '64-bit' : 'https://example.org/qtox-stable-64.exe'
               }
           },
           'Linux' :
           {
               'Debian' :
               {
                   'tox.chat\'s pacakges' : 
                   {
                       'stable' :
                       {
                           'Jessie'  : { 'packages' : ['qtox']},
                           'Stretch' : { 'packages' : ['qtox']},
                           'Sid'     : { 'packages' : ['qtox']}
                       },
                       'nightly' :
                       {
                           'Jessie'  : { 'packages' : ['qtox']},
                           'Stretch' : { 'packages' : ['qtox']},
                           'Sid'     : { 'packages' : ['qtox']}
                       }
                   },
                   'qTox OBS packages' : 'https://software.opensuse.org/download.html?project=home%3Aantonbatenev%3Atox&package=qtox'
               },
               'Ubuntu' :
               {
                   ...
               }
           }
       },
       {
           'name' : 'Toxic',
           ...
       },
       ...
   ]

   You can see from that example of what a Client dictionary might look like that I have split Debian for qTox into "tox.chat's packages" and "qTox OBS packages" options, and the "tox.chat's packages" option is further split into "nightly" and "stable", which means that the html generating code should be flexible enough to be able to generate as many choice selection screen as needed.

4. Not sure. Can't we keep the download links only in .html?

(looking for a packageable tox library to get into a major GNU/linux distribution, but it seems that i am not the only one)

i came here, because you are in charge of the tox.chat domain, and you provide several other downloads related to the tox project on a site under that domain. there's a lot of development taking place at random places and subject to random practices. it's very hard to do serious packaging based on that.

let me suggest to provide an official tox tarball with a version number on it containing consistently versioned libraries. any random version that you chose, will definitely do for a start. future tarballs must increase relevant version numbers, according to how the code has changed.

some background: the tox package (sometimes "toxcore") contains everything you need to ship proper release tarballs. it has a package version triplet and contains two libtool versioned libraries. all version triplets i could find are currently/still stuck at 0.0.0. type make dist to create this tarball (after configuring, after choosing a development repository).

version numbers are quite common for libraries to let linkers and binaries select the libraries with the desired or compatible interface. the original tox developer chose the libtool versioning scheme, likely because (s)he knew the implications, and because it works very well for a plethora of other libraries.
see this link for the full story or just read the relevant comment in the configure.ac file, if you are a tox developer.

• The Clients page should have galleries of screenshots for users to look at. You can save space by using lightbox or something like that.
• Every section should include a small table to the right of the screenshot listing the same information as can be found on the wiki (repo url, maintainer, language, etc.).

I can help a little. After reading through your blog post, I am not sure what is needed first. Anything specific you'd like done @installgen2

It's impossible to get Tox for Ubuntu Trusty following download instructions on tox.chat website.

The Binaries wiki page tries to help with that

To be able to install packages from this repository, run the following in your shell. Be sure to replace “$CODENAME” with the release codename of your distribution (jessie, stretch or sid for Debian and trusty or vivid for Ubuntu). If you use another Debian-based distribution like Ubuntu 14.04 Trusty or Elementary OS, just replace “$CODENAME” by “release”

but not very successfully though. At first it says that you can replace $CODENAME with "trusty", but this doesn't work (see the log below). Then it says to replace $CODENAME with "release" for Trusty. Wtf? Make up your mind!

But the website no longer links to the wiki page, it has a pop-up for Debian/Ubuntu at https://tox.chat/download.html which doesn't mention "release" at all, so users would try to add trusty with 0 packages!

A quick-fix would be to add more complete explanation to the Debian/Ubuntu download popup, saying which Debian/Ubuntu releases are supported and which are not (and/or mention "release"). A proper fix would be to package everything for all supported Debian/Ubuntu releases (@stal @tux3) so that we wouldn't have this issue in the first place.

$ cat #tox
<calher> Hi.
<calher> I'm trying to install qTox on an Trusty derivative.
<calher> Since lsb_release -cs spits out something that the repos won't understand, I replaced $(lsb_release -cs) with trusty.
<calher> Everything seemed well when I updated package index.
<calher> qtox failed to install and libtoxcore was not available.
<stal> i don't know if toxcore is actually packaged yet
<stal> ok it actually looks like half the distros have empty package indexes
<calher> I just followed the Ubuntu instructions on tox.chat.
<stal> i guess you could try using "vivid"
<stal> that seems to have packages
<calher> What's vivid?
<stal> as the codename
<calher> Just for completeness's sake, my results are at <http://bluehome.net/~csh/paste/qtox-install-error.txt>.
<stal> yeah so just replace trusty with vivid
<stal> probably won't break your whole system
<calher> stal, what system is vivid?  I'm on Trisquel GNU/Linux, which is based on recent Ubuntu LTS.
<stal> ubuntu 15.04
<nurupo> calher: https://wiki.tox.chat/binaries#debianubuntu
<nurupo> >If you use another Debian-based distribution like Ubuntu 14.04 Trusty or Elementary OS, just replace “$CODENAME” by “release”
<nurupo> despite its name, "release" has actually nothing to do with release versions. in release there are static binaries of nightly builds, which should work on ubuntu 14.04 and others
<calher> Oh, OK.  That sounds like what worked before.
<calher> Cool, it's working.  Thanks, nurupo!

If you'd like to learn, in more detail, about what the Tox Project is, and how it's being run, see The Tox Project Organizational Bylaws.

Link is dead.

Hey, it would be nice to use this instead of images: https://github.com/saneki/tox-webfont
Maybe fork it and add the icons u need. Would permit to have something more flexible in the long-term by making contributors able to use icons a way more easy.

The link to the pdf in about.html is death. This should be fixed before the site goes live...

Hi,
The page at https://tox.chat/download.html#gnulinux has wrong instructions:

echo "deb https://pkg.tox.chat/debian nightly $(lsb_release -cs)" | sudo tee /etc/apt/sources.list.d/tox.list
wget -qO - https://pkg.tox.chat/debian/pkg.gpg.key | sudo apt-key add -

The problem is that on linux mint $(lsb_release -cs) == rosa/qiana etc.

But the repo at https://pkg.tox.chat/debian does not have such folders.

So to fix:

1. we need to change the instructions and either add new section "for linux mint users" OR fix the debian/ubuntu instructions to make them work for linux mint users too...
2. Additionally when i add
   deb http://pkg.tox.chat/debian nightly trusty

to my /etc/apt/sources.list.d/tox.list

and refresh sources: and try to install qtox or anything from that new repo - nothing happens and there are no such packages...

This 2nd issue is separate and offtopic for this issue que here - where to post it ?

PS. Linux mint is the most popular linux distro - at least acc. to distrowatch stats. So its a pitty that a mint user cant install Tox.

We should have some kind of "Downloads" page that we can easily plug new clients into. It should include descriptions and logos for each client project.

I was thinking maybe a grid of logos (separated by platform), and when you click on a particular logo, you get a dialog with the project image, description, maintainers, etc. But you'd also need to include an easy way for people who don't know what they want to download an appropriate client for their platform.

To make it easy to include logos/wordmarks/screenshots in articles.

Tox-Archive/Tox-Website#8

Simple site to find a compatible license: http://choosealicense.com/

buildsite.py doesn't seem to generate the language list correctly. On the English page, I only see "English", and on the French page, I only see "Français".

Also, it should be able to handle partially-translated sites. Currently, if you don't have a translation for (for example) faq.html, you'll get dead links. Ideally, the user would just see the original page in its source language instead of a 404.

Hi.
I seen today that tox.chat was using this absolutly stupid "css-framework" that is Bootstrap. First bootstrap is an absolute bullshit. It just makes the code more ugly and not compatible with all the webbrowsers.

You can instead of this use some Flexbox css "framework" like Bulma.io or Kube.css (i think that kube.css is the more indicated for this website). You can also stop using external css and build your own using simple flexboxes layout. See this link for more informations on why using Flexbox is better.

qTox/qTox#2900

https://www.archlinux.org/packages/?sort=&q=tox&maintainer=&flagged=

https://wiki.tox.chat/users/tox_over_tor_tot
"Does Tox leak my IP address?" section of https://wiki.tox.chat/users/faq

How will my 'friend'(also via Tor or non-tor) see my IP address(I'm via Tor).
127.0.0.1, 10.x.x.x(my local network IP), or Tor's exit node IP address?

The site needs an "About" page that explains what the Tox Project is, who runs it, etc.

Don't worry about filling in the text, just come up with the layout and styles. I'll take care of the rest.

I spent about 30 minutes to find the link to the tox core git repo. And still not pretty sure that this is an official one. It would be great (and obvious) to add this link to the Download section of the website.

Thank you for great IM software :)

https://tox.chat/download.html#oses

How about adding Github URLs to each platforms, so the downloaders
pay a visit to Github to know more?

For example;
Windows
qTox 32 bit | 64 bit (Github)
uTox 32 bit | 64 bit (Github)

Hello,
You must be subscribed to the mailing list in order to post messages.
This is an automated message, so please don't reply to it.

irungentoo/toxcore#1595

https://news.slashdot.org/story/16/04/27/222233/former-tor-developer-created-malware-to-hack-tor-users-for-the-fbi

While Tox is not ToR, I want to know all people who actually writing the code.

https://tox.chat/about.html
Those listed without names have chosen to keep themselves anonymous (for now)

Anonymous is fine with me, buy why don't you just give us their @github username or something?
In short, can we actually trust these 'anonymous'?

In addition to the nav-bar at the top right of every page, we should have a separate navigation bar listing pages on the actual site. The FAQ, About, and Client pages should all be reachable within one click from the index page.

Is this desirable?
Alternatively, including short descriptions and/or images on download page?
Would help people decide on and download a client without navigating back and forth between the two pages and having to remember the name of the client they like the look of.

https://i.imgur.com/Ywr94AA.jpg

Using canvas for tracking unique visitors?
"How does Tox protect my privacy?"

Brief description: Wrong entry in sources.list; could not find "debian/binary-amd64/Packages" in release file.

Operating System: Linux Mint Debian Edition 2.0
qTox version: /

Reproducible: Always

Steps to reproduce:

1. Follow the instructions at https://tox.chat/download.html#gnulinux for Debian/Ubuntu

Observed Behavior:
Literally:

W: Fehlschlag beim Holen von https://pkg.tox.chat/debian/dists/nightly/InRelease Erwarteter Eintrag »debian/binary-amd64/Packages« konnte in Release-Datei nicht gefunden werden (falscher Eintrag in sources.list oder missgebildete Datei).

(German version)

Expected Behavior:
Install qTox.

Additional info:
May be related to qTox/qTox#2968

originally reported at qTox/qTox#3030

https://tox.chat/faq.html

There's no donation link(bitcoin).

It's difficult for a user to know which packages they're able to install from the repositories if we don't point them in the right direction. We should compile a list of clients and other utilities that a user can install from our repos.

Please just disable it.

• The client images in the middle of the index page are too small
• The mockup needs to be removed. I never want to see the mockup used in place of a client screenshot again.

Here is a list of Packages files in deb repos that are empty (empty ones have 0 in front, the last ones are NOT empty and the number in front is the size in bytes of the file..):

0 ./debian/dists/nightly/debug/binary-amd64/Packages
0 ./debian/dists/nightly/debug/binary-armel/Packages
0 ./debian/dists/nightly/debug/binary-armhf/Packages
0 ./debian/dists/nightly/debug/binary-i386/Packages
0 ./debian/dists/nightly/jessie/binary-armel/Packages
0 ./debian/dists/nightly/jessie/binary-armhf/Packages
0 ./debian/dists/nightly/release/binary-armel/Packages
0 ./debian/dists/nightly/release/binary-armhf/Packages
0 ./debian/dists/nightly/sid/binary-armel/Packages
0 ./debian/dists/nightly/sid/binary-armhf/Packages
0 ./debian/dists/nightly/stretch/binary-armel/Packages
0 ./debian/dists/nightly/stretch/binary-armhf/Packages
0 ./debian/dists/nightly/trusty/binary-amd64/Packages
0 ./debian/dists/nightly/trusty/binary-armel/Packages
0 ./debian/dists/nightly/trusty/binary-armhf/Packages
0 ./debian/dists/nightly/trusty/binary-i386/Packages
0 ./debian/dists/nightly/vivid/binary-armel/Packages
0 ./debian/dists/nightly/vivid/binary-armhf/Packages
0 ./debian/dists/nightly/wheezy/binary-amd64/Packages
0 ./debian/dists/nightly/wheezy/binary-armel/Packages
0 ./debian/dists/nightly/wheezy/binary-armhf/Packages
0 ./debian/dists/nightly/wheezy/binary-i386/Packages
0 ./debian/dists/nightly/wily/binary-armel/Packages
0 ./debian/dists/nightly/wily/binary-armhf/Packages
0 ./debian/dists/nightly/xenial/binary-amd64/Packages
0 ./debian/dists/nightly/xenial/binary-armel/Packages
0 ./debian/dists/nightly/xenial/binary-armhf/Packages
0 ./debian/dists/nightly/xenial/binary-i386/Packages
0 ./debian/dists/stable/jessie/binary-amd64/Packages
0 ./debian/dists/stable/jessie/binary-armel/Packages
0 ./debian/dists/stable/jessie/binary-armhf/Packages
0 ./debian/dists/stable/jessie/binary-i386/Packages
0 ./debian/dists/stable/release/binary-amd64/Packages
0 ./debian/dists/stable/release/binary-armel/Packages
0 ./debian/dists/stable/release/binary-armhf/Packages
0 ./debian/dists/stable/release/binary-i386/Packages
0 ./debian/dists/stable/sid/binary-amd64/Packages
0 ./debian/dists/stable/sid/binary-armel/Packages
0 ./debian/dists/stable/sid/binary-armhf/Packages
0 ./debian/dists/stable/sid/binary-i386/Packages
0 ./debian/dists/stable/stretch/binary-amd64/Packages
0 ./debian/dists/stable/stretch/binary-armel/Packages
0 ./debian/dists/stable/stretch/binary-armhf/Packages
0 ./debian/dists/stable/stretch/binary-i386/Packages
0 ./debian/dists/stable/trusty/binary-amd64/Packages
0 ./debian/dists/stable/trusty/binary-armel/Packages
0 ./debian/dists/stable/trusty/binary-armhf/Packages
0 ./debian/dists/stable/trusty/binary-i386/Packages
0 ./debian/dists/stable/vivid/binary-amd64/Packages
0 ./debian/dists/stable/vivid/binary-armel/Packages
0 ./debian/dists/stable/vivid/binary-armhf/Packages
0 ./debian/dists/stable/vivid/binary-i386/Packages
0 ./debian/dists/stable/wheezy/binary-amd64/Packages
0 ./debian/dists/stable/wheezy/binary-armel/Packages
0 ./debian/dists/stable/wheezy/binary-armhf/Packages
0 ./debian/dists/stable/wheezy/binary-i386/Packages
0 ./debian/dists/stable/wily/binary-amd64/Packages
0 ./debian/dists/stable/wily/binary-armel/Packages
0 ./debian/dists/stable/wily/binary-armhf/Packages
0 ./debian/dists/stable/wily/binary-i386/Packages
0 ./debian/dists/stable/xenial/binary-amd64/Packages
0 ./debian/dists/stable/xenial/binary-armel/Packages
0 ./debian/dists/stable/xenial/binary-armhf/Packages
0 ./debian/dists/stable/xenial/binary-i386/Packages
4 ./debian/dists/nightly/release/binary-amd64/Packages
4 ./debian/dists/nightly/release/binary-i386/Packages
12 ./debian/dists/nightly/jessie/binary-amd64/Packages
12 ./debian/dists/nightly/jessie/binary-i386/Packages
12 ./debian/dists/nightly/vivid/binary-amd64/Packages
12 ./debian/dists/nightly/vivid/binary-i386/Packages
12 ./debian/dists/nightly/wily/binary-amd64/Packages
12 ./debian/dists/nightly/wily/binary-i386/Packages
16 ./debian/dists/nightly/stretch/binary-amd64/Packages
16 ./debian/dists/nightly/stretch/binary-i386/Packages
20 ./debian/dists/nightly/sid/binary-amd64/Packages
20 ./debian/dists/nightly/sid/binary-i386/Packages

Is this the right place to report that? Who is in charge for debian packaging?

Hey guys, I was browsing the current beta of tox.chat on m'y smartphone and saw an horrible thing : centered texts. This is really ugly and it should be justified.

Screenshot of uglyness: http://imgur.com/M8Tizqg

ie.

p {
  text-align: justify;
}

I think it's related to the font Fira Sans

http://benschwarz.github.io/gallery-css/

The area that currently contains the mockup should instead contain an automatically scrolling screenshot gallery.

after follow instruction from
https://tox.chat/download.html#gnulinux
in the last step to install qtox-unity
but there is no qtox-unity package and try this command to show unity package
cat /var/lib/apt/lists/pkg.tox.chat* | grep "unity"
there was't unity package .

before:
Download
About
FAQ
Clients
Wiki
Mailing lists
Blog

after:
Download
About
FAQ
Clients
Wiki
Blog

1. Move 'Mailing lists' link to Wiki.
2. Add 'IRC' link to Wiki.

because:
Both mailing lists and IRC belongs to 'support' category.
Adding a 'Support' category, or moving them to 'FAQ' or 'Wiki' is a good idea I think.

Also, I find it hard to find your IRC.
irungentoo/toxcore#1596 (comment)

Hey guys, would it be possible to add Ricin on the clients page ?

0.0.2 release: here 😄
Screenshot: http://i.imgur.com/0OIIYvq.png (The current view show a blocked contact)
Repository: https://github.com/RicinApp/Ricin
Maintainer: SkyzohKey
Language: Vala
Graphical Toolkit: GTK+3
Operating Systems: Available for Linux (binary) + compilable under Windows/OSX.

It looks too think and gray instead of black. It's hard to see. At least harder than the white on gray text.

https://gist.github.com/nurupo/c7e7f454332fcf376315

After installing I saw this funny description of qTox package:

Is not that discriminatory against the other clients?

The dialog window that pops up when you click on an image preview should not be much larger than the picture being viewed. Currently, the dialog is way too big. Ideally, it would either be flush with the border of the picture, or hug it with a very small margin.

Tested on latest Tor Browser Bundle.

What is the preferred method for reporting possible exploits and bugs? I may have stumbled upon one and it might be better to tell one of the devs perhaps first.

Let me know...

Makes it annoying to scroll down since it allows you to scroll horizontally as well.

Hello, when I show people that tox is, those who speak and read Spanish, I generally share the https://tox.chat/ site but I see that the Spanish translation is incomplete. How do we fix it?

You don't list any fingerprint and also no QR code for scanning the FDroid repo. This is not only less secure it is also inconvenient.

Have a look at the Guardinproject repo to see how it should be done.

Would be nice to have an option to configure/create a shortcut to enable/disable the microphone.
Thanks guys :-D

<3 Tox

try again