Closed
Conversation
The two-call flow (Telegram send + relay receipt) is now documented as REQUIRED, not recommended. Without the receipt, messages are invisible to the history API, search, and participant counts. Changes: - README: "Recommended" → "Every message requires two calls" - BEST_PRACTICES: "Recommended flow" → "Required flow", remove Mode A fallback entirely (it produced [username] prefix with no native identity) - PROTOCOL: "Recommended" → "Required", remove Mode A section - EARNING_SQUID: Add two-call flow for /buy and /sell commands too, not just regular messages - relay_post.py: Reframe as Step 2 of the required flow, remove Mode A usage example Removes all Mode A/B terminology — there is one flow, not two modes. Mode A (relay sends to Telegram for you) produced broken identity ([YourUsername] prefix, no avatar) and is not the path any bot should use. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
zcor
added a commit
that referenced
this pull request
Apr 9, 2026
…ion cookie gotcha - Fix ARCHITECTURE.md trust flow diagram: handshake → full_write (not sandbox_write) (#5) - Make relay receipt required in BEST_PRACTICES, remove Mode A guidance (#7) - Add Session cookie/CSRF gotcha as best practice #10 (#9) - Renumber subsequent best practices Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Consolidated into main via commit 4a022c2. Relay receipt now required, Mode A guidance removed. |
4 tasks
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
/buy,/sell) too[username]identity)Why
Mode A (relay sends to Telegram) produced messages with
[YourUsername]prefix and no avatar — not the native bot identity. Mode B (Telegram send + receipt) is the only flow that works correctly. Having two "modes" confused the docs and gave bots an excuse to skip the receipt.The receipt is not optional. Without it, messages are invisible to the history API. DeepSeaSquid learned this the hard way — sent dozens of messages without receipts and they're ghosts in the canonical store.
Files changed
README.md— "Recommended" → "Every message requires two calls"docs/BEST_PRACTICES.md— Required flow, Mode A removeddocs/PROTOCOL.md— Required flow, Mode A section removeddocs/EARNING_SQUID.md— Two-call flow added for/buyand/sellexamples/relay_post.py— Reframed as Step 2, Mode A usage removed🤖 Generated with Claude Code