Hello everyone,

I am working on Telegram Amiga, an experimental Telegram Bot API based client/tester for Amiga-like systems.

The long-term goal is to understand how far we can support AmigaOS 3.x, MorphOS, AmigaOS 4.x and AROS, starting from small technical validation builds rather than a full Telegram client.

A new pre-alpha tester build for AROS One i386 alt-abiv0 is available here:

https://github.co...12-514c4ee

Telegram Amiga is not a complete Telegram client yet.
At this stage it is a technical tester used to verify networking, TLS, JSON parsing, message polling, saved chats, controlled replies and an early interactive shell chat mode on Amiga-like systems.

I am currently developing and testing the AROS build using an AROS One i386 virtual machine under QEMU, because my main development machine is an Apple Silicon Mac.

For this reason, feedback from other AROS setups — especially real x86 hardware or different VM configurations — would be very valuable.

As part of this work, I also started an early port of Bebbo’s sshd to AROS:

https://github.co...bossh-aros

The port is still very embryonic, but already useful for development workflows, remote testing and moving files in/out of the AROS environment.

Latest Telegram Amiga update:

• TLS-enabled AROS i386 alt-abiv0 builds are available;
• HTTPS, preflight, getMe, read-only polling and controlled sendMessage have already passed in my AROS VM;
• TLS certificate validation can be tested with --tls-verify and a CA bundle;
• the manual console now has an early chat mode:
• chat <index>
• normal text sends to the selected chat;
• incoming messages are auto-polled every 5 seconds while waiting for input;
• /watch <seconds> changes the auto-read interval;
• /watch off disables auto-read;
• /read polls immediately;
• /back exits the selected chat;
• /quit exits.

This is still Bot API based: it works as a chat with a Telegram bot, not as a full Telegram user-account client.

Suggested offline tests, no Telegram token required:

telegram-test --help
telegram-test --telegram-json-self-test
telegram-test --telegram-get-updates-self-test
telegram-test --telegram-read-once-state-self-test
telegram-test --telegram-inbox-self-test
telegram-test --telegram-echo-once-self-test
telegram-test --telegram-send-message-self-test
telegram-test --telegram-client-self-test
telegram-test --telegram-tls-status

Network tests, no Telegram token required:

telegram-test --net-test example.com 80
telegram-test --http-test example.com 80 /

TLS tests, no Telegram token required:

telegram-test --https-test api.telegram.org 443 /
telegram-test --telegram-preflight

If you have a CA bundle available, certificate validation can be tested with:

telegram-test --tls-verify --tls-ca-file ca-bundle.crt --https-test api.telegram.org 443 /
telegram-test --tls-verify --tls-ca-file ca-bundle.crt --telegram-preflight

For live Bot API tests, please use only a disposable test bot token created with @BotFather.

Save it as:

telegram-token.txt

in the same drawer as telegram-test.

Please do not publish tokens or screenshots that show tokens.

Useful live commands:

telegram-test --telegram-getme-default
telegram-test --telegram-client-default
telegram-test --telegram-client-console
[12/05/26 13:25] kaffeine: Inside telegram-client-console:

read
list
chat 1

Inside chat mode:

hello from AROS
/watch 2
/watch off
/read
/back
/quit

Please test the interactive console and chat mode from the local AROS Shell, not through SSH, if possible.
Remote shell interaction through early SSH ports may not behave reliably enough yet and could produce misleading results.

Please report:

• AROS distribution and version;
• 32-bit or 64-bit;
• hosted, native, emulated or virtualized setup;
• compiler name/version if built from source;
[12/05/26 13:25] kaffeine: • whether OpenSSL or AmiSSL is available;
• whether --tls-verify was tested and which CA bundle/path was used;
• output of offline, TCP/HTTP, HTTPS and Bot API commands;
• whether the interactive chat mode works from the local Shell;
• any crash, freeze, requester or unusual delay.

Thank you for helping test Telegram Amiga on AROS.

Great, I'd love to test it. But why 32-bit and not x86_64 right away?

Good point. x86_64 is definitely planned.

I started with i386 mostly because it was the fastest AROS environment for me to bring up under QEMU on my Apple Silicon Mac, and because I wanted to validate the code first on one known AROS target.

The current AROS build does not use AmiSSL directly: it uses OpenSSL directly, linking against libssl/libcrypto.

From what I found, AROS x86_64/ABIv11 has OpenSSL 1.1.0h available in the contrib archive as linker libraries, and it has already been used for software such as Odyssey. So an x86_64 port should be feasible.

I still want to validate the i386 build first, then try an AROS x86_64 build/test as the next step.

If you want to try building or testing it on AROS x86_64, that would be very welcome. Any build logs, errors, patches or runtime test results would be extremely useful.

Small update on Telegram Amiga.

The project is now mainly focused on MTProto, aiming at a real text-based Telegram client for Amiga-like systems with login, saved sessions, peer handling and message reading.

New AROS i386 ABIv0 release:
https://github.co...28-91b0506

Repository:
https://github.co...gram-amiga

AROS x86_64 is currently frozen as a diagnostic/porting target due to an early runtime crash before --help. Development and testing are therefore focused on AROS i386 ABIv0, currently the most practical AROS target.

Tests, logs and feedback from real AROS i386 systems are very welcome.

If you need help debugging, check out this short tutorial on using GDB:

https://arosworld.org/infusions/forum/viewthread.php?thread_id=1201&pid=10891#post_10891

Small update on Telegram Amiga.

The project has moved from the text/TUI client to the first public GUI alpha.

This is still alpha software and should be treated as a test build, but the basic flow is now available through a native GUI:

- reuse of the MTProto session;
- chat list;
- conversation view;
- sending text messages;
- native builds for the main Amiga-like targets.

The AROS builds are here:

- AROS i386 ABIv0:
https://github.com/kaffeine1/telegram-amiga/releases/tag/aros-i386-alpha-0.0.1

- AROS x86_64:
https://github.com/kaffeine1/telegram-amiga/releases/tag/aros-x86_64-alpha-0.0.1

General release page:
https://github.com/kaffeine1/telegram-amiga/releases

I also wrote a short release note with screenshots here:
https://androidlab.it/telegram-amiga-gui-alpha-001-amigaos-morphos-aros/

The interesting part is that this is the real MTProto path, not the old Bot API diagnostic path. So the client logs in as a Telegram user account, creates/reuses the local auth state, reads chats/history and sends text messages.

For AROS testing, useful feedback would be:

- AROS version/distribution;
- i386 ABIv0 or x86_64;
- real hardware, hosted, VM or emulator;
- TCP/IP stack/environment;
- whether login, chat list, history and sending messages work;
- freezes, crashes, requester messages, rendering problems or strange delays.

Important privacy note: please do not post auth files, phone numbers, login codes, 2FA passwords, access hashes or private message text. Logs and screenshots are very welcome, but please redact them first.

i use the X86_64 on real hardware works fine

I have released the new version of Telegram Amiga, 0.0.5.

This release brings several improvements: real avatars in the chat list, @ mention autocomplete in groups, optional own-screen mode (for now it requires manual configuration: in the Telegram Amiga drawer, edit data/telegram-gui-win.txt; the line must use the format width height x y own), remembered window position and size between sessions, a fix for the right-click freeze, cleaner handling of data/ and avatars/, and better preservation of newlines and lists in messages.

Full article with details and links to the GitHub/Aminet packages:

https://androidla...phos-aros/

As always, testing on real hardware or emulated setups is extremely valuable: bug reports, freezes, graphical issues, incompatibilities or any odd behaviour are very welcome. The more platforms and configurations we test, the more solid the client becomes.

I wanted to test the latest version, but I got stuck right at the beginning
I enter my phone number in the following format:
+48123456789
I wait for the code, but nothing comes to my phone.

When, after a long wait, I press Esc and then try to run the program again, it crashes

x86_64 version
I tried it on Aros Linux Hosted and on QEMU

Hi, thanks for testing! Three quick things:

The login code goes to your Telegram app on an already-logged-in device (check the chat called "Telegram" on your phone), not by SMS unless you have no other session. Did you check there?
Which AROS exactly? The x86_64 build is picky: it needs a trunk-matched AROS and won't run properly on AROS One v0.38 (different kickstart), crashes included. On AROS One or hosted setups the aros-i386 ABIv0 package is the safe one.
For the crash on relaunch: delete data/phone-code-hash.txt before retrying and tell me if it still crashes. If you can capture the crash text or Guru number, even better.

Unfortunately, the code isn't coming through via SMS or in the app (which I have running on my phone).

I noticed that I have to delete the telegram-auth.bin file; then I can restart it without it crashing.

As for the x86_64 version, I tested it on the latest stable release (20250418-1 + U3) and on the latest nightly build.

If there’s another specific version that works, please provide a download link. This app looks really promising

Good news: found it and fixed it, thanks to your hint about deleting telegram-auth.bin, that was the decisive clue. The client was tearing down a shared network library while other connections were still using it, which is exactly what happens on a relaunch after an aborted login. Fix will be in 0.0.7, on all platforms.

Your AROS versions are fine by the way, the stable 20250418 is the same base I use as reference for the x86_64 build, so no need to change anything.

About the login code: after you enter the phone number, does it say "Login code sent"? If yes, Telegram accepted the request and the code should appear in your phone app, in the service chat called "Telegram" (not as SMS). Also note Telegram won't resend a new code for a few minutes if one is still pending, so quick retries can look like nothing arrives.

It's finally working After logging in on my home computer, the code finally arrived on my phone. Maybe the missing code was just a temporary issue with Telegram? I'll try to confirm that tomorrow. I'll keep testing it and let you know if I run into any problems.

The new Telegram Amiga alpha 0.0.8 release is now available.

The main additions are non-blocking file transfers, multi-datacenter downloads and Workbench drag-and-drop upload. The client remains usable while a file is being transferred: you can keep chatting, switch conversations and receive messages.

There is much more as well, including local chat search, a configurable download drawer and clickable URLs.

https://androidla...-blocking/

Telegram Amiga 0.0.9 alpha is out for AROS (i386/x86_64).

Photos have finally arrived: inline rendering with progressive decode, built-in viewer, native JPEG sending and message forwarding to other chats.

https://androidla...orwarding/

I wanted to test the new version, but I'm having trouble receiving the code for the app again. TelegramAmiga displays a message saying that the code has been sent and is waiting for me to enter the 5-digit code, but nothing is showing up on the app on my phone.

Now I'm wondering - is Telegram generally so unreliable that it doesn't deliver these codes, or is there perhaps an issue with the AROS-side app? Is there any way we can debug this?

Thanks so much for your patience, and sorry for the runaround!

To help narrow this down, quick question: what exactly does your screen say when you request the code? It should tell you whether it sent it via SMS, a phone call, or inside Telegram.
(Heads up: if it says "in Telegram", look for it in the official Telegram service chat with the blue checkmark on a device where you're already logged in — just make sure that chat isn't muted or tucked away in your Archived folder).

In the meantime, it's worth trying this:

Delete telegram-auth.bin and data/phone-code-hash.txt, then restart the client.
Request the code once and wait a couple of minutes without spamming it (Telegram rate-limits quickly).
Just so you know, right now the client shows the same error whether a code is wrong or just expired (my bad, working on a fix!). If none of that helps, let me know your version and build (i386 or x86_64) and we'll sort it out together.

Telegram Amiga 0.0.92 alpha - AROS x86_64

I've already tried what you're suggesting.

After entering my phone number, the screen shown in the attached screenshot appears.
I have the Telegram app open on my phone (I also have the Telegram service chat).

Thanks, that narrows things down a lot! The request left your Amiga fine and Telegram accepted it the only missing piece is the actual delivery of the code.

There's one big thing to rule out, and it's likely on my end, the app currently ships with shared api_id and api_hash keys. When too many people use the same key, Telegram throttles it; the client sees a normal "code sent" status, but nothing ever reaches your phone (which would explain why it suddenly resolved on its own last time).

Could you try with your own credentials?

Generate a pair at my.telegram.org (under API development tools).
Add them to data/telegram-api.txt (first line: api_id, second line: api_hash).
Delete telegram-auth.bin and data/phone-code-hash.txt, then try logging in again.
If it works with your own keys, we have our answer and I'll sort out a proper fix. If it still doesn't, launch with --gui-live-debug and send over PROGDIR:tg-gui-debug.log.
(I'm also adding the delivery method and digit count to the log in the next build, so we won't need to rely on screenshots anymore!)

I generated my own API ID/hash, but it didn't make a difference

The log doesn't tell me much:

[71623] live: start
[71623] live: refresh peers start
[71623] live: refresh peers done
[71623] live: session open start
[71623] live: session open FAIL
[71623] live: no auth -> login flow
[71623] live: run_window start
[71623] photo cache: scan done files=0 MB=0
[71623] window: RGB888 inline-photo replay active
[71623] window: double-buffer 820x560 depth 24
[71623] window: drag-and-drop enabled
[71623] window: setup complete
[71623] paint1: off-screen rendering start
[71623] login paint: clear
[71623] prim 1: fill 0,0 820x560
[71623] login paint: title+status
[71623] prim 2: text 354,232 14x0
[71623] prim 3: text 290,264 30x0
[71623] login paint: input box
[71623] prim 4: fill 270,284 280x24
[71623] login paint: footer
[71623] prim 5: text 306,328 26x0
[71623] login paint: done
[71623] paint1: blit start
[71623] paint1: blit done
[71623] window: first paint done
[71623] window: activating
[71623] window: opened
[71639] login: send_code start
[71640] login: send_code done