Bluesky / ATProto Integration for DasBlog

[poppastring]

Overview

This epic tracks the work required to add first-class Bluesky and ATProto integration to DasBlog. The goal is to make DasBlog a modern, decentralized-friendly blogging engine that can publish to Bluesky, use Bluesky replies as comments, authenticate authors via DID, and expose ATProto-native feeds.

Bluesky’s ATProto provides:

• Decentralized identity (DIDs)
• Portable social graphs
• A rich posting API
• A feed generator system
• A spam-resistant comment ecosystem

Integrating these features will modernize DasBlog and reduce maintenance overhead (e.g., spam comments, identity management).

---

Goals

• Allow authors to publish posts directly to Bluesky.
• Use Bluesky replies as the comment system.
• Support Bluesky/DID-based login for authors.
• Provide a Bluesky feed generator endpoint.
• Optionally store posts as ATProto records.
• Add Bluesky metadata fields to the post editor.

---

Related Issues

✔ Publish to Bluesky

• Add Bluesky/ATProto integration to publish blog posts as Bluesky posts #790 — Add Bluesky/ATProto integration to publish blog posts as Bluesky posts

✔ Bluesky Replies as Comments

• Integrate Bluesky Replies as Blog Comments #791 — Integrate Bluesky Replies as Blog Comments

✔ Bluesky Feed Generator

• Generate a Bluesky Feed (ATProto Feed Generator API) #793 — Generate a Bluesky Feed (ATProto Feed Generator API)

✔ ATProto Record Storage

• Publish DasBlog posts as metadata-only Standard.site records #856 — Adopt site.standard.document and site.standard.publication Lexicons as canonical ATProto record format (supersedes Store Blog Posts as ATProto Records (Experimental) #794)

✔ Bluesky Metadata Fields

• Add Bluesky Metadata Fields to Post Editor #795 — Add Bluesky Metadata Fields to Post Editor

---

Progress Tracking

• Add Bluesky/ATProto integration to publish blog posts as Bluesky posts #790 Publish to Bluesky
• Integrate Bluesky Replies as Blog Comments #791 Bluesky Replies as Comments
• Generate a Bluesky Feed (ATProto Feed Generator API) #793 Bluesky Feed Generator
• Publish DasBlog posts as metadata-only Standard.site records #856 Adopt site.standard.* Lexicons (supersedes Store Blog Posts as ATProto Records (Experimental) #794)
• Add Bluesky Metadata Fields to Post Editor #795 Bluesky Metadata Fields

GitHub will automatically check these off as issues are closed.

---

Acceptance Criteria

• All six issues implemented or scoped.
• Documentation added for Bluesky integration.
• Admin UI updated with Bluesky configuration.
• Optional features clearly marked as experimental.
• Integration tested with real Bluesky accounts.

---

Notes

This epic should also be added to a GitHub Project for tracking.
Each sub‑issue can be worked on independently, but this umbrella issue provides the architectural context and long-term vision.

[poppastring]

Cleanup pass:
• Auth model settled: server-to-PDS delegation via a stored Bluesky app-password, encrypted at rest alongside the existing SMTP-password pattern in  SiteSecurity . No admin-side OAuth.
• #792 closed as won't do — wrong layer. Removing from this epic's scope.
• Canonical lexicon for records is Standard.site ( site.standard.publication  +  site.standard.document ), tracked in #856.
Remaining scope in this epic: #856, #790, #791, #793, #795, plus a new small issue for  /.well-known/atproto-did  to be filed separately.