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.

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

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.