Telegram RegisterThe public register of Telegram
Telegram profile photo for nullptr.party

Channel

nullptr.party

@nullptr_party

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

228subscribers

+32 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002487306327
TypeChannel
Username@nullptr_party
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live28 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 28 September 2026
On Telegramt.me/nullptr_party

Topic

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 24 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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

195228211.57 August 2026 — 196 subscribers8 August 2026 — 196 subscribers23 August 2026 — 197 subscribers29 August 2026 — 195 subscribers8 September 2026 — 212 subscribers15 September 2026 — 216 subscribers28 September 2026 — 228 subscribers7 August 202628 September 2026
7 measurements spanning 51 days, net +32. 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 190–233 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Sept 2026, 02:55228+12
15 Sept 2026, 09:15216+4
8 Sept 2026, 12:57212+17
29 Aug 2026, 15:55195-2
23 Aug 2026, 10:17197+1
8 Aug 2026, 11:46196no change
7 Aug 2026, 22:40196first reading

Engagement

20 posts held, back to 23 April 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

111 reactions across 12 posts, in 6 distinct kinds. The most used accounts for 46.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤5246.8%
🔥3531.5%
👍1917.1%
👏32.70%
👀10.901%
🤔10.901%

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 12 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 111 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 23 April 2026 to 6 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

6 Aug 2026, 05:00 UTC115 views12 reactionsread 8 August 2026
Photo

В прошлую субботу прошла 53-я встреча nullptr.party в Алматы. В этот раз вновь собрались в Воронке. Обсудили: • Оптимизация R8 и ускорение минификации • Прокси OpenAI для Claude Code • Kimi, Qwen и хайп вокруг китайских моделей Спасибо всем, кто пришёл! Те, кто не смог присутствовать, могут присоединиться к обсуждению в группе сообщества almaty.nullptr.party

❤7👍3🔥2

29 Jul 2026, 13:02 UTC189 viewsread 8 August 2026
Photo

Встреча nullptr.party в Алматы #53 Уже в эту субботу 🚀 📅 Когда: 01.08.26 с 17:00 🌐 Где: кофейня «Воронка» 📌 Локация: большой стол в дальнем зале 👇 План встречи: ➡️ Прокси OpenAI для Claude Code • Веб-сокеты, кеширование, ускорение индексации, UX-улучшения и поддержка собственного форка. ➡️ Kimi, Moonshot и хайп вокруг китайских моделей • Сравнение с Claude и GPT, доверие к бенчмаркам и роль государственной подде…

23 Jul 2026, 05:52 UTC402 views7 reactionsread 8 August 2026
Photo

🚀 Ищем спикеров на nullptr.talks[3] 📅 Когда: сентябрь 2026 📍 Где: to be announced ⏰ Заявки принимаем до: 15.08.26 🎯 Что нас интересует: - AI в разработке (практическое применение) - Мобильная разработка (iOS, Android, cross-platform) - Фулстек решения (от API до UI) - Околоразработка (работа лидов, QA, дизайн) 💡 Ищем доклады на русском/казахском ✅ Что важно: - живой опыт из реальных проектов - проблемы, решения…

🔥3❤2👏2

22 Jul 2026, 05:16 UTC178 views8 reactionsread 8 August 2026
Photo

В прошлую субботу прошла 52-я встреча nullptr.party в Алматы. В этот раз вновь собрались в Воронке. Обсудили: • GPT-5.6 Sol: первые впечатления после запуска, реальные кейсы использования и задачи, в которых новая модель показала себя особенно хорошо • ВНЖ по программе Digital Nomad: с какими бюрократическими нюансами можно столкнуться • Тонкости и особенности казахского языка: неоднозначные формулировки, контекст,…

❤8

16 Jul 2026, 05:44 UTC206 views5 reactionsread 8 August 2026
Photo

Встреча nullptr.party в Алматы #52 В эту субботу 🚀 📅 Когда: 18.07.26 с 17:00 🌐 Где: кофейня «Воронка» 📌 Локация: в «Воронке» есть подземелье 👇 План встречи: ➡️ GPT-5.6: Sol, Terra, Luna и новые возможности OpenAI • Сравнение моделей, реальные кейсы использования и первые впечатления после запуска. ➡️ Агентные workflow и выбор моделей • Fable vs Opus, planner/executor, сабагенты, TDD и построение эффективных AI-n…

🔥4❤1

7 Jul 2026, 05:18 UTC241 views15 reactionsread 8 August 2026
Photo

В прошлую субботу прошла 51-я встреча nullptr.party в Алматы. В этот раз собрались в подземелье Воронки. Обсудили: • Почему сегодня всё чаще побеждает не самая сильная LLM, а грамотно выстроенный workflow с агентами, харнессами и хорошей оркестрацией • Новые модели OpenAI (GPT-5.6 Sol, Terra, Luna), чего от них ждать и как меняется подход к релизам перед общим запуском • Vision Pro, Quest и другие XR-устройства: нас…

👍10❤5

3 Jul 2026, 10:56 UTC253 views13 reactionsread 8 August 2026
Photo

Встреча nullptr.party в Алматы #51 Уже завтра 🚀 📅 Когда: 04.07.26 с 17:00 🌐 Где: кофейня «Воронка» 📌 Локация: в «Воронке» есть подземелье 👇 План встречи: ➡️ Fable vs. Opus и агентные харнесы • Что сегодня важнее: качество модели или правильно выстроенный workflow и оркестрация агентов. ➡️ GPT-5.6 Sol, Terra, Luna и новые модели OpenAI • Новая линейка OpenAI, max reasoning, sandbox и сабагенты, и чего ждать после…

❤7🔥3👍2🤔1

11 Jun 2026, 09:46 UTC402 views7 reactionsread 8 August 2026
Photo

Встреча nullptr.party в Алматы #50 В эту субботу 🚀 📅 Когда: 13.06.26 с 17:00 🌐 Где: ЩУКА bistro 📌 Локация: VIP-помещение в дальнем зале справа 👇 План встречи: ➡️ Claude Opus 4.8, Mythos 5 и новые frontier-модели • Последние релизы Anthropic, необычное поведение моделей и новые SOTA-результаты. ➡️ Токен-оптимизация и инструменты для работы с контекстом • rtk, ECC, headroom и другие способы выжимать больше из дост…

👍3🔥3❤1

Showing the 12 most recent of 20 posts we hold for @nullptr_party. 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 2 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.

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.

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 28 September 2026 — this entry's latest reading, not the date you are reading this.

“nullptr.party” (@nullptr_party), 228 subscribers as measured 28 September 2026. Telegram Register, tgregister.com/channel/nullptr_party.

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.