OpenWyrd

What it is

OpenWyrd MOP is a federated wire specification for one-shot encrypted artifacts. An author composes. The server returns a capability URL. The author shares the URL through any channel. The recipient pastes it and decrypts client-side. The server holds ciphertext, never keys. Any host can serve. Any client can read from any host. The artifact is the message; the URL is the entire access-control system.

Why it exists

You have lived inside the feed for a decade. You have noticed what it costs. OpenWyrd is the smallest correct primitive that does not feed you back to itself. There is nothing to scroll. There is no inbox. There is no ranking. The protocol does not know who you are and refuses to learn.

A messaging primitive that runs on one host is a hostage. Federation is the price of admission, not a feature.

What you can do now

• Read the spec. MOP-001 — wire specification.
• Run the conformance suite. Bring up an implementation, point the suite at it, get the badge or fix the bug.
• Fork a host. Stand up your own MOP server. The reference implementation runs in production; the spec runs everywhere.
• Build a client. Any client that decrypts a wyrd from any conformant host is a peer of every other client.
• Read the manifesto. Why this is a primitive and not a product.
• Read the charter. How the spec is governed and how it stays uncapturable.

Footer

• Specification: github.com/openwyrd/mop
• Conformance suite: github.com/openwyrd/mop-conformance
• Reference deployment: sendwyrd.com — one host among many
• Warrant canary: openwyrd.org/canary
• Security disclosures: security@openwyrd.org
• PGP fingerprint: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 (replace with project key fingerprint at launch)

Compose, capability, decrypt. The rest is noise.