постарался понормальнее сделать документацию к tomlinks

Channel
Разрабская ночь
@nightofdev
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
42,260subscribers
-19,953 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1002626480553 |
|---|---|
| Type | Channel |
| Username | @nightofdev |
| Description | Небольшой блог о разработке |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/nightofdev |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 07:46 | 42,260 | -30 |
| 20 Aug 2026, 23:48 | 42,290 | -22 |
| 19 Aug 2026, 23:12 | 42,312 | -19 |
| 18 Aug 2026, 22:36 | 42,331 | -26 |
| 17 Aug 2026, 19:58 | 42,357 | -27 |
| 16 Aug 2026, 20:08 | 42,384 | -51 |
| 15 Aug 2026, 12:16 | 42,435 | -39 |
| 14 Aug 2026, 00:27 | 42,474 | -67 |
| 12 Aug 2026, 16:04 | 42,541 | -26 |
| 11 Aug 2026, 16:21 | 42,567 | -68 |
| 10 Aug 2026, 16:22 | 42,635 | -18 |
| 9 Aug 2026, 18:21 | 42,653 | -58 |
| 8 Aug 2026, 18:01 | 42,711 | -19,502 |
| 7 Aug 2026, 19:31 | 62,213 | first reading |
Engagement
29 posts held, back to 22 July 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 34 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.468%
- avg views ÷ 42,260 subscribers
- Avg views / post
- 198
- 28 posts measured
- Reaction rate
- 1.01%
- reactions ÷ views · ER floor
- Posts in window
- 28
- of 29 held
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. It is computed over the 10 of 28 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 21 August 2026 |
|---|---|
| Posts held | 29 (22 July 2026 – 21 August 2026) |
| Views total | 5,532 |
| Reactions total | 24 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 23 Aug 2026, 03:37 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.
What this channel posts
- Photos
- 97
- Videos
- 4
- Links
- 164
Lifetime counters from Telegram’s own channel header, read 23 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.
Reaction mix
25 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 32.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🍌 | 8 | 32.0% | |
| 👍 | 8 | 32.0% | |
| ❤ | 3 | 12.0% | |
| 🗿 | 3 | 12.0% | |
| 👾 | 1 | 4.00% | |
| 💘 | 1 | 4.00% | |
| 🔥 | 1 | 4.00% |
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 29 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 25reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 29 most recent posts we hold, published 22 July 2026 to 21 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.
Recent posts
довел tomlinks до рабочего состояния, делаю теперь им бэкапы и восстанавливаю их. Дополнительно конечно эту директорию с бэкапами тоже бэкаплю через restic
Photo, posted without a caption
Немного подразобрался с Odin, нашел в нем свои недостатки, написал небольшой проектик для восстановления бэкапов https://github.com/lunardoesdev/tomlinks
на odin разрабатывают freestanding ядра https://github.com/flysand7/odin-os/blob/main/build.sh
это kotlin toolchain скачивает mingw под линукс чтобы собрать kotlin native проект под винду из-под линукса
👍2
jetbrains что-то придумывает на смену gradle, если верить документации то оно уже умеет работать с андроид, ios, kmp и десктопными проектами https://kotlin-toolchain.org/dev/
👍1
Первый проект который я попытаюсь делать не как обычно, а сначала планируя и разбивая на задачи, а потом делая их по одной не отвлекаясь на остальные, и так чтоб с перерывами. Вдруг будет получше чем с другими проектами https://github.com/lunardoesdev/flappy-melon
🍌3❤1🗿1
Я еще раз заглянул на различные фрилансы и места где размещают вакансии. Снова могу сказать все то же самое: - требования неадекватные, хотят человека все-в-одном за копейки и еще будут спрашивать за результат и оспаривать необходимость платить за работу - при этом откликов огромное количество, от ботов или от отчаявшихся людей. Может так кто-то и сможет устроиться на подобную работу, но через месяц-два этому не буду…
❤2🗿2🍌1
ну в целом чуть поработал, дальше труднее, боты с никами, кто-то с датой рождения, с аватарками, очень правдоподобные. Было интересно, написал многопоточный баннер на четырех админ-ботов, а список пользователей брал через клиентское телеграм апи, скорость дошла до 200 банов за 7 секунд, теперь затык в том что вот этих менее подозрительных ботов не удалишь руками - до остальных более простых не доберешься
🍌2👍1
Интересная задачка свалилась на мою голову - 60 000 ботов зашли на канал. Я написал пару скриптов, боты постепенно будут забанены. Все.
🍌1👍1
Сегодня пытался разобраться в чужом андроид-проекте, писал e2e тест, ничего не получилось. Для е2е теста нужно множество импортов, как-то откопать из этой очень сложной стркутуры какую-то суть проекта, найти modelView или хотя бы понять что это такое, очень много недокументированного непонятного бойлерплейта. Все-таки мне хочется писать код и ощущать что делаю что-то важное, а не что ковыряюсь в непонятной структуре …
🍌1
Showing the 12 most recent of 29 posts we hold for @nightofdev. 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.
Cite this entry
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“Разрабская ночь” (@nightofdev), 42,260 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/nightofdev.
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.