NoteSurge Changelog

v1.52.0

v1.52.0

August 24, 2026

Fixed

A Telegram connection that can’t actually deliver now fails at connect time — not after your notes pile up

Connecting a bot used to accept destinations that could never work: paste your bot’s own numeric id (or its @username) as the chat and the connection saved cleanly — then every scheduled note to it died with “Forbidden: the bot can’t send messages to the bot”, surfacing only as a stuck retrying note. The connect step now catches both forms on the spot and tells you what to use instead.

  • A new “Send test message” button on the Connect Telegram card fires one real message at the exact credentials you typed, before anything is saved — proving the bot can actually deliver there, and showing Telegram’s own error text if it can’t.
← v1.51.0v1.53.0 →
← All versions