Slack-Colibri bridge: update proposal for v0 production status#21
Open
tomlarkworthy wants to merge 1 commit into
Open
Slack-Colibri bridge: update proposal for v0 production status#21tomlarkworthy wants to merge 1 commit into
tomlarkworthy wants to merge 1 commit into
Conversation
Reflect that the bridge has shipped and is operational. Tighten the narrative from "design we propose" to "this is live, here's what's running and where the code lives". Status: v0 forward path live since 2026-05-31 on feelingofcomputing.bsky.social. Inverse-pattern channel ownership (community owner pre-creates channels under their DID, bot authors messages referencing those channel rkeys) - the workaround the original proposal described under "Inverse pattern: community owner pre-creates channels" is what shipped. Major changes: - Status banner reflects live deployment with bot DID (4gcxakknd6hxtnhf33miwsob) and separate community-owner DID (j7nm3lrd5h7fm3sfhcv3lhfv). - "What's live" bullet list of operational features: messages, edits, deletions, reactions, mentions (with DID resolution + inline pre-pass to populate the name cache), threaded replies, file attachments (image / video / audio inline, 5 MB cap, oversize placeholder), and lossless `com.feelingofcomputing.bridge.slackRaw` capture. - "Code" section linking the slack-sync monorepo (worker + backfill + Slack manifest); auto-deploy via Cloudflare Workers Builds on push to main. - Lexicon namespace renamed `com.feelingof.bridge.*` -> `com.feelingofcomputing.bridge.*` (community owns feelingofcomputing.com/.org/.net). - Architecture diagram updated: no D1 cache in v0; slackRaw is the de-facto idempotency boundary; D1 binding is reserved for v0.1+ if cache reads become useful. - slackRaw marked live; slackOrigin / slackChannel / slackUser marked designed-for-v0.1 (worker uses in-source maps today). - "Asks of Colibri" + "Open questions" reframed as "What would improve v0 next" + "Open" with already-shipped items removed (reactions, edits, deletes, file attachments now in "What's live"). New "Open" item: backfill in progress (4 weeks bridged as of 2026-06-01); unmapped-channel gap (6 channels, ~4600 msgs) pending community-owner action. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
tomlarkworthy
force-pushed
the
slack-colibri-bridge-live
branch
from
b729700 to
0161cb0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updates the Slack-Colibri bridge proposal (merged in #20) to reflect that v0 has shipped and is operational. Tightens the narrative from "design we propose" to "this is what's running, here's where things need to go to be maintained".
Status: v0 forward path live since 2026-05-31 on
@feelingofcomputing.bsky.social(did:plc:4gcxakknd6hxtnhf33miwsob). Community owned by a separate identity (did:plc:j7nm3lrd5h7fm3sfhcv3lhfv) — the inverse pattern the original proposal described under Inverse pattern: community owner pre-creates channels is what shipped.What the update reflects
com.feelingofcomputing.bridge.slackRawarchive.main.com.feelingof.bridge.*→com.feelingofcomputing.bridge.*since FoC owns feelingofcomputing.com/.org/.net.slackRawis the de-facto idempotency boundary.CHANNEL_MAP+SLACK_USER_DID_MAP, mirrored in JSON sidecars for the backfill) and how the community owner extends it for new channels.slackOrigin/slackChannel/slackUserlexicon designs (we don't intend to write these — the in-source maps are sufficient at FoC scale), the v2 claim-flow and OAuth narrative, and the "we propose to ship X" framing. Replaced with a "Known gaps" section that lists what's observably missing as facts, not as a commitment.Diff is
-291 / +86againstmain(one commit on top, scope is just the post-merge update — the original proposal landed in #20).Test plan
@feelingofcomputing.bsky.social; can be observed end-to-end by posting in any bridged Slack channel and watching the record land on the bot's PDS, then in Colibri.🤖 Generated with Claude Code