|
|
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.
|
|
|
|
|
|
# Protocol
|
|
|
* [BDF](BDF) binary data format
|
|
|
* [BQP](BQP) key agreement protocol
|
|
|
* [BSP](BSP) application layer data synchronisation protocol for delay-tolerant networks
|
|
|
* [BTP](BTP) transport layer security protocol for delay-tolerant networks
|
|
|
|
|
|
# Architecture and Clients
|
|
|
* [Bramble Application Architecture](BrambleApplicationArchitecture)
|
|
|
* [Client API Notes](ClientApiNotes)
|
|
|
* There's some thoughts on [how RPC could be implemented as a BSP client](RpcNotes)
|
|
|
|
|
|
Clients
|
|
|
* [Transport Client](TransportClient)
|
|
|
* [Messaging Client](MessagingClient)
|
|
|
* [Forum Client](ForumClient)
|
|
|
* [Blog Client](BlogClient)
|
|
|
|
|
|
# Contributing
|
|
|
* [Project Roadmap](Roadmap)
|
|
|
* [Development Workflow](development-workflow) and [Building from Source](https://briarproject.org/building.html)
|
|
|
* Translation Workflow (TODO) |
|
|
\ No newline at end of file |