Idun

Each app has its own UX, moderation policies, and community. Consumes Idun credentials and participates in federation via either protocol. Apps never hold identity keys — they request presentations from the user's wallet.

AT Protocol uses personal data repositories (signed Merkle trees) for content-addressable, portable data. Content is genuinely portable — you can prove authorship independent of any server. Custom feeds and algorithmic discovery are pluggable layers.

Standard ActivityPub with Idun extensions. Follow relationships are bilateral — both servers hold copies. When a server goes down, the surviving side retains the relationship and can reconnect when you resurface on a new node.

The core protocol. Defines credential types for social trust (verified human, reputation score, platform membership), how they attach to DIDs, and how the social graph replicates across federated nodes. Protocol-agnostic — works with both ActivityPub and AT Protocol. All specs are open, all implementations are forkable.

Your canonical identity is a DID (Decentralised Identifier) that works with both ActivityPub and AT Protocol. It resolves to your ActivityPub actor URI, your AT Protocol PDS, and your Idun credentials simultaneously. Your keys are self-generated and self-held — no server owns them.

You verify once with your national eID. Credentials live in your EUDI Wallet on your device. Idun never holds your private keys. Selective disclosure means platforms only see what they need — "verified human, over 18" — never your name or personnummer.