Channel
@urixblog
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
13subscribers
-1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001296134759 |
|---|---|
| Type | Channel |
| Username | @urixblog |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 4 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 4 October 2026 |
| On Telegram | t.me/urixblog |
Personal blog — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 4 October 2026 and assigned it the closest of 31 fixed categories, at 69% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Oct 2026, 05:01 | 13 | -1 |
| 12 Aug 2026, 00:32 | 14 | no change |
| 8 Aug 2026, 00:03 | 14 | first reading |
20 posts held, back to 11 February 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 page of 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 20 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 12 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.
5 reactions across 4 posts, in 5 distinct kinds. The most used accounts for 20.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👌 | 1 | 20.0% | |
| 👍 | 1 | 20.0% | |
| 👏 | 1 | 20.0% | |
| 🔥 | 1 | 20.0% | |
| 😱 | 1 | 20.0% |
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 4 of the 20 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 5 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 11 February 2026 to 11 August 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.
The Museum of the History of the Universe in Dedovsk, near Moscow. It’s only a 400-meter walk from Miitovskaya station. A high-quality, compact exhibition — great for visiting with kids. https://youtube.com/shorts/FOYLM-7nEW0?si=Sdts_fi5lCKyEf0E
🎉 I made it into RuStore with my very first Android app! Of course, I don’t actually know how to develop for Android, so ChatGPT handled the technical side under my wise supervision. I asked him to rewrite my tiny iOS/macOS/ObjC app, FlexRecipes, into a native Android app written in Kotlin, and it did the job remarkably well. After that, we spent a couple of evenings polishing and debugging the little details togeth…
I was actually trying to make a stand for my Kärcher CVH AE handheld vacuum… but somehow it ended up looking like a mortar. At least it’s pretty solid!
Video, posted without a caption
🎉 After 5 years, I’ve finally updated XstereO Player for macOS! 🎉 By that time I’d already accumulated quite a few changes over time, and not all of them were particularly good. So this update turned into a major cleanup of those changes along with a lot of obsolete code. ChatGPT helped me quite a bit here as well, but converting the XIB to Auto Layout was something I had to tackle myself. https://apps.apple.com/us…
Just made a hood ornament for the fender of my kick scooter. And the fender itself - this model does not have one. I used PETG with PLA as support layers (on Bambu lab X2D); I primed, painted, and varnished it. I ordered ASA for the final result
Self-portrait. PLA + PETG support. Made in Meshy.ai and BambuStudio.app. I first tried free Hunyuan - but the results were very bad.
A little upgrade. . (Creality Space Pi Filament Dryer)
I highly recommend printing these silica gel boxes for yourself. They lowered the humidity inside my AMS by more than 10% compared to the standard configuration. Previously, I had 25-30%—almost the same as in the room outside the AMS.
Upgrade ✅
I built myself a little utility for correcting panoramas called Fix360. The funny thing is that out of the 2,057 lines of final code, more than 99% were written by Codex! Even the App Store description was generated. My conversations with the AI during the debugging process probably amounted to about half that volume again. But we got there in the end! Codex decided to build everything in SwiftUI, and I had no objec…
I just added HEIC and AVIF to the export formats in StereoFix.app! I need AVIF especially, because it is the most compatible format across web browsers and I use it now in my blog. I also added downscaling options https://apps.apple.com/us/app/stereofix/id6504026232
👌1
Showing the 12 most recent of 20 posts we hold for @urixblog. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 4 October 2026 — this entry's latest reading, not the date you are reading this.
“UrixBlog” (@urixblog), 13 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/urixblog.
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.