DiPhyxDiPhyx
Workspace
Messaging

Every chat you have,in one browser tab

Telegram Desktop, running on a Void Linux desktop of your own.Sign in once, and the cloud brings every chat with it.

Telegram 7.0.42 cores · 4 GBOpens in a browser tab
hub://telegram

$ dxflow workflow create --identity telegram hub://telegram --start --link

01Pick a machinecores, memory and a rate per hour
02Create the workflowpulled from the hub, once
03Run it, then stopstopped when the work is done
The application

Sign in,and it is all there

The client is already installed. Sign in and your chats follow.

The history is cloud-side

Telegram keeps your history in its cloud, so all of your chats arrive with it.

Runs on either chip

The image is built for amd64 and arm64 alike, so the cheapest machine runs it.

Calls arrive silent

Calls and notifications stay silent until you switch AUDIO on for the session.

How you run it

Every defaultis one override away

The session reads its settings from the environment, so you set them on the start line.

VNC_PASSWORDWhat the tab asks for. It ships as dxflow, and everyone reading this knows that, which matters more here than most places.
PANEL and TASKBARBoth hidden, so the app has the whole screen. Show either one to get the desktop back.
AUDIOOff by default. Turn it on before you expect to hear a voice message or a call.
start it your way

$ dxflow workflow start telegram --override env.app.VNC_PASSWORD=something-long

$ dxflow workflow start telegram --override env.app.AUDIO=on --link

The session

One app,one whole desktop

Streamed to your browser, with Telegram already maximized.

6082Browserin the tab, at /vnc.html
5901VNCin a native client
/volumeStoragethe session, kept signed in
Open it from anywhereStart with --link and the session comes back on an HTTPS address.
Set a password firstVNC_PASSWORD defaults to dxflow, and everyone can read this page.
Good to know

The history isalready in the cloud

Telegram syncs from the server, so a fresh session catches up rather than starting empty.

Nothing to migrate

Sign in and the chats arrive. Secret chats are the exception, since those live only on the device that made them.

The session is the device

Anyone who reaches the tab is signed in as you. A real VNC_PASSWORD is the whole of the protection here.

Downloads land on the volume

Keep the profile and the download directory under /volume and the next start knows you already.

The image

Pulled once,then it stays

Telegram arrives as one image. This is what comes down the first time, and what the disk should have free for it.

375Mamd64compressed, the way the registry counts it
370Marm64compressed, the way the registry counts it
20GOn diskunpacked, with room to work beside it
ghcr.io/dxflow-ai/telegram:latestPublished from the hub, pulled on the first start and kept for the ones after it.
Either architectureamd64 and arm64 are both published, and the machine pulls the one it runs.
What it asks for

What it wants,and what it needs

The definition asks for 2 cores and 4 GB. The image comes up on less than that, and a start given --fit trims the ask to whatever the machine actually has.

2 cores · 4 GBAsks forwhat the definition writes down
2 cores · 2 GBRuns onthe least the image comes up on
Not neededGPUit works on the cores alone
The ask is not the floorThe definition writes down what suits the work. The image itself starts on less, which is what the second figure is.
--fit caps it to the hostA start given --fit trims each step to what the machine actually has, for that start alone. The definition is never rewritten.

Machines that fit it

Telegram asks for 2 cores and 4 GB. Cheapest first.

E2 Medium
$0.0419/ hour2 cores · 4 GBStart this machine
T3 Medium
$0.052/ hour2 cores · 4 GBStart this machine
B2s
$0.052/ hour2 cores · 4 GBStart this machine
Run Telegram on your own machinePick a machine that meets it, and it opens about a minute after you ask.
Start TelegramBrowse workflows