Search Results for "java voice chat"

Smoke is an encrypting chat messenger for Android written in Java. Please read the Web site for more information: https://textbrowser.github.io/smoke/ (original, current) https://www.amazon.com/dp/3752691999/ https://smokeappope.sourceforge.io/ (old, third party archive) Smoke App OPE - Open Personal Encryption Download Android APK Installer: https://sourceforge.net/projects/smokeappope/files/ Smoke Source: https://github.com/textbrowser/smoke SmokeStack Source: https://github.com/textbrowser/smokestack (Android) https://github.com/textbrowser/spot-on (Desktop) Smoke appears to be one of the first projects with an open source mobile encrypting chat server., an decentralized and easily-configurable chat server. ...

Briar is a messaging app designed for activists, journalists, and anyone else who needs a safe, easy and robust way to communicate. Unlike traditional messaging tools such as email, Twitter or Telegram, Briar doesn't rely on a central server - messages are synchronized directly between the users' devices. If the Internet's down, Briar can sync via Bluetooth or Wi-Fi, keeping the information flowing in a crisis. If the Internet's up, Briar can sync via the Tor network, protecting users and...

Polarity is a dual engine browser powered by both Chromium and Trident that focuses on system efficiency by bringing low RAM and low CPU usage. This browser was also programmed to be optimized for Windows with an Android version available. Browse the web with an uncomplicated UI that is highly customizable with themes, apps, and extensions from the Polarity Store, GreasyFork, OpenUserJS, and UserStyles. Polarity also comes with a built in password manager which safely encrypts all data to...

SecuXabber is a secure Jabber-client for Android that bases on Xabber and uses a strong, asymmetric enryption that works on top of the XMPP protocol. A key pair is generated on application start-up. Users can send their public key to other SecuXabber users via Bluetooth. This ensures the origin of the public key because people do a face-to-face check during key exchange. After the keys are imported by both users, all communication between them is done fully encrpyted using a strong 4096 bit...