AndroidLab From retrocomputing to AI, through Android.
Telegram Amiga alpha 0.0.4: edit, delete and real-time read receipts on AmigaOS, MorphOS and AROS

Telegram Amiga alpha 0.0.4: edit/delete, live read receipts and correct timestamps

by

Telegram Amiga alpha 0.0.4 is now available as a new pre-release for AmigaOS 3.x, AmigaOS 4.x, MorphOS, AROS i386 and AROS x86_64. This is a meaningful release because it moves the project from “you can chat” toward something much closer to daily use: message editing, message deletion from the GUI, near real-time read receipts, synchronization of messages sent from other devices and corrected timestamps on Amiga-like systems.

The project is still a native MTProto client written in C, not a web wrapper and not a Bot API shortcut. The GUI still uses Intuition/GadTools and a renderer controlled by the program itself, while the public packages cover five different system lines. In 0.0.4 the focus is on the features that matter once a chat window stops being a demo and starts behaving like a real client.

Edit and delete from the GUI

The most visible addition is support for editing and deleting your own messages. In the GUI, you can open the right-click context menu on a sent bubble, choose edit, correct the text in the composer and save it. Deletion asks for confirmation and, if Telegram accepts the operation, removes the message from the view.

Under the interface these are real MTProto calls: messages.editMessage, messages.deleteMessages and, for channels or supergroups, channels.deleteMessages. It is not a local renderer trick. The client goes through Telegram’s protocol and then updates the chat state shown to the user.

On a modern client, fixing a typo or deleting a message sent by mistake is almost invisible. On AmigaOS, MorphOS and AROS it means coordinating GUI hit-testing, composer state, message state, TL builders and server responses without a contemporary messaging framework doing half the work for you.

Read receipts that react faster

Alpha 0.0.3 introduced graphical checkmarks drawn by the client. Alpha 0.0.4 makes them more alive: Telegram Amiga now parses updateReadHistoryOutbox, the update Telegram sends when the other side has read outgoing messages. When that read cursor changes, the blue double checks can update almost in real time.

The client still keeps a getPeerDialogs backstop for cases where the update stream is not enough. The polling cadence is adaptive: while one of your own messages is still only “sent”, Telegram Amiga checks more often; once everything is read, it relaxes again to avoid wasting round-trips on slower links or less forgiving systems.

This is one of those features that feels obvious until you implement it in a portable MTProto client. The checkmark is no longer just a neat drawing next to a timestamp; it becomes an indicator synchronized with the real state of the conversation.

Messages sent from other devices

Multi-device behavior also improves. If the same Telegram account sends a message from a Mac, phone or another client, the open conversation in Telegram Amiga can now see that outgoing message too. The chat poll includes outgoing messages and deduplicates entries that already exist as local optimistic echoes.

When a local echo does not yet have a final server ID, the driver can reconcile the message by comparing content and state, then adopt the real ID. The visible result is simple: the chat stays more coherent. The technical work avoids duplicates, gaps and ghost messages, which is exactly the swamp every messaging client enters if it treats the network as ordered and polite.

Correct message times on Amiga

The most subtle fix may be the most Amiga-like one: message timestamps. Real-world testing exposed a problem where some messages could appear one hour ahead. The cause was not Telegram itself, but the way some C runtime paths handled time(), local offsets and daylight saving time compared with the clock actually visible to the system.

Alpha 0.0.4 adds a platform abstraction based on the Amiga wall clock. On AmigaOS 3.x, AmigaOS 4.x, MorphOS and AROS the client reads DateStamp, the local system clock, and compensates for skew between that value and the epoch used by the C runtime. In practice, Telegram Amiga no longer assumes that “printing the time” is simple, because on historical systems simple and correct are not always the same thing.

It is a very representative fix. Telegram Amiga is not only about bringing modern code to older machines; it is about discovering where compatibility layers expose bugs that modern systems often hide under thicker carpets.

More polished UX and packages

The release also improves the surrounding experience. Version 0.0.4 is now a single source of truth in TG_VERSION and appears in the About box and startup banner. The context menu highlights the hovered item, the 2FA login step is clearer and the human-facing packages are aligned with the public release.

The packages are published as five GitHub pre-releases, all dated July 2, 2026:

Project status

The word alpha still matters. Telegram Amiga is not a complete Telegram Desktop replacement: media upload/download, reactions, full contact management and long-session polish remain outside the main scope. The priority is still to build a dependable text and graphical client before adding weight.

Still, the trajectory is clear. Alpha 0.0.1 brought the public GUI, 0.0.2 consolidated chat lists, history, search, unread state and packages, and 0.0.3 added native replies and graphical checkmarks. Alpha 0.0.4 completes another loop: editing, deletion, more reactive read state, multi-device coherence and sensible timestamps. These are not fireworks. They are exactly the normal features that make a client feel less like an experiment and more like a tool.

Quick summary

  • Telegram Amiga alpha 0.0.4 is available for AmigaOS 3.x, AmigaOS 4.x, MorphOS, AROS i386 and AROS x86_64.
  • The GUI supports editing and deleting your own messages through the context menu.
  • Blue double checks update almost in real time through updateReadHistoryOutbox.
  • Messages sent by the same account from other devices are synchronized into the open chat.
  • Message times use the Amiga wall clock through DateStamp, fixing the one-hour offset seen in testing.
  • README, visible version, About box and public packages are aligned with release 0.0.4.

Sources and context

AUTHOR

IT specialist, developer and systems engineer with a long history across code, Linux servers, retrocomputers and e-learning platforms. On AndroidLab he brings a technical, pragmatic eye: less brochure smoke, more attention to infrastructure, usability, privacy, updates and the real consequences of manufacturers' choices.

Leave a Comment