← Back to Docs
TIP Protocol Overview
The Threadline Identity Protocol (TIP) is an open protocol for cross-site commenter identity and reputation. It lets users carry a verified identity across any TIP-compatible site without creating separate accounts.
Why TIP Exists
Traditional comment systems either lock users into a walled garden (Disqus, Facebook Comments) or force them to create yet another account. TIP takes a different approach:
- No central account. Identity is cryptographically verified, not stored in a central database.
- Cross-site portability. Your identity works on any TIP-compatible site.
- Reputation travels with you. Build trust on one site, carry it to another.
- Self-hostable. Run your own identity provider or use Threadline's managed one.
Core Concepts
| Concept | Description |
|---|---|
| Identity | A cryptographically signed profile (name, avatar, public key) issued by an identity provider. |
| Reputation | A score derived from comment history, moderation outcomes, and engagement patterns. |
| Provider | A service that issues and verifies TIP identities. Threadline runs a default provider; you can run your own. |
| Attestation | A signed statement from one site about a user's behavior (e.g., "this user had 50 comments, 0 moderated"). |
Real-world examples
- Indie blog: A solo writer builds reputation on their site; readers keep that portable identity when they comment elsewhere.
- Newsroom SSO + TIP: A publication signs readers in with existing SSO, then issues a TIP identity so reputation works beyond the paywall.
- Multi-site publisher network: One media group runs several domains; a trusted commenter on Site A arrives on Site B with the same score and level.
- Leaving a site: A reader exports their TIP identity (and optional history summary) when a site shuts down or they switch platforms - no lock-in.
Specification
The full protocol spec is available in the repository at tip/SPECIFICATION.md and as an OpenAPI spec at docs/API/tip-spec-v1.0.0.yaml.