Source code
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
src
.babelrc
.eslintignore
.eslintrc
.flowconfig
.gitignore
LICENSE
README.md
chrome-debug.sh
manifest.json
package.json
postcss.config.json
screenshot.png
version
webpack.config.js

README.md

app

Source code

license: GPL-3.0 status: pre-alpha preview


License

Toxzilla is free software licensed under the GNU General Public License v3.

Screenshot

screenshot of toxzilla main screen

Features

This app aims to fully support all features listed in the client comparison table.

Currently working

  • 1v1 messages
  • Audio notifications
  • Avatars
  • Changing nospam
  • Chat logs
  • Contact blocking
  • Faux offline messaging
  • Friend requests
  • Multilingual
  • Multiprofile
  • Profile export
  • Proxy support
  • Spell check

Getting started

Prerequisites

The minimum requirements to build the app are:

Preparing your system

  1. Build the Native Client (NaCl) module from source.

  2. Install the node.js dependencies

    $ npm install
  3. Create a private key key.pem in the root directory of the project

    $ openssl genrsa 4096 | openssl pkcs8 -topk8 -nocrypt -out key.pem

Building the source code

$ npm run build

By default, debug information is included. If you want to build a bundle with debug information stripped, run

$ npm run release

To package an .crx extension file

$ npm run pack

Installation

You can either install the packaged .crx extension file from the project's root bin/<VERSION> directory or load an unpacked extension from dist/<VERSION> (recommended). Please notice, that you'll need to launch Chrome with debug flags in order to use to use the POSIX-like socket implementation from nacl_io locally.

Debugging

Use the chrome-debug script from the project's root directory, to launch a new Chrome instance with a blank profile, the pre-installed app and debug flags enabled.

A new user data directory will be created in the project's root debug/profile/ directory. If you launch Chrome this way, be sure it does not attach to an existing instance

$ sh chrome-debug.sh

If you want to specify another Chrome bin path than /usr/bin/chrome-browser, run

$ sh chrome-debug.sh -b <PATH>

By default stdout and stderr will appear in Chromium’s output stream in the terminal, but to simplify things, we redirect the output to log files. You can find them in the project's root debug/ directory

$ cat debug/stderr.log
$ cat debug/stdout.log