Channel
@alurman
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
205subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001935054745 |
|---|---|
| Type | Channel |
| Username | @alurman |
| Created | Between 1 March 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 9 August 2026 |
| On Telegram | t.me/alurman |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 21:15 | 205 | no change |
| 8 Aug 2026, 21:30 | 205 | first reading |
20 posts held, back to 31 October 2023 — 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 20 posts for this entry, the most recent from 27 June 2026. An engagement rate over an empty window would be a number about nothing.
231 reactions across 19 posts, in 14 distinct kinds. The most used accounts for 41.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 96 | 41.6% | |
| ❤ | 38 | 16.5% | |
| 🔥 | 35 | 15.2% | |
| 🤓 | 26 | 11.3% | |
| 💯 | 6 | 2.60% | |
| 💊 | 5 | 2.16% | |
| 🤡 | 5 | 2.16% | |
| 🥰 | 5 | 2.16% | |
| 👏 | 4 | 1.73% | |
| 😁 | 4 | 1.73% | |
| 👎 | 3 | 1.30% | |
| ❤🔥 | 2 | 0.866% | |
| 🙏 | 1 | 0.433% | |
| 🤔 | 1 | 0.433% |
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 19 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 231reactions 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 31 October 2023 to 27 June 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @alurman. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 31 October 2023 to 27 June 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
TacoSprint 2026: making Nix more relocatable, fixing shebangs and sending my first kernel patch TacoSprint is a week-long sprint dedicated to hacking Nix on the Pacific coast of Mexico. This was my first sprint ever, so I wasn’t sure what to expect. But it was an amazing experience: lots of Nix hacking, tacos, surfing, learning and meeting cool people. I’m grateful to everyone who participated. Read more here: ht…
❤11❤🔥1👍1🙏1
A generic dynamic array in C that stores no capacity and needs no struct Here's an interesting pattern I've found. The following header shows a way to make a generic dynamic array in C with an array of two pointers: • the first pointer stores the length of the dynamic array; • the second pointer points to the data. So, int *vec[2] = { 0 }; is an empty dynamic array of ints. struct person *people[2] = { 0 }; is an e…
❤6👍3
Make external YouTube shorts regular videos I made a small browser extension for YouTube that works together with unhook.app to be able to open external shorts as regular YouTube videos. Unhook is an extension that blocks various distracting things on YouTube. It has an option to block shorts, but that blocks them completely, even if you're opening a link somebody sent to you. My extension fixes this by redirectin…
🔥19👍2❤1
Channel photo updated
Say no to AI generated crap! #wearesoback #cuttheslop (Normal posts coming eventually as well)
💯6🤡5😁2
Ищем Linux мастера для нового Flipper One Мы делаем новый Flipper One — это ARM-компьютер на Linux на базе процессора RK3576. Мы хотим слепить для него свой кастомный дистрибутив. Мы не хотим использовать устаревшие системны обновления вроде Debian APT. Почему классическая система обновлений APT нам не подходит: • Обновление легко может сломаться на середине и система станет не консистентна • Нельзя откатиться к…
❤6🔥3🤓3👍2👎2
More shell tricks: first class lists, jq, and the es shell On the web: https://alurm.github.io/blog/2025-08-07-first-class-lists-in-shells.html Preamble It's not a secret that most common shells don't have first class lists. Sure, you can pass a list to a program by passing each element in argv (e.g. with "$@" or "${list_variable[@]}"), but what if you want to *return* a list? There are a couple of options. The…
🤓11❤9🔥4❤🔥1👍1
Провёл лекцию про Nix в @f0rthsp4ce. Nix это такой язык программирования/пакетный менеджер/способ описывать окружения разработки. По-русски. https://youtube.com/watch?v=noEbul27dHE
👍23🤓4
Turned out a little chaotic. This time the talk is in English. Enjoy! https://youtube.com/watch?v=BzqpjE7lgxw
🔥8👍1
An argument for having trailing slashes in canonical directory paths I was writing some GNU make today and remembered an age old question: "Should canonical directory paths contain a trailing slash (as in dir/) or not (as in dir)?" I always thought that they shouldn't (so, dir). That makes concatenation easy: always do $dir/$suffix. The benefit is that we statically know that $dir must be a directory since the pa…
👍8❤1
C scripting with TCC and Bash How to know what's the value of the constant INT_MAX in the C header <limits.h>? There are many ways. However, here's how I like to do it: by running a script in C. Here it is: $ tcc -run <(printf '%s\n' '#include <'{stdio,limits}'.h>' 'int main() { printf("%u\n", INT_MAX); }') 2147483647 Now that you've seen this, let's take this command line apart, going from the left to the right. …
👍20❤4👎1
Creating pipes with non-standard file descriptors (Да, по-английски.) (Yes, this post is in English.) Today I got curious about creating pipes with non-standard descriptors (not using 0 and 1 for stdin and stdout) bound to them, so I explored that for a bit. Introduction to pipes In most shells, "a | b" syntax signifies a pipeline. The standard output from "a" gets redirected to the standard input of "b" (and no…
🤓6👍1👏1
Showing the 12 most recent of 20 posts we hold for @alurman. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank — 1,025,477 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Alan Urmancheev's channel” (@alurman), 205 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/alurman.
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.