Telegram RegisterThe public register of Telegram
Telegram profile photo for @yegor256 news

Channel

@yegor256 news

@yegor256news

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry

8,892subscribers

-17 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001158157932
TypeChannel
Username@yegor256news
Created6 October 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live16 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/yegor256news

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

8,8718,9138,8926 August 2026 — 8,909 subscribers6 August 2026 — 8,909 subscribers6 August 2026 — 8,908 subscribers9 August 2026 — 8,913 subscribers11 August 2026 — 8,904 subscribers14 August 2026 — 8,900 subscribers18 August 2026 — 8,904 subscribers21 August 2026 — 8,882 subscribers24 August 2026 — 8,887 subscribers30 August 2026 — 8,888 subscribers2 September 2026 — 8,890 subscribers8 September 2026 — 8,872 subscribers12 September 2026 — 8,871 subscribers16 September 2026 — 8,892 subscribers6 August 202616 September 2026
14 measurements spanning 41 days, net -17. 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 8,865–8,919 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 05:218,892+21
12 Sept 2026, 02:568,871-1
8 Sept 2026, 02:388,872-18
2 Sept 2026, 17:278,890+2
30 Aug 2026, 20:388,888+1
24 Aug 2026, 11:478,887+5
21 Aug 2026, 06:038,882-22
18 Aug 2026, 07:228,904+4
14 Aug 2026, 22:278,900-4
11 Aug 2026, 22:138,904-9
9 Aug 2026, 05:528,913+5
6 Aug 2026, 12:528,908-1
6 Aug 2026, 02:528,909no change
6 Aug 2026, 01:508,909first reading

Engagement

22 posts held, back to 16 May 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 30 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 22 posts for this entry, the most recent from 19 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 19s
Average length
1m 19s

Measured directly from 1 video 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

1,022 reactions across 22 posts, in 2 distinct kinds. The most used accounts for 77.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤79677.9%
👎22622.1%

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 22 of the 22 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 1,022 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 16 May 2026 to 19 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
15
across the posts below
Posts paid on
7
of 22 we hold a reading for · 32%
Most on one post
8
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @yegor256news. 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 22 most recent posts we hold for this entry, published 16 May 2026 to 19 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.

Recent posts

19 Aug 2026, 06:52 UTC≈2,040 views11 reactions1 Starread 28 August 2026

This is the last call for paper submissions to the 6th ICCQ, sponsored by IEEE and indexed in Scopus. CfP closes on the 27th of August. The conference focuses on source code quality, better programming practices, and software maintainability. Don't miss it this year — be brave and submit.

❤10👎1

Signed Yegor Bugayenko

18 Aug 2026, 13:01 UTC≈2,690 views61 reactions1 Starread 28 August 2026
Photo

17-го октября в 12:00, в Нижнем Новгороде на ITGorky выступлю с разговором о типичных ошибках опен-сорс разработчиков, особенно ярко проявляющихся в эру ИИ. Вход бесплатный, но нужна регистрация. Будет видео запись, но вы приходите.

❤61

Signed Yegor Bugayenko

3 Aug 2026, 09:11 UTC≈4,340 views12 reactionsread 28 August 2026

Can someone create an open source Java library with a JUnit extension to provide tests with an ephemeral (random) TCP port as argument? We need it badly for EO runtime library testing. Should work like this: @ExtendWith( EphemeralResolver.class) class FooTest { @Test void f(@Ephemeral int port) { // Here we know the "port" // is random // and doesn't conflict // with other processes // and o…

❤12

Signed Yegor Bugayenko

30 Jul 2026, 04:57 UTC≈7,430 views24 reactions1 Starread 28 August 2026
Photo

The 6th ICCQ conference has been granted in-cooperation status by the IEEE. Accepted papers will be published in IEEE Xplore and indexed in Scopus. The CfP deadline is about three weeks away, on August 17 — so there's still time to submit your work. This year, Patrick Cousot is our keynote speaker, and our Program Committee includes three ACM Fellows: Doug Lea, Benjamin Pierce, and Philip Wadler. It's the strongest l…

❤24

Signed Yegor Bugayenko

21 Jul 2026, 08:54 UTC≈5,770 views45 reactions1 Starread 28 August 2026
Photo

The team is busy. Calls are happening. But the real question is: are they actually working or just looking busy? I gave the talk during DevOn Summit 2017 in Delft, The Netherlands, where I break down the four main killers of productivity that exist in almost every engineering team: endless meetings, useless documentation, the strange role of managers, and the illusion of control; and the alternative of how to manage …

❤37👎8

Signed Yegor Bugayenko

17 Jul 2026, 08:31 UTC≈5,790 views34 reactionsread 28 August 2026
Photo

Just released a new LaTeX package on CTAN: handstroke. It makes underline more artistic. I already use it in both Angry Tests volumes and intent to use in all slidedecks and other books too. Feel free to use and/or contribute: yegor256/handstroke.

❤31👎3

Signed Yegor Bugayenko

16 Jul 2026, 06:58 UTC≈6,180 views35 reactionsread 28 August 2026
Photo

KaiCode, our annual festival of open source projects, is announcing winners of the 2026 competition (and rewarding some cash to help them grow): raprogramm/yew-nav-link 6★ Perfect $2048 ahoo-wang/wow 296★ Excellent $1024 choplogic/chop-logic-components 5★ Awesome $512 These projects were selected out of all 153 submitted this year. As you see, popularity didn't matter, but only the quality of code, discipline of …

❤35

Signed Yegor Bugayenko

13 Jul 2026, 07:20 UTC≈4,590 views38 reactions2 Starsread 28 August 2026
Photo

I've just published a new blog post: Rat's Skills. The piece is summarizing what equipment you may need to win a power game in the office and get a promotion. I tried to stay practical and concise. It's a long read, but I hope you find if funny.

❤35👎3

Signed Yegor Bugayenko

10 Jul 2026, 07:32 UTC≈4,910 views28 reactionsread 28 August 2026
Photo

We've published a new set of benchmarks for Java Stream API: objectionary/sabj25. Unlike all other existing benchmarks, our set covers the entire Stream API of JDK 25. We used these new benchmarks to verify the effect of optimization of Java bytecode by our hone-maven-plugin. Quick conclusion: we can make some Stream pipelines 2x faster.

❤28

Signed Yegor Bugayenko

7 Jul 2026, 06:40 UTC≈7,730 views146 reactions8 Starsread 28 August 2026
Photo

Артемий Лебедев убежден: великий русский язык, ежели запретить в нем обсценную лексику, величие свое непременно утратит. Возможно. Однако всему свое время, Артемий, и свое место. Скажем, тело твое без срамного уда тоже красоту свою утратит. Но не станешь же ты выставлять свой орган на всеобщее обозрение в офисе. Потому что воспитание ты получил соответствующее. Любимой женщине похабщину на ушко шептать да в краску ее…

❤116👎30

Signed Yegor Bugayenko

6 Jul 2026, 07:55 UTC≈5,020 views44 reactionsread 28 August 2026
Photo

I'm spending about 30 million Anthropic tokens via Claude Code, working 6-7 days per week. What's your mileage?

❤24👎20

Signed Yegor Bugayenko

1 Jul 2026, 17:03 UTC≈11,900 views76 reactionsread 28 August 2026
Photo

Новое интервью у меня на YouTube и VK, с Сергеем Марковым, руководителем разработки ИИ-проектов в Сбере. Обсудили главное: победят ли нас машины? Пришли к выводу, что... Хотя, смотрите сами (with English and Russian subtitles).

❤70👎6

Signed Yegor Bugayenko

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

Posts edited after publishing

@yegor256news edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
20 August 2026
Most recent edit
20 August 2026

Forward network

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 5 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.

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.

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.

Диджитализируй!
@t0digital · 28,573
Telegram ranks this channel #50 of 88 here — alongside 87 others — read 9 September 2026
Осознанная Меркантильность | Антон Назаров
@m0rtymerr_channel · 80,213
Telegram ranks this channel #69 of 87 here — alongside 86 others — read 18 August 2026
Java библиотека
@javalib · 30,666
Telegram ranks this channel #74 of 84 here — alongside 83 others — read 7 September 2026
Библиотека джависта | Java, Spring, Maven, Hibernate
@javaproglib · 22,055
Telegram ranks this channel #88 of 88 here — alongside 87 others — read 21 September 2026
Alek OS
@Alek_OS · 32,932
Telegram ranks this channel #93 of 95 here — alongside 94 others — read 4 September 2026
Владилен: IT в эпоху AI
@vladm · 39,307
Telegram ranks this channel #93 of 96 here — alongside 95 others — read 30 August 2026

This channel appears in 6 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 16 September 2026 — this entry's latest reading, not the date you are reading this.

“@yegor256 news” (@yegor256news), 8,892 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/yegor256news.

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.