Summary

Integrate JSS with Bluesky (AT Protocol) to bridge Solid pods with Bluesky's 40+ million users. This gives Solid a massive distribution channel and gives Bluesky users decentralized data ownership.

Why this matters

Bluesky users already understand decentralized identity (DIDs) and personal data servers (PDSes). The mental model maps directly to Solid pods. Bridging the two ecosystems lets:

• Bluesky users get a Solid pod backed by their existing DID
• Solid users publish to Bluesky from their pod
• Both benefit from a larger network effect

Possible integration points

Phase 1: Read bridge

• Mirror Bluesky posts into a pod container as JSON-LD
• Map AT Protocol DIDs to WebIDs
• Display Bluesky feeds via mashlib/SolidOS UI

Phase 2: Write bridge

• Post to Bluesky from a Solid pod (write to /bluesky/feed/, syncs to AT Protocol)
• Cross-post: write once to pod, publish to both Solid and Bluesky

Phase 3: Identity bridge

• Link Bluesky DID ↔ WebID (similar to existing Nostr DID linking)
• Use Bluesky handle as pod name
• SSO: log into JSS with Bluesky credentials

Phase 4: Full federation

• JSS acts as a lightweight AT Protocol PDS
• Bluesky users can use JSS as their data server
• Pod data accessible via both Solid and AT Protocol

Prior art

• JSS already has ActivityPub federation (--activitypub)
• JSS already has Nostr DID linking (did:nostr)
• AT Protocol uses DIDs and signed data — similar trust model to Solid+WebID