0047ec5e7490215f2202f258b05ac9f8d4edef98
telegramMediaSender routes a MediaAttachment to the matching Bot API method (sendVideo/sendPhoto/sendAudio/sendDocument) rather than sendMessage, which cannot carry a file. It is constructed per-launch from the same *bot.Bot the update handler already has, matching telegramApprover's lifetime rule: a /restart abandons an in-flight send against the outgoing bot instance rather than silently redirecting it through the new one. liveReply.Media wires TurnStream into this: it checks gateway.CapabilitiesOf before attempting delivery -- not just on failure -- so a sender that already knows it cannot deliver a given media kind never costs a doomed network round trip. Either path (capability-limited or a failed send) falls back to rendering the attachment's URL as a visible link, so a generated asset is never silently dropped. newMediaSender is an injectable field so tests can prove the capability check actually short-circuits, since the real Telegram sender always reports Media: true and can't exercise that path itself.
Description
Archie connects events from your systems to agents that can investigate, reason, and act.
Define what an event means, map its data into a workflow, and give that workflow an agent equipped for the job: its own execution environment, tools, and identity.
https://archie.catlow.cloud
133 MiB
0 Stars
1 Watchers
0 Forks
Releases
11
Archie v1.62.0
Latest
Languages
Go
76.8%
Vue
13.1%
TypeScript
7.8%
JavaScript
1.2%
Shell
0.6%
Other
0.4%