Telegram Amiga alpha 0.0.93 is available from September 12, 2026 for AmigaOS 3.x, AmigaOS 4.x, MorphOS, AROS i386 and AROS x86_64. This is the release in which the client starts turning the conversation into a fuller experience: it adds an emoji picker, PNG photo sending, a more honest login flow when the code does not arrive and automatic updates for previews that are already open.
Telegram Amiga remains a native MTProto client written in C, with an Intuition/GadTools GUI and TUI sharing the same engine. Version 0.0.93 is mainly a sending release: the program no longer just displays received content, but makes messages leaving the Amiga richer and more reliable.
Emoji: from text emoticons to real characters
The new picker opens from Insert emoji in the menu, with Amiga+E, or from the smiley button. Its grid shows 109 emoji, keeps recently used items at the front and can be navigated with the mouse, arrow keys and ENTER. ESC closes the panel without inserting anything.
The client keeps a text representation for the TUI and smaller graphical environments, while the Amiga GUI draws emoji as 16-pixel pictures. Composition, editing and cursor movement treat each emoji as one unit; when the message is sent, Telegram receives the actual Unicode character. The bundled Noto Emoji font is distributed under the SIL Open Font License.
The feature is disabled by default on native AGA/ECS/OCS systems and slower 68k machines, while it requires at least a 68040 and RTG where the hardware can sustain it. Settings > Enable emoji is separate from Inline photos: a lighter GUI can keep emoji disabled without giving up photos, and vice versa.
PNG as a photo, not just a file
Version 0.0.93 adds PNG image sending as Telegram photos. The client checks the actual file bytes, reads chunks through IEND and rejects truncated files before upload. It also validates dimensions and proportions, with a combined width-plus-height limit of 10,000 pixels and a maximum ratio of 20:1.
The same feature is available from the menu, drag-and-drop and the TUI through /photo. JPEG and PNG now follow the photo path with captions introduced in earlier releases; if the server rejects an image, the client returns a human-readable explanation instead of leaving the user with an opaque error.
A more reliable login when the code does not arrive
Login now handles the case where the code is not delivered through the expected route more clearly. After the wait shown by the screen, the client offers the available alternative, normally SMS; in the TUI, press S. The diagnostic log records the selected route and the wait without making a false promise to the user.
The release also fixes new-code handling related to the en-US locale versus bare en. The screen explains the verified-email case, shows an unknown delivery type when the server does not specify one and reports the expected digit count when that information is available.
Previews update while the chat is open
Link previews no longer remain stuck in their initial state. If metadata arrives after sending, the message already open in the chat updates automatically. This also works for a link just sent: the preview enters the inline-photo pipeline when available and is stored in the transcript cache.
The release includes smaller but concrete fixes too: pointer alignment on wrapped links, consistent URL and link styling, MorphOS freezes in popups and photo drawing, emoji no longer resizing avatars and fonts, composer baseline alignment and centred Send labels.
Official downloads
Alpha 0.0.93 is available on Aminet and GitHub for the five published targets:
- Aminet for AmigaOS 3.x and the GitHub AmigaOS 3.x release;
- Aminet for AmigaOS 4.x and the GitHub AmigaOS 4.x release;
- Aminet for MorphOS and the GitHub MorphOS release;
- Aminet for AROS i386 and the GitHub AROS i386 release;
- Aminet for AROS x86_64 and the GitHub AROS x86_64 release.
These packages should be distinguished from the AROS aarch64 Raspberry Pi build: the repository contains the build file and porting work, but it is not a sixth published release. The official repository contains source and documentation, while the CHANGELOG and roadmap describe the wider technical path. The historical context is collected in the Telegram Amiga development diary, while the previous milestone is covered in the 0.0.92 article.
A more expressive client that still respects the limits
Version 0.0.93 brings features that would seem obvious on a modern system, but require explicit choices on Amiga: graphics resources, hardware thresholds, TUI paths, caching, Unicode compatibility and understandable error messages. It is another step towards the 0.1.0 beta gate, which still depends on a quiet cycle, no known freezes on the five targets, adversarial review and updated documentation.
For testers, the most useful report includes the platform, version, network, TLS stack, command and observed behaviour. Session files, login codes and personal data should never be shared: the laboratory is open, but security remains part of the program.
Sources and materials
- Official Telegram Amiga repository
- CHANGELOG for release 0.0.93
- Official roadmap
- TelegramAmiga for AmigaOS 3.x
- TelegramAmiga for AmigaOS 4.x
- TelegramAmiga for MorphOS
- TelegramAmiga for AROS i386
- TelegramAmiga for AROS x86_64
- GitHub AmigaOS 3.x release
- GitHub AmigaOS 4.x release
- GitHub MorphOS release
- GitHub AROS i386 release
- GitHub AROS x86_64 release
- Telegram Amiga development diary