The Open Presence Protocol Directory is the reference implementation and specification for resolving Open Presence Protocol (OPP) identities.
An OPP Directory allows applications to discover the current location of a subjects's signed OPP Presence Document.
It serves a role similar to DNS on the Internet: given a subject, it tells clients where to find the authoritative record.
The Open Presence Protocol ecosystem is composed of independent components with distinct responsibilities.
| Component | Responsibility |
|---|---|
| OPP | Defines subjects, presence documents, signing, and verification |
| OPP Directory | Resolves subjects into Presence Documents |
The Directory specification intentionally does not redefine subject or cryptography. Those are defined by the core OPP specification.
OPP Directory follows a simple principle:
Directories provide discovery. Presence Documents provide truth.
A directory helps clients locate a subject's current Presence Document.
The Presence Document itself remains the authoritative statement of that subject's online presence.
This separation keeps the protocol decentralized and allows individuals to retain control of their own presence information.
The project has four primary goals:
- Provide an open, vendor-neutral directory for OPP identities.
- Allow subject owners to update the location of their Presence Documents.
- Allow applications to resolve identities into Presence Documents.
- Remain simple enough that anyone can operate an OPP Directory.
| File | Purpose |
|---|---|
SPEC.md |
OPP Directory protocol specification |
README.md |
Project overview |
src/ |
Reference server implementation |
This project is in active development.
The protocol specification is being developed alongside the reference implementation.
Early versions should be considered experimental and may change as the protocol evolves.
The Sinatra/SQLite reference server lives in src/. See src/README.md for quick-start, API, test, and Docker instructions.
See LICENSE