Channel
@huly_dev_blog
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
180subscribers
+5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003128102296 |
|---|---|
| Type | Channel |
| Username | @huly_dev_blog |
| Created | Between 1 September 2025 and 20 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 28 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 28 August 2026 |
| On Telegram | t.me/huly_dev_blog |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Aug 2026, 23:34 | 180 | -1 |
| 22 Aug 2026, 11:56 | 181 | +3 |
| 15 Aug 2026, 12:07 | 178 | +2 |
| 8 Aug 2026, 14:00 | 176 | no change |
| 8 Aug 2026, 11:52 | 176 | +1 |
| 7 Aug 2026, 21:22 | 175 | first reading |
17 posts held, back to 20 October 2025 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 9 July 2026. An engagement rate over an empty window would be a number about nothing.
122 reactions across 12 posts, in 18 distinct kinds. The most used accounts for 32.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 39 | 32.0% | |
| 🔥 | 16 | 13.1% | |
| custom 5382322671679708881 | 12 | 9.84% | |
| custom 5381879959335738545 | 9 | 7.38% | |
| 👍 | 7 | 5.74% | |
| 😱 | 6 | 4.92% | |
| 🤩 | 5 | 4.10% | |
| custom 5381990043642502553 | 4 | 3.28% | |
| ⚡ | 4 | 3.28% | |
| 🌚 | 4 | 3.28% | |
| 💔 | 4 | 3.28% | |
| 👏 | 3 | 2.46% | |
| ✍ | 2 | 1.64% | |
| 🎉 | 2 | 1.64% | |
| 🗿 | 2 | 1.64% | |
| custom 5382054253403577563 | 1 | 0.82% | |
| 🙏 | 1 | 0.82% | |
| 🥰 | 1 | 0.82% |
Custom emoji. 4 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 12 of the 17 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 122reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 20 October 2025 to 9 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.
Rethinking how I've been building Huly Over the past several months, I've approached the development of this platform as if I was on my own. I focused on doing most of the work myself, without fully accounting for the fact that there are actually a lot of people out there who care about where this product goes. I've come to think that approach wasn't the right one. So I've started an open-source collective focused…
❤9
📢 Huly Hosted Service — Update on Shutdown We want to share an important update regarding the Huly-hosted service (huly.app). As of July 20, 2026, Huly's hosted infrastructure will be shut down. This applies to all accounts. We strongly recommend backing up and migrating your data before this date — after the shutdown, recovery may not be possible. For context: the founder has been uninvolved for some time and has …
😱6💔4👍3✍2🙏1
Hi everyone! We’ve published a new release v0.7.423 with the following changes: • Cards & automation: richer processes (helpers, transforms, cleanup triggers), stronger associations (including bulk and nested setup), clearer execution lists—plus card UI improvements such as grid layout, space type selector, and “show all versions” • Documents & printing: print by class and id; copy content from controlled documents…
❤7🤩3🎉2👍2🥰1
Hi everyone! We’ve published a new release v0.7.411 with the following changes: Authentication • SSO password setup — set or reset password after email verification for SSO-linked accounts. • 2FA — optional second factor at sign-in. Guest access • Guest permissions — admin can configure what guests can do. • Guest auto-join — control guest inclusion in space auto-join. Cards & processes • Process helpers — built-i…
❤5🔥1
Hi everyone, We’re updating the dark theme and would like your input. We can either refresh the current theme or ship it as a new option. Please react with the variant you prefer, or leave a comment. Options 1–3 use an updated dark background; 4 is the current theme for comparison. Thanks, everyone.
custom 538232267167970888112custom 53818799593357385459custom 53819900436425025534custom 53820542534035775631
Hi everyone! We have published a new release v0.7.375 with the following changes: Internationalization - Add Brazilian Portuguese translation - Enable Turkish translation Workspace invites & login - Redesigned workspace join flow - Show Google login on mobile devices Guest collaborations - Guests can now upload attachments, use reactions, and configure notification settings - Allow notifications for guests with c…
🔥5⚡4👏3
Woke up at 4 am? Perfect Time for a "Quick" Prod Deploy. It's 4 AM. You're wide awake for no reason, and your brain, instead of dreaming about peaceful landscapes, decides it's the ideal time to think about bugs in production. "I'll just do a quick deploy," you tell yourself. "It's a tiny update, just a few changes. What could possibly go wrong?" So, there I was, pushing the new version of Huly to production. The …
🌚4🔥3
Posted without readable text
A Week of Fires, Fixes, and a Plan for Better Releases This week was a testament to resilience. After facing downtime from the global Cloudflare outage and a separate hosting provider issue, I stabilized our Docker pipeline and shipped a new version on Thursday. True to form, the release uncovered new bugs, which we've mostly fixed. A patched version is imminent. This process highlighted flaws in our release strat…
🔥7🤩2
This morning, Alexander Onnikov and I set out to build the production version of Huly. But the universe had other plans! All previous builds went smoothly, but starting today, even 30 GB of disk space just wasn’t enough. I wouldn’t call it a tough problem—we’ll optimize our build process soon (maybe with a little magic). But today, I had a flight booked to celebrate my father’s 70th birthday. Tomorrow, I’ll be back, …
❤5🗿2
Meet our newest contributor to the Huly Platform: Ryzhik the Cat! 🐾 Ryzhik has already made some impressive changes: i \\\\ Pm I’m not sure what these mean, but the code smells like tuna and curiosity. I can't commit this to our codebase at this point, but I hope he continues to develop his talents — maybe one day he’ll master rushx build (or at least stop sitting on the keyboard)! [Artyom Savchenko via https://hu…
❤10
Photo, posted without a caption
Showing the 12 most recent of 17 posts we hold for @huly_dev_blog. 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.
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 28 August 2026 — this entry's latest reading, not the date you are reading this.
“Huly Dev Blog” (@huly_dev_blog), 180 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/huly_dev_blog.
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.