Session Desktop - Onion routing based messenger
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Go to file
Beaudan c93aff7ebe Setup grunt/yarn etc for loki tests plus wrote first 2 simple libloki-protocol tests 7 years ago
.github
.tx
_locales fix missing awaits 7 years ago
app Hide new contact view unless we have no matches. 7 years ago
build
components Fixes to get production build working 7 years ago
config
fixtures Add style guide examples for portrait/landscape images 8 years ago
fonts
images
js Fix conversation status not being reset upon conversation messages deletion. 7 years ago
libloki Setup grunt/yarn etc for loki tests plus wrote first 2 simple libloki-protocol tests 7 years ago
libtextsecure Setup grunt/yarn etc for loki tests plus wrote first 2 simple libloki-protocol tests 7 years ago
mnemonic_languages
mockup_servers Linting and other housekeeping stuff 7 years ago
protos Merge pull request #61 from Mikunj/feature/profile-nickname 7 years ago
stylesheets Allow generating mnemonic for different languages. 7 years ago
test Fixed test again after rebase, reworked some logic in the conversation validateNumber function to correctly reflect what libsignal thinks is valid 7 years ago
ts Handle session reset, Loki style 7 years ago
.aptly.conf
.editorconfig
.eslintignore Setup grunt/yarn etc for loki tests plus wrote first 2 simple libloki-protocol tests 7 years ago
.eslintrc.js
.gitignore Setup grunt/yarn etc for loki tests plus wrote first 2 simple libloki-protocol tests 7 years ago
.gitlab-ci.yml gitlab-ci: install hunspell and set locale to en_US 7 years ago
.nvmrc
.prettierignore
.prettierrc.js
.travis.yml
.yarnclean
CONTRIBUTING.md
Gruntfile.js Setup grunt/yarn etc for loki tests plus wrote first 2 simple libloki-protocol tests 7 years ago
LICENSE
LOKI-NOTES.md
README.md
about.html
about_preload.js Remove jshint - move everything over to eslint 7 years ago
appveyor.yml
aptly.sh
background.html More consistent naming of key storage functions, moved some loki messenger only functions into new file 7 years ago
bower.json
debug_log.html
debug_log_preload.js
dev-app-update.yml.sample
find_broken_perms.sh
fix_broken_perms.sh
index.html
main.js Setup grunt/yarn etc for loki tests plus wrote first 2 simple libloki-protocol tests 7 years ago
package.json Setup grunt/yarn etc for loki tests plus wrote first 2 simple libloki-protocol tests 7 years ago
permissions_popup.html
permissions_popup_preload.js Fix permissions popup; add needed function on window (#2554) 7 years ago
preload.js Add header options. 7 years ago
prepare_beta_build.js
prepare_import_build.js
settings.html
settings_preload.js
styleguide.config.js
travis.sh
tsconfig.json
tslint.json
yarn.lock replaced jdenticon with identicon.js. 7 years ago

README.md

Loki Messenger

Loki Messenger allows for truly decentralized and end to end and private encrypted chats, Loki Messenger is built to handle both online and fully Asynchronous offline messages , Loki messenger implements the Signal protocol for message encryption, Our Client interface is a fork of Signal Messenger. All communication that passes through Loki messenger is routed through Lokinet.

Summary

Loki messenger integrates directly with Loki Service Nodes, which are a set of distributed, decentralized and Sybil resistant nodes. Service Nodes act as both federated servers which store messages offline, and a set of nodes which allow for mixnet functionality obfuscating users IP Addresses. For a full understanding of how Loki messenger works, read the Loki whitepaper

Online Messages

If Alice and Bob are both online they can simply resolve each others public keys, to introduction sets, this functionality is handled by interfacing with Lokinet. With the appropriate introduction sets Alice and Bob can create a path and using onion routing pass messages through the Loki network without giving away personally identifiable information like their IP address.

Offline messages

Offline messaging uses Swarms, given any users public key the user can resolve a public key to a specific grouping of Service Nodes (AKA Swarm) each user in Loki Messenger belongs to a Swarm. When routing a message offline the user selects a Service node in the destination users Swarm, when the user comes online they query any node in their Swarm, if the Swarm is holding any messages for the user they disseminate those messages to the user.

Swarm Messaging

Spam protections for Loki Messenger are based on a Proof of Work which is attached to any message that exceeds a default size or Time To Live, this process is discussed further in the Loki whitepaper.

Want to Contribute? Found a Bug or Have a feature request?

Please search for any existing issues that describe your bugs in order to avoid duplicate submissions. Submissions can be made by making a pull request to our development branch, if you don't know where to start contributing , try reading the Github issues page for ideas.

License

Copyright 2018- Current, Loki Foundation Copyright 2014-2018, Open Whisper Systems Licensed under the GPLv3: http://www.gnu.org/licenses/gpl-3.0.html