Technology — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
Growth
13 measurements spanning 40 days, net +36. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 3,004–3,055 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
15 Sept 2026, 05:20
3,049
+6
6 Sept 2026, 03:17
3,043
+5
2 Sept 2026, 07:37
3,038
+5
30 Aug 2026, 07:24
3,033
+9
27 Aug 2026, 17:07
3,024
+3
24 Aug 2026, 08:14
3,021
+2
20 Aug 2026, 22:57
3,019
+3
18 Aug 2026, 08:32
3,016
+5
15 Aug 2026, 02:05
3,011
+1
12 Aug 2026, 00:42
3,010
-5
9 Aug 2026, 08:31
3,015
+2
6 Aug 2026, 06:01
3,013
no change
6 Aug 2026, 05:53
3,013
first reading
Engagement
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 3 pages 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 5 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
5m 33s
Average length
1m 51s
Measured directly from 3 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.
Reaction mix
951 reactions across 19 posts, in 26 distinct kinds. The most used accounts for 28.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
274
28.8%
😁
199
20.9%
👍
151
15.9%
❤
93
9.78%
🤡
48
5.05%
😢
33
3.47%
🤯
24
2.52%
🤩
23
2.42%
😱
19
2.00%
🥴
17
1.79%
🤣
15
1.58%
😐
10
1.05%
🤔
8
0.841%
🤮
8
0.841%
💯
7
0.736%
❤🔥
4
0.421%
👏
4
0.421%
🎉
3
0.315%
🙏
3
0.315%
🥰
2
0.21%
6 further kinds
6
0.631%
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 951 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 5 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.
Telegram Stars
Stars received
8
across the posts below
Posts paid on
5
of 20 we hold a reading for · 25%
Most on one post
4
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @localhost_ru. 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 11 February 2026 to 5 August 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.
Сделал библиотеку для отрисовки Compose прямо внутри таскбара Windows
То, что раньше делалось сотнями строк кода через обскурное API на C# - теперь одной строчкой на Kotlin Compose:
fun main() = application {
WindowsTaskBar {
Text("Hello, taskbar")
}
}
Ставьте ⭐️, делайте свои виджеты, создавайте Issues на фичареквесты или баги, все поправлю ❤️
https://github.com/LionZXY/ComposeWindowsTaskBar
Мы наконец выпускаем BUSY Bar (https://busy.bar/)
Многолетняя разработка подошла к концу. Мне тяжело понять какой продукт получился, находясь внутри - глаз замылился.
Пока лучшее его описание для меня - цитата одного из изданий:
It’s overengineered in the best way;
RU: Он переусложнен в лучшую сторону
Простая идея с табличкой занят/не занят доведена до совершенства - rest api через локал и web, умный дом, сверхпрор…
Хоттейк - ИИ увеличит количество рабочих мест в IT
💰📉Эффективность работы увеличиться в 2 раза -> стоимость софта уменьшиться в два раза
📲📈Цена в два раза меньше -> больше бизнесов смогут позволить себе приложения -> количество проектов увеличиться больше чем в два раза (например, в 10)
Что думаете?
Мой любимый браузер, Brave, сделал свою платную версию.
С одноразовой покупкой за 60$ (~4400рублей).
Природа настолько очистилась, что на рынок браузеров вернулись нормальные способы монетизации.
Я очень рад, не хочу чтобы браузер закрылся так же, как это было с моим любимым Arc
https://brave.com/origin/
Наш ex-HRD Flipper Devices ищет новое место.
За ~пять лет работы я успел сменить три страны, съездить на два+ крупных корпоратива и наблюдал рост из компании ~10 человек в ~70.
Все это заслуга, не в последнюю очередь, нашего HRD
И так получилось, что наши пути разошлись, поэтому она сейчас активно ищет новое место где сможет вырастить еще одну крутую команду
Пишите ей, если вам нужен топовый HRD.
Telegram: @flippe…
Flipper One официально анонсирован!
Почитать подробнее:
- На хабре: https://habr.com/ru/companies/flipperdevices/articles/1033162/
- В официальном блоге: https://blog.flipper.net/flipper-one-we-need-your-help/
Android официально отправил Android View на свалку истории
Это старый способ разработки нативного UI под Android, используемый лет пять назад
Теперь Android View будут получать только высоко-критичные фиксы, т.е. дефакто будут заброшены
https://developer.android.com/develop/ui/compose/first
Эпоха софта без zero-day уязвимостей прошла
https://blog.himanshuanand.com/2026/05/the-90-day-disclosure-policy-is-dead/
Теперь:
1) Уязвимость публикуется
2) Спустя день-два выходит патч
3) Спустя пару недель выходит обновление
4) Пользователи обновляются спустя еще пару недель
И все это время (~месяц) уязвимость публична и любой её может проэксплуатировать. Всему виной AI и простота создания PoC.
Только за послед…
Каждый день у меня на телефоне новые обои рабочего стола.
Фото берутся через Resplash с unsplash.com
Сегодня, например, у меня, в качестве фона, налоговая декларация США 🌚
В интернете драма - люди уходят с GitHub из-за его нестабильности
Как его активный пользователь, подтверждаю - это кошмар. Иногда не работают даже базовые git pull/git push
GitHub даже выпустил официальные "извинения": https://github.blog/news-insights/company-news/an-update-on-github-availability/
На HackerNews обвиняют GitHub в лицемерии и напоминают что гитхаб стоит ОЧЕНЬ дорого для его бизнес пользователей. А …
Showing the 12 most recent of 20 posts we hold for @localhost_ru. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Mentions
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@localhost_ru named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@flipperhr named in 1 post, 8 August 2026 – 8 August 2026
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Golden Borodutch @golden_borodutch · 65,429 Telegram ranks this channel #37 of 68 here — alongside 67 others — read 29 August 2026
Tech Debunker @tech_debunker · 23,964 Telegram ranks this channel #51 of 89 here — alongside 88 others — read 17 September 2026
запуск завтра @ctodaily · 33,699 Telegram ranks this channel #84 of 96 here — alongside 95 others — read 4 September 2026
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 15 September 2026 — this
entry's latest reading, not the date you are reading this.
“Локалхост (Никита Куликов)” (@localhost_ru), 3,049 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/localhost_ru.
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.