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 available, Briar can sync via the Tor network, protecting users and their relationships from surveillance.

Feel free to edit this wiki! Your contributions are appreciated.

• Frequently Asked Questions (FAQ)

Protocol

• A Quick Overview of the Protocol Stack
• How Briar Connects to Contacts
• BDF - a structured data format
• BQP - a QR code key agreement protocol
• BHP - a key agreement protocol
• BRP - a discovery protocol
• BTP - a transport layer security protocol for delay-tolerant networks
• BSP - an application layer data synchronisation protocol for delay-tolerant networks

Architecture

• Threat Model
• Application Lifecyle
• Client API Notes
• Some thoughts on how RPC could be implemented as a BSP client
• Mailbox Architecture

Clients

• Transport Key Agreement Client
• Transport Properties Client
• Messaging Client
• Forum Client
• Forum Sharing Client
• Blog Client
• Blog Sharing Client
• Private Group Client
• Private Group Sharing Client
• Introduction Client

Build Process

• Building from Source
• Building the Tor Binaries

Development

• Development 101
• Changelog
• Project Roadmap to 1.0
• Sponsor 1 Roadmap
• Product Backlog (aka possible future features)
• Process for Designing and Developing New Features
• Development Workflow
• Pre-Review Checklist
• Coding Style
• Signed Commits
• Translation Workflow
• Adding support for new architectures in Tor

Testing

• Testing
• Field Guide (work in progress)

Briar Desktop

Please see its respective wiki.