Release: Alpha.1

February 12, 2026

The initial Teleghosts release!

We were too busy crafting this website so Alpha.1 ships with a bunch of silly bugs. For example, the app miserably crashes when a Telegram contact sends you a voice/audio message but you have disabled “voice messages” in your SimpleX profile preferences.

Fortunately, you can completely avoid most of these silly bugs by not messing with your SimpleX profile: create a separate profile specifically for Teleghosts, leave the default preferences untouched, and you should have a pretty decent experience. We’ve been running teleghosts in production this way for 2 months without any issues.

However, having a decent experience doesn’t make you a useful alpha-tester so we encourage to break things! Specifically, we’re interested in:

  • If somebody can reproduce the “Message is too long” error in SimpleX-Chat when sending a message from Telegram

  • A list of possible errors caused by deleting your profile address the teleghosts instance is linked with (this is a sure way to create a complete disaster)

  • Is it possible to crash teleghosts or a Simplex-Chat client by sending some bad file from Telegram or vice-versa

  • Any bugs that we didn’t expect. Be creative and surprise us!

Join our SimpleX group to report your findings, get help, share suggestions, and participate in general discussions!

Release integrity verification

To verify the release you must have ssh-keygen installed

  1. Download the release and the corresponding .sig file from the Downloads section below
  2. Download the SSH allowed signers file
  3. Ensure that the downloaded allowed signers file matches the .gitsigners file located in the code repository
  4. Execute ssh-keygen -Y verify -n file -f ./allowed_signers -I teleghost-dev@nomail.brr -s teleghosts.sig < teleghosts

Downloads

chmod +x ./teleghosts after download