Project Dignity (PD)

                 _           _         _ _             _ _         
 _ __  _ __ ___ (_) ___  ___| |_    __| (_) __ _ _ __ (_) |_ _   _ 
| '_ \| '__/ _ \| |/ _ \/ __| __|  / _` | |/ _` | '_ \| | __| | | |
| |_) | | | (_) | |  __/ (__| |_  | (_| | | (_| | | | | | |_| |_| |
| .__/|_|  \___// |\___|\___|\__|  \__,_|_|\__, |_| |_|_|\__|\__, |
|_|           |__/                         |___/             |___/ 

A decentralized, end-to-end encrypted community connection application built on Tor onion services.

About

Project Dignity (PD) is designed to balance human rights (privacy and security) with usability. Privacy is more important than usability, and privacy must not be sacrificed in order to increase user adoption. PD does not aim to solve societal problems, only to reduce tech harms.

PD enables people to meet each other -- romantically, socially, or otherwise -- through physically-anchored communities. Users join communities by physically visiting a location (a bar, community center, convention, or any space that hosts a PD relay) and scanning a QR code. All subsequent communication is peer-to-peer over Tor onion services.

Clients are the primary nodes -- they host Tor onion services and communicate directly with each other. Relays exist only for community membership onboarding, discoverability, and end-to-end encrypted offline message caching. Relays hold no user data by default. All relays are assumed to be malicious by design.

Planned Development Path

Phase	Document	Description
RFC-01	High Level Design	Architecture overview and design principles
RFC-02	Threat Model	Adversary taxonomy, threat analysis, mitigations
RFC-03 (TBD)	Software Requirements	Functional and non-functional requirements (SRS)
RFC-04 (TBD)	Low Level Design	Implementation details, crate architecture, protocols
MVP	--	Single relay, single community (alpha)
Audit	--	External security and code audit
Beta	--	First public beta

Planned Core Dependencies

• Arti -- Rust implementation of the Tor client for onion service hosting and connectivity.
• OpenMLS -- Rust implementation of MLS (RFC 9420) for end-to-end encrypted relay-cached messaging.
• Privacy Pass (VOPRF) -- Anonymous community membership tokens (RFC 9578, RFC 9497).
• Language: Rust

Planned Target Platforms

• Phase 1: Linux (postmarketOS, Jolla, Ubuntu Touch)
• Phase 2: Android
• Phase 3: iOS

RFC Format

All documents in this repository follow a lightweight RFC structure: metadata table, numbered requirements, and rationale sections. Documents are open for community review and comment.

License

All documents in this repository are licensed under CC BY-SA 4.0.

Contact

TBD (Lemmy, Matrix, Movim (XMPP), or Ergo (IRC) perhaps)