Hi @connorlanigan I think it will be great to add the build instructions on the README. I can't seem to find them clearly anywhere in the code.

The registration process should get some animations to guide the user through the process. The needed components should be blended in in the order in which they should be read.

I'd very much like an alternative to the chrome-app that whispersystems calls "desktop client".

Is this project dead?

Currently

This software is currently only available in English. It lacks a system of displaying Strings in the user's language.

After fixing

The program is available in at least one other language.
The program has a mechanism to allow for easy translation into more languages.

Possible approaches

Using the Java internationalisation procedures: Click here to visit the Java translation tutorial.

Relevant code

• de.norvos.log.Errors.Message

Create a GUI that makes available the functions that have been developed so far.
The GUI is developed using JavaFX.

• Guided Registration Process
• Overview over messages and contact list

Hey,
in main directory of the project, I get following error:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.3:compile (default-compile) on project norvos: Fatal error compiling: invalid target release: 1.8 -> [Help 1]

I already tried several versions of openjdk/jre and the Oracle version of Java. All results in the same error :(

Currently

All files are detected as "application/octet-stream".

After fixing

The method differentiates between the files that are common to be sent with this program and returns the correct corresponding MIME-type.
An external library could be used for this.

Relevant code

• String de.norvos.communication.Communicator.getMimeType(File file)

Currently

Debug messages are outputted via different methods (System.out.println and Errors.*). This leads to unclear code and makes it hard to deal with generated output.

After fixing

These message output should be unified into a single output process, which includes outputting the Axolotl debug messages. A logging framework should be used here, to allow for different relevance levels of messages.

Relevant Code

• de.norvos.log.Errors.[debug|warning|messaging](String)
• other code which contains System.out and System.err
• org.whispersystems.libaxolotl.logging.AxolotlLogger should be implemented

Currently

The program does not provide any introduction at first start.

After fixing

On first start, Norvos displays two messages to the user.

• a welcome message - before registration
  • In this message, the basic concept of the program is explained.
  • Goal: The user knows what the program does.
• a tutorial - after registration
  • In this message, the graphical interface of the program is explained.
  • Goals:
    • The user knows how to operate the program.
    • The user knows where to get further information and help.

Currently

The program cannot contact the server because the program does not have a KeyStore containing the server's TLS certificate.

After fixing

The server's TLS certificate is stored in a Java Keystore available to the program.

Possible approach

collect the servers SSL certificate (the server's URL is https://textsecure-service.whispersystems.org) from different locations and:

• if all certificates are the same:
  • create a keystore using this certificate
• else:
  • check if someone needs to be notified

Relevant code

• de.norvos.store.Locations.TRUST_STORE

Currently

Keys are stored in a single object, which in turn gets saved to disk on calling its save-method.

After fixing

The keys are stored as individual files on disk, which makes sure that they are permanently stored even if the program crashes.
This approach is used in the TextSecure-android app as well.

Relevant code

• de.norvos.store.axolotl.NorvosAxolotlStore

Contact should be stored and read from a database.