BasePlatformAdapter optional methods (typing, edit, delete, media) #661
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#661
Reference in new issue
Block a user
Extend adapter capability beyond the four required
BasePlatformAdaptermethods with optional per-platform methods: typing indicator, message edit, message delete, and media-specific send.Context for implementers
internal/gateway/adapter.gotoday definesBasePlatformAdapterwith exactly four methods:Connect,Disconnect,Send,ChatInfo(see full listing — the file is 80 lines). Not every platform supports typing/edit/delete/media uniformly, so these should be a separate optional interface(s) that callers type-assert for, not additions to the required interface (that would break every existing adapter implementation). Pairs witharchie-core-1786637493387-138-cad8e7a7(platform capability flags) — callers need a way to know ahead of a type assertion whether an adapter supports a given optional method, rather than probing via failed assertions at call time.Acceptance Criteria
Optional methods are defined on a separate interface (or interfaces) from
BasePlatformAdapter, so existing adapters keep compiling unchanged. At least one adapter implementation exercises each optional method in a test. Callers that invoke an optional method on an adapter that doesn't implement it get a defined, non-panicking behavior.Close reason
Media portion delivered: gateway.MediaSender + telegramMediaSender + TurnStream.Media wiring in Telegram's liveReply. Typing/edit/delete indicators from this issue's original scope are NOT done -- splitting them out if still wanted, since they're unrelated to the video-gen work that drove this. [Closure restored 2026-08-24: originally closed 2026-08-22, lost when the beads DB was rebuilt (.beads.backup-pre-recovery).]
Imported from beads
archie-core-1786637493329-136-49b39c78· GitHub #157 · type task · priority P2 · created 2026-08-08 · closed 2026-08-24