4 Commits
Author SHA1 Message Date
sam 48019ec868 fix(telegram): a long message goes out in parts instead of failing for ever
publish / publish (push) Successful in 1m22s
The connector sent title and body as one sendMessage, so any notification
over Telegram's 4096 UTF-16 unit limit was refused with 'message is too
long' and, because a delivery is retried until the channel confirms it,
retried every ten minutes for ever without ever arriving. The chat channel
had its own splitter; both now share one in sdk/telegramtext, which counts
UTF-16 units rather than runes so an emoji-heavy body isn't over the limit
either.
2026-11-18 00:36:44 +11:00
sam ea7e88d4b0 feat(channels): typed settings for email and telegram
publish / publish (push) Canceled after 13s
2026-11-08 16:16:50 +11:00
sam f55d78487d feat(channels): declare email and telegram settings for the dashboard form (archie #1796)
publish / publish (push) Successful in 1m14s
2026-11-08 15:50:34 +11:00
sam 86501fa1d4 feat(messaging): run Telegram as an archipelago channel extension (#1399)
The bundled internal/channels/telegram package (17 files) is deleted; the
channel now ships as archipelago/channels/telegram, launched by archiemessaging
through the existing channel-extension machinery. An existing [chat.telegram]
config enables it with the same keys: the token stays a secret reference
(token_ref) the host resolves, allowed_user_ids and show_tool_calls map onto
extension settings. Per-org bots compose the same extension per org from the
org's credential binding. Reload support is now derived from a channels.Reloader
interface instead of a *telegram.Gateway assertion. The five host-only seams
(/update, release announcements, running versions, in-place show_tool_calls,
reload) are dropped from the channel and need a contract home or deletion.
2026-10-31 15:30:27 +11:00