A from-scratch, native MTProto Telegram client for Amiga-family systems — log in with a normal Telegram account, list your chats and exchange messages. Zero external dependencies: no MUI, no ixemul, no AmiSSL. All the cryptography (RSA, Diffie-Hellman, SRP/2FA, AES, SHA) is built in.

Two front-ends share one engine:

• TelegramAmiga — a native Intuition/GadTools GUI: chat list with real avatars and persistent unread badges, conversation view, scrollbars (wheel, knob drag, arrow keys, pixel scroll), scroll-to-top history paging, click-to-compose with multi-line wrap, online chat search, drag-and-drop reorder and remove, live receive, "<name> is typing", read receipts, file sharing and a pinned Saved Messages chat. A double-click starts it with no flashing console and no launcher script. Drawn by the client itself on a RastPort.
• TelegramAmiga-TUI — the text/console client, at home on a 68030 with a serial console: same engine, launched from the second icon.

Status: alpha 0.0.8 — everyday direct-message and group chat works on all five platforms below. 0.0.8 is transfers 2.0: the client stays fully usable while a file moves — keep chatting, switch chats, receive messages — with pipelined download chunks, the speed next to the percentage, documents and profile photos fetched from any Telegram datacenter, drag-and-drop upload onto the chat window, and a download drawer picked from the menu. The sidebar search filters your chats as you type, searches your own dialogs first (it finds back a chat you removed, even a private group with no public username) and browses your complete dialog list from an empty box; URLs in messages are blue and clickable, menus follow the system colours, the chat list reloads on demand and remembers the chats you removed, and AmiKit/AfA_OS systems render text correctly. All that on top of 0.0.7's robust big transfers, Copy/Cut/Paste and Edit menu, reply on double-click and live remote edits, 0.0.6's file sharing, pinned Saved Messages cloud drawer, script-free launch icons, and 0.0.5's real avatars, @username autocomplete, remembered window position and optional own screen, 0.0.4's edit & delete, live read receipts, multi-device sync and system-clock times, 0.0.3's replies, checkmarks and flicker-free drawing, and 0.0.2's history paging, search, badges and chat management.

Development on main is now preparing 0.0.9: hidden chats stay available in the local search, messages can be forwarded to Saved Messages or another chat, photo thumbnails render inline from a geometry-independent cache, a click opens a larger progressive photo viewer, inline loading can be disabled on slower machines, and JPEGs can be sent as native Telegram photos. These changes are not part of the 0.0.8 downloads below until all five platform lanes complete real-system validation.

License: MIT — a non-commercial community project, a gift to the Amiga community. Development diary: https://androidlab.it/en/telegram-amiga-mtproto-client-development-diary/

Each package bundles both clients, icons, a public telegram-api.txt and per-architecture IT/EN manuals — and no private files.

All releases: https://github.com/kaffeine1/telegram-amiga/releases — full history in CHANGELOG.md (also bundled in every package as CHANGELOG.txt).

AmigaOS 3.x is a native clib2 build (no ixemul, no AmiSSL) and needs a 68020 or better. AROS x86_64 targets trunk-SDK-matched systems (AROS One v0.38 pairs a different kickstart and will not run it); AROS i386 ABIv0 is the broadest AROS build.

1. Download your platform's package and copy the drawer to a writable volume (e.g. Work:) — it writes its files next to itself, so not the CD.
2. Double-click TelegramAmiga — it opens the GUI directly, with no flashing console window — or TelegramAmiga-TUI for the console client.
3. First run signs you in: phone number → login code → optional 2FA password. A telegram-auth.bin session is saved; later runs go straight to your chats.

2FA on a slow 68k: Telegram's two-step key derivation is PBKDF2 (100000× SHA-512) — about 40 minutes on a stock 14 MHz 68020, long enough that Telegram drops the login first. On such machines disable Two-Step Verification (Telegram app → Settings → Privacy and Security) before signing in. The client warns at the password prompt rather than blocking, so faster/accelerated 68k can still try.

Full IT/EN instructions are inside each package.

• MTProto auth-key creation, phone/code login wizard, 2FA, saved session.
• Chat list (users, basic groups, channels/supergroups): the full list is fetched once on first login, then your curation wins — drag-reorder, remove (menu / Del / right-Amiga+R), online search to add, persistent unread badges.
• Reading history with scroll-to-top paging (load older on demand) and sending long, multi-line text where the account has permission.
• File sharing: send and download big files (up to 125 MiB on 68k, 250 MiB elsewhere; live %, retry, cancellable), plus a pinned Saved Messages chat as a cloud transfer drawer (fully editable).
• Message edit & delete (right-click), replies on double-click, live updates for messages edited elsewhere, clipboard Copy/Cut/Paste with text selection (mouse or Shift+arrows), @username autocomplete.
• Real profile-picture avatars (blurred previews instantly, crisp on open).
• Current main: inline message photos with an on-disk cache and a larger click-to-open viewer, a persistent text-only photo mode for slower machines, forwarding to Saved Messages or another chat, and hidden chats surfaced by local search.
• Native GUI scrolling (wheel / scrollbar / arrows / pixel), remembered window size and position, optional own screen, Iconify to a Workbench AppIcon, dark theme, script-free flashless Workbench launch.
• Live receive, "<name> is typing…", read receipts (v / vv), message styling/entities, reply quotes, cross-chat notifications.
• gzip_packed responses decoded in-tree (embedded puff, no zlib needed).

Reactions, contact management, albums and media playback, and files served by Telegram's CDN (some big public-channel downloads). The aim is a dependable text-and-files client first; richer media comes later only where the platform makes it realistic.

Never publish these (or screenshots/logs that reveal them):

telegram-auth.bin   phone-code-hash.txt   telegram-password.txt
telegram-peers.txt  telegram-seed.bin     telegram-token.txt

telegram-auth.bin is your logged-in Telegram session — anyone who gets it can access your account; if it leaks, treat the account as compromised.

On targets without a system CSPRNG/TLS, the crypto secrets come from an in-tree DRBG seeded from local entropy (timer jitter, keystrokes, a persisted telegram-seed.bin). A first login in a fresh emulator/VM is the weakest moment — prefer real hardware, or an AmiSSL/OpenSSL target, if your threat model needs it.

Five lanes — see the Makefile.* files and docs/: AmigaOS 3.x (m68k clib2), AmigaOS 4 (PPC), MorphOS (PPC), AROS i386, AROS x86_64. Host smoke test:

make -f Makefile.aros clean all ENABLE_GZIP=0 ENABLE_GZIP_PUFF=1
./build/TelegramAmiga --mtproto-self-test-fast

A token-based Bot API mode remains in the tree for diagnostics and TLS/HTTP validation; it is no longer the product direction.

Developed with the help of LLM agents used as engineering tools (analysis, implementation, packaging, docs, test prep). Local diaries, transcripts and secrets stay out of Git.

Useful bug reports: platform + version, real/emulated, CPU, TCP/IP stack, and what failed — secrets removed. Never post tokens, auth files, phone numbers, login codes, 2FA passwords or private message text.