What do you prefer?
- Wayland77%
- X11, X.org, xLibre23%
Shares as published. No per-option vote count is published by Telegram, so none is shown.

Channel
@dekuve
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
64subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001277451491 |
|---|---|
| Type | Channel |
| Username | @dekuve |
| Description | Your future favorite desktop operating system☺ based on Debian/GNU Linux 🐧 |
| Created | Between 1 April 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/dekuve |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 03:02 | 64 | no change |
| 7 Aug 2026, 20:52 | 64 | first reading |
15 posts held, back to 3 April 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 25 July 2026 |
|---|---|
| Posts held | 15 (3 April 2026 – 25 July 2026) |
| Views total | 32 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 03:02 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
30 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 26.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 8 | 26.7% | |
| 🔥 | 7 | 23.3% | |
| 😁 | 6 | 20.0% | |
| 👍 | 4 | 13.3% | |
| ❤🔥 | 2 | 6.67% | |
| 😱 | 2 | 6.67% | |
| 🤓 | 1 | 3.33% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 11 of the 15 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 30reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 3 April 2026 to 25 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
What do you prefer?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Возвращаю старое название канала, так как сообщество Desert OS больше не нуждается в моей помощи продвижения проекта. Если кто-то ищет проект, то он находится здесь https://t.me/DESERTOSLinux I'm returning to the old channel name, as the Desert OS community no longer needs my help promoting the project. If anyone is looking for the project, it's here: https://t.me/DESERTOSLinux Estou voltando ao nome antigo do cana…
❤2😱2
Signed Denys
Channel name was changed to «DEKUVE»
Congratulations to Desert OS 👏🎉 This impressive Linux distro can bring your spare PC back to life | ZDNET https://www.zdnet.com/article/desert-os-linux-distro-bring-spare-pc-back-to-life/
❤3
Signed Denys
https://www.npmjs.com/package/postcss-dpx 12 скачиваний пакета dynamic pixel за 18 дней. Я считаю, что это успех. Без активного продвижения и рекламы. Следим и ждём отзывы 😁 12 downloads of the dynamic pixel package in 18 days. I consider that a success. No active promotion or advertising. Will be monitoring and waiting for feedback 😁 12 downloads do pacote de pixels dinâmicos em 18 dias. Considero isso um sucesso…
❤1🔥1
Signed Denys
Что-то мне напоминает 🤔🤷 Reminds me of something 🤔🤷 Me lembra de algo 🤔🤷
Signed Denys
Спасибо, что пользуетесь - @SaveAsBot'ом
🤓1
Signed Denys
Тестирую эффект размытия фона окна без участия композитора. Как вам? Testing out the window background blur effect without the compositor. What do you think? Testando o efeito de desfoque de fundo da janela sem o compositor. O que vocês acham?
👍2
Signed Denys
Apple анимировало логотип DEKUVE 😁🤣 Apple animated the DEKUVE logo 😁🤣 A Apple animou o logotipo da DEKUVE 😁🤣 Siri orb for macOS 27 Golden Gate
😁3🔥2👍1
Signed Denys
Дробное масштабирование - это жопа. 😁 🇬🇧 Fractional scaling is a complete mess for modern UIs. 🤦♂️ Look how legacy units deform when changing resolution, while DPX remains completely stable. I don't understand why anyone would buy a 3K, 4K, or 8K monitor if Linux or Windows will cut the resolution down to a tiny image with fractional scaling. 😁 I just developed a permanent solution to the screen fragmentation prob…
👍1
Signed Denys
Разработка пользовательского интерфейса для маленьких телефонов и огромных 8K-экранов не должна быть кошмаром. Создано постоянное решение! 🎉 postcss-dpx v1.0.0 уже доступен на npm. Четкое, аппаратно-независимое масштабирование с 0% затратами ЦП на стороне клиента. Попробуйте: dpx.dekuve.top 🌍⚙️ 🇬🇧 Designing UI for tiny phones & huge 8K screens shouldn't be a nightmare. Built a permanent fix! 🎉 postcss-dpx v1.0.0 …
🔥2
Signed Denys
Сейчас работаю над интеграцией Liquid Metal в GTK. Получилось неплохо? 🇬🇧Currently working on bringing the Liquid Metal to GTK. Any good? 🇧🇷Atualmente estou trabalhando para trazer o Liquid Metal para o GTK. Alguma novidade?
🔥2
Signed Milky Way
Showing the 12 most recent of 15 posts we hold for @dekuve. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
What do you prefer?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 15 most recent posts we hold, published 3 April 2026 to 25 July 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 10 August 2026 — this entry's latest reading, not the date you are reading this.
“DEKUVE” (@dekuve), 64 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/dekuve.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.