mtflute 0.1.3

Pure-Dart Telegram MTProto client (API layer 225).

Changelog

0.1.3

• Fixed DC migration loop: migrate now kills the old poll loop before reconnecting, preventing duplicate pollers and repeated migrations.
• Migration depth capped at 5 (matching gogram) to prevent infinite recursion.
• Poll loop and reconnect logic bail immediately during active migration instead of racing.

0.1.2

• Fixed reconnect-spam loop: long-poll TCP reads no longer time out at 15s and trigger false reconnects.
• Reconnect is now single-flight (mutex-guarded), capped at 20 attempts, with exponential backoff (1s → 30s max).
• Poll loop runs once per client lifetime — no more concurrent pollers spawned per reconnect.

0.1.1

• Shorter pub.dev description.
• Replaced stub example with a real bot quickstart (inline buttons + callback handler).
• Bumped pointycastle to ^4.0.0 and lints to ^6.0.0.
• Added dartdoc coverage on generated TL types and the main client surface.

0.1.0 — first publish

Initial release. Pure-Dart MTProto client against Telegram API layer 225.

• Auth: bot tokens, phone + OTP + 2FA (SRP), string + file sessions
• Messaging: send/edit/delete/forward/pin, Markdown + HTML parse modes, inline button builder
• Updates: socket push + getDifference polling, dedup, auto-reconnect with backoff
• Files: multi-worker parallel up/download, cross-DC sender pool with caching
• DC migration: transparent on USER/PHONE/FILE/NETWORK_MIGRATE
• Conversation API, channels admin ops, participant iteration, bot commands, callback/inline answers
• Logger with TRACE/DEBUG/INFO/WARN/ERROR levels
• 64 tests: 55 unit + 9 live against Telegram