Telegram Desktop
https://desktop.telegram.org
Telegram is a non-profit cloud-based instant messaging service.
Users can send messages and exchange photos, videos, stickers, audio and files of any type.
Its client-side code is open-source software but the source code for recent versions is not always immediately published, whereas its server-side code is closed-source and proprietary.
The service also provides APIs to independent developers.
This is the official binary built by Telegram devs, but the package is unofficial.
-
1
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:Mx775/telegram && cd $_ - Create Badge
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| _service | 0000000725 725 Bytes | |
| org.telegram.desktop.desktop | 0000000590 590 Bytes | |
| org.telegram.desktop.service | 0000000065 65 Bytes | |
| telegram.spec | 0000002966 2.9 KB |
Comments 1
Hi Mohamed —
Could you share how you usually handle version updates?
Do you trigger them manually, or do you have automation set up with repo hooks/webhooks/CI?
If you’re using automation, it would be helpful to know: - Tool/Service in use
- Trigger event (tag, release, branch, etc.)
- Automation mechanism (CI/CD, webhook, OBS API, etc.)
- Rollback/Failure handling (notifications, fallback steps, etc.)
Example: - Automated via GitHub Actions on tag creation → CI pipeline → OBS API submit; token‑scoped; changelog auto‑generated from commits; failures notify maintainers.
Thanks in advance for clarifying — it will help others following the workflow.
— itachi_re xanbenson99@gmail.com