API описали дважды: людям и агентам Команда ApyHub построила MCP-сервер, чтобы ассистенты вроде Claude дёргали их API. Через пару релизов выяснилось: описание одного и того же API живёт в двух местах и расходится. Ручной MCP-сервер — это вторая кодовая база поверх уже готовых запросов. Переименовал поле, забыл поправить — агент ломается молча, без предупреждений. В Voiden запросы лежат в репозитории как Markdown, …

Channel
NOP::Nuances of Programming
@nuancesprog
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
56,542subscribers
-541 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001120605809 |
|---|---|
| Type | Channel |
| Username | @nuancesprog |
| Description | Любые вопросы по сотрудничеству: @ramilkr Если нужен токен: https://telega.in/c/nuancesprog NOP::Humor - https://t.me/nophumor NOP::Recruiter Удаленка- https://t.me/nopremote РКН: 4977653520 |
| Created | 7 July 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/nuancesprog |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 00:18 | 56,542 | -30 |
| 15 Sept 2026, 17:16 | 56,572 | -27 |
| 14 Sept 2026, 03:16 | 56,599 | -25 |
| 12 Sept 2026, 09:22 | 56,624 | -31 |
| 10 Sept 2026, 02:59 | 56,655 | -47 |
| 6 Sept 2026, 21:57 | 56,702 | -22 |
| 4 Sept 2026, 09:21 | 56,724 | -28 |
| 2 Sept 2026, 18:39 | 56,752 | -8 |
| 1 Sept 2026, 15:16 | 56,760 | -19 |
| 31 Aug 2026, 15:53 | 56,779 | -1 |
| 30 Aug 2026, 18:02 | 56,780 | -11 |
| 29 Aug 2026, 14:26 | 56,791 | -14 |
| 28 Aug 2026, 12:13 | 56,805 | -13 |
| 27 Aug 2026, 11:09 | 56,818 | -10 |
| 26 Aug 2026, 13:03 | 56,828 | -9 |
| 25 Aug 2026, 10:26 | 56,837 | -7 |
| 24 Aug 2026, 13:47 | 56,844 | -30 |
| 22 Aug 2026, 20:07 | 56,874 | -16 |
| 21 Aug 2026, 11:47 | 56,890 | -10 |
| 20 Aug 2026, 14:52 | 56,900 | first reading |
Engagement
164 posts held, back to 8 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 107 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.82%
- avg views ÷ 56,542 subscribers
- Avg views / post
- 2,160
- 90 posts measured
- Reaction rate
- 0.207%
- reactions ÷ views · ER floor
- Posts in window
- 90
- of 164 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 89 of 90 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 27 September 2026 |
|---|---|
| Posts held | 164 (8 July 2026 – 27 September 2026) |
| Views total | 194,556 |
| Reactions total | 401 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 16:26 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
- ≈4,300
- Videos
- ≈11
- Links
- ≈5,640
Lifetime counters from Telegram’s own channel header, read 27 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
593 reactions across 134 posts, in 2 distinct kinds. The most used accounts for 96.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 571 | 96.3% | |
| 👎 | 22 | 3.71% |
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 134 of the 164 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 593 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 164 most recent posts we hold, published 8 July 2026 to 27 September 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
F-Droid 2.0: первый крупный редизайн за 10 лет Открытый каталог Android-приложений выпустил версию 2.0 после 14 тестовых релизов. Интерфейс переписали на Kotlin Compose, а навигацию свели к трём разделам: Discover, Search и My Apps. Поиск теперь смотрит не только на названия, но и на описания, категории и переводы. Фильтры комбинируются по совместимости с устройством и антифичам — например, можно спрятать приложени…
👍3
Robert O'Callahan прощается с Google Автор записи — Роберт О'Каллаган, создатель rr, отладчика с перемоткой выполнения назад. В сентябрьском посте он объявляет об уходе из Google. Роберт много лет двигал тему отладки: сначала Mozilla и Firefox, потом rr и Pernosco. Его уходы из больших компаний обычно заканчивались новыми инструментами для нас. В открытом виде текст поста нам не отдался — на странице видно только …
👍1
ESP32-S31: микроконтроллер, на котором заводится Linux Espressif выпустила ESP32-S31 с гигабитным Ethernet, USB 2.0 Host и двумя слотами SD. Внутри два RISC-V ядра на 320 МГц и настоящий MMU с Sv32 и тремя режимами привилегий. Именно MMU меняет всё: ядро Linux запускается в supervisor-режиме, как на обычных RISC-V машинах. Espressif уже выложила BSP на Buildroot и U-Boot, а сообщество подняло ядро 6.18 с рабочими д…
👍7
Kafka учится зеркалить кластеры без внешних воркеров KIP-1279 встраивает межкластерную репликацию прямо в брокер Kafka. Брокер-приёмник тянет записи тем же fetch-протоколом, что и обычные реплики. Смещения (offset) сохраняются один в один, включая пропуски после компакции. Сжатые батчи копируются байт в байт, без цикла распаковки и повторного сжатия. Переключение при аварии сводится к --stop и перенаправлению клие…
👍5
Claude Code читает AGENTS.md только с включённой телеметрией Поддержку AGENTS.md в Claude Code спрятали за удалённым флагом tengu_agents_md_mod. Если выключить телеметрию через DISABLE_TELEMETRY=1, флаг не приходит и файл молча игнорируется. Чтение файла с локального диска внезапно зависит от сети и сервера Anthropic. Предупреждения нет: модель просто отвечает без твоих инструкций, а ты правишь промпты. Обходной п…
👍1
📬 Дайджест недели Лучшее за неделю: • OpenJev: решения агента из логитов, а не из JSON • Claude Opus 5.5: дешевле, быстрее и с новыми ограничениями • ZCode тихо заливает всю историю Git в облако • Как Ryzen стал быстрее на 50% за два года • ZCode от Z.ai молча выгружает твою .git-историю в облако • gzip как языковая модель: генерация текста без нейросетей • Папский шифр 1542 года вскрыли имитацией отжига Мимо ленты…
👍4
Очередной BGP-хайджек: под удар попал поставщик хостинг-софта Блог APNIC разбирает свежий случай перехвата маршрутов у вендора программного обеспечения для хостинга. Чужая автономная система анонсировала его префиксы и на время притянула трафик к себе. BGP до сих пор верит анонсам на слово, поэтому такой перехват технически доступен многим. Пока трафик идёт мимо, атакующий может выпустить TLS-сертификат и подменить…
👍4
Спираль выгорания сеньора: как в неё попадают Санил Пай описал частый сценарий: инженер получает новую роль и решает доказать свою крутость. Он берётся за амбициозный проект, пропадает на три недели и кормит команду «всё идёт хорошо». Дальше включается спираль: работы не видно, значит надо пахать ещё больше. Финал предсказуем — бессонница, выгорание, PIP или увольнение по собственному. Совет автора контринтуитивен…
👍5
Как Ryzen стал быстрее на 50% за два года Дэниел Лемир прогнал свои микробенчмарки на двух соседних поколениях Ryzen. Разрыв дошёл почти до 50% при сопоставимой тактовой частоте. Значит, дело в микроархитектуре: более широкий декодер и точнее предсказание переходов. Твой код может ускориться заметно, без единой правки в исходниках. Подвох в том, что на синтетике разрыв всегда красивее реального. Память и диск легк…
👍8
gzip как языковая модель: генерация текста без нейросетей Натан собрал GziPT — генератор текста, где вместо весов работает обычный zlib. Он подмешивает корпус Шекспира в окно сжатия и ищет продолжение, которое жмётся лучше всех. Это наглядная иллюстрация равенства сжатия и предсказания: -log2(p) бит на символ. Любой компрессор внутри себя хранит вероятностную модель, даже если её никто не писал. Подвох в том, что …
👍4
Claude Opus 5.5: дешевле, быстрее и с новыми ограничениями Anthropic выпустила Claude Opus 5.5 — первую модель семейства 5.5. Она на 40% дешевле Opus 5 в типичных задачах и выдаёт ответ на 30% быстрее. Особенно подешевело чтение кэша — $0.20 за миллион токенов вместо прежних $0.50. Для агентских сценариев и работы с кодом это основная статья расходов. Сама Anthropic признаёт: разрыв с конкурентами в реальной работ…
👍8
Showing the 12 most recent of 164 posts we hold for @nuancesprog. 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.
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 4 registered channels — 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.
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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
@proglibrary · 78,288#1
@bzd_channel · 36,402#2
@thecodemedia · 49,232#3
@ithumor · 60,568#4
@habr_com · 132,465#5
@codeclean · 12,039#6
@webb_dev · 8,299#7
@tproger_web · 22,429#8
@front_end_dev · 25,875#9
@frontendnoteschannel_ru · 31,430#10
@frontendproglib · 20,930#11
@github · 155,991#12
@pyproglib · 37,384#13
@goproglib · 24,076#14
@ai_machinelearning_big_data · 279,417#15
@denissexy · 137,610#16
@techrocks · 12,886#17
@Golang_google · 40,461#18
@pythonist_ru · 24,046#19
@nopremote · 4,988#20
@frontend_mind · 6,327#21
@prog_tools · 12,927#22
@prog_point · 18,040#23
@Social_engineering · 125,008#24
@open_source_friend · 52,304#25
@hahacker_news · 25,571#26
@haccking · 63,183#27
@maschinelearning · 10,823#28
@we_use_js · 10,795#29
@bookflow · 15,607#30
@python2day · 63,764#31
@code_m0de · 10,783#32
@developer_shelf · 26,815#33
@data_secrets · 94,138#34
@senior_front · 19,323#35
@xor_journal · 182,317#36
@neuro_channel · 11,778#37
@python_academy · 44,284#38
@codeby_sec · 37,041#39
@mobi_dev · 13,170#40
@SecLabNews · 84,654#41
@dsproglib · 18,339#42
@backend_it · 18,983#43
@web_stack · 4,131#44
@t0digital · 28,475#45
@csharpproglib · 21,700#46
@procode404 · 40,506#47
@codeblog · 10,462#48
@structuredata · 7,691#49
@techskill · 14,261#50
@tproger · 78,305#51
@nophumor · 7,569#52
@dvachannel · 938,773#53
@g_code · 14,872#54
@rozetked · 656,361#55
@codecamp · 181,043#56
@bugfeature · 571,363#57
@d_code · 406,147#58
@thingsprogrammersdo · 16,037#59
@physics_lib · 146,712#60
@techno_media · 790,765#61
@zen_of_python · 18,830#62
@addmeto · 71,835#63
@retra · 165,571#64
@itmemes · 123,290#65
@black_triangle_tg · 63,850#66
@ai_newz · 96,889#67
@Reddit · 162,484#68
@theaftertimes · 16,799#69
@remedia · 698,207#70
@seniorFront · 23,904#71
@javaproglib · 22,022#72
@unilecs · 15,433#73
@seniorsoftwarevlogger · 22,808#74
@NeuralShit · 53,680#75
@dataleak · 119,401#76
@mintsifry · 234,926#77
@programmer_memes · 51,307#78
@seniorpy · 39,864#79
@seeallochnaya · 79,594#80
@nsmag · 191,658#81
@exploitex · 2,048,279#82
@whackdoor · 1,603,481#83
@progeri · 15,108#84
Read from Telegram’s recommendation API, most recently 23 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
@bzd_channel · 36,402
Telegram ranks this channel #5 of 57 here — alongside 56 others — read 1 September 2026
@thecodemedia · 49,232
Telegram ranks this channel #6 of 97 here — alongside 96 others — read 25 August 2026
@pythonist_ru · 24,046
Telegram ranks this channel #7 of 82 here — alongside 81 others — read 17 September 2026
@procode404 · 40,506
Telegram ranks this channel #8 of 83 here — alongside 82 others — read 30 August 2026
@proglibrary · 78,288
Telegram ranks this channel #9 of 82 here — alongside 81 others — read 19 August 2026
@tproger_web · 22,429
Telegram ranks this channel #11 of 96 here — alongside 95 others — read 20 September 2026
@python_academy · 44,284
Telegram ranks this channel #22 of 87 here — alongside 86 others — read 28 August 2026
@frontendproglib · 20,930
Telegram ranks this channel #24 of 93 here — alongside 92 others — read 25 September 2026
@sitodel · 25,725
Telegram ranks this channel #29 of 89 here — alongside 88 others — read 13 September 2026
@pyproglib · 37,384
Telegram ranks this channel #29 of 84 here — alongside 83 others — read 1 September 2026
@trendo · 67,788
Telegram ranks this channel #31 of 90 here — alongside 89 others — read 20 August 2026
@front_end_dev · 25,875
Telegram ranks this channel #32 of 95 here — alongside 94 others — read 13 September 2026
@EnglishScript · 45,107
Telegram ranks this channel #35 of 82 here — alongside 81 others — read 27 August 2026
@eruditurl24 · 97,352
Telegram ranks this channel #38 of 86 here — alongside 85 others — read 16 August 2026
@iworldcom · 32,093
Telegram ranks this channel #39 of 73 here — alongside 72 others — read 5 September 2026
@pythonist24 · 55,872
Telegram ranks this channel #40 of 88 here — alongside 87 others — read 23 August 2026
@tbite · 28,050
Telegram ranks this channel #41 of 85 here — alongside 84 others — read 9 September 2026
@porscode_tg · 28,393
Telegram ranks this channel #46 of 77 here — alongside 76 others — read 9 September 2026
@developer_shelf · 26,815
Telegram ranks this channel #48 of 63 here — alongside 62 others — read 11 September 2026
@iznytri · 80,259
Telegram ranks this channel #48 of 85 here — alongside 84 others — read 18 August 2026
@physics_lib · 146,712
Telegram ranks this channel #51 of 72 here — alongside 71 others — read 13 August 2026
@slovar_psikhologia · 83,517
Telegram ranks this channel #52 of 91 here — alongside 90 others — read 18 August 2026
@javalib · 30,666
Telegram ranks this channel #53 of 84 here — alongside 83 others — read 7 September 2026
@frontendnoteschannel_ru · 31,430
Telegram ranks this channel #53 of 95 here — alongside 94 others — read 6 September 2026
This channel appears in 34 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“NOP::Nuances of Programming” (@nuancesprog), 56,542 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/nuancesprog.
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.