Telegram RegisterThe public register of Telegram

Channel

Yet another senior pomidor (by @gmelikov)

@yetanotherit

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

186subscribers

+1 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-1001881385824
TypeChannel
Username@yetanotherit
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/yetanotherit

Growth

185186185.57 Aug 2026, 17:07 — 185 subscribers8 Aug 2026, 12:16 — 185 subscribers8 Aug 2026, 13:33 — 186 subscribers7 Aug 2026, 17:078 Aug 2026, 13:33
3 measurements taken within a single day, net +1. 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 185–186 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 13:33186+1
8 Aug 2026, 12:16185no change
7 Aug 2026, 17:07185first reading

Engagement

18 posts held, back to 17 January 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
90.3%
avg views ÷ 186 subscribers
Avg views / post
168
1 post measured
Reaction rate
5.36%
reactions ÷ views · ER floor
Posts in window
1
of 18 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 19 July 2026
Posts held18 (17 January 202619 July 2026)
Views total168
Reactions total9
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 12:16 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.

Reaction mix

165 reactions across 18 posts, in 26 distinct kinds. The most used accounts for 18.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁3018.2%
🔥2414.5%
👍127.27%
👀116.67%
106.06%
🤔106.06%
🍾95.45%
💅74.24%
👌63.64%
👨‍💻53.03%
🤝53.03%
🥰53.03%
42.42%
42.42%
💯42.42%
👾31.82%
🤡31.82%
🎉21.21%
👏21.21%
🗿21.21%
6 further kinds74.24%

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

Measured over the 18 most recent posts we hold, published 17 January 2026 to 19 July 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

19 Jul 2026, 17:42 UTC168 views9 reactionsread 8 August 2026
Photo

Был приятно удивлён обнаружить на кинопоиске первые серии нового Призрака в доспехах (2026)! Эта версия максимально близка по духу к оригинальной манге, она точно будет менее серьёзной чем фильм 1995го и оба сезона GITS SAC, и мне нравится что они отличаются. По саундтреку даже чем-то на Cowboy Bebop похоже, кайф!

👍4👀2👏2🤔1

10 Jun 2026, 10:49 UTC269 views4 reactionsread 8 August 2026
Photo

Трудно было не заметить (за собой и окружающими) что во всех каналах/конференциях/чатах, даже если они посвящены узким темам (а я сижу во всяких там iaas/storage/sdn и тд обществах), всё равно бОльшая часть контента и обсуждений сейчас - про ИИ. Тут ещё и MythosFable подъехал. Вот и получается, что основные темы площадок смещаются. Плохо ли это, если надеть шапочку организаторов таких обществ/конференций? Думаю, что

🔥2👀1🥰1

9 Jun 2026, 15:59 UTC237 views8 reactionsread 8 August 2026
Photo

It'sa me, Malwario! В контексте взлома гитхаба через плагин к ide

5🍓1🥰1😁1

22 May 2026, 13:27 UTC364 views8 reactionsread 8 August 2026
Photo

10 июня проведём уже 4й InfraDev Meetup, в этот раз про AI в SDLC инфровой разработки, распределённое обучение LLM, и про более вечное тоже не забудем - проблематика имаджей ОС в облаках. Мск, очно, 10 июня, ламповый зал на ограниченное количество мест, где можно и нужно челленджить спикера прямо с мест, приходите или слушайте онлайн! Увидимся!

🔥4🍾2🎉2

15 May 2026, 19:26 UTC360 views12 reactionsread 8 August 2026

"Мне только спросить". И вот нейронка фигачит тебе то, что ты бы сам откладывал сто лет, а тебе потом это ревьюить.

😁6💯2🤔21🌭1

14 May 2026, 10:25 UTC393 views5 reactionsread 8 August 2026
Photo

О времена, о нравы, нынче поменять язык - дело наличия нормальных тестов. А что говорить о смене лицензии тем же образом... Но это отдельный холивар. 1млн+ строк диффа, даже если это немного фиктивная статистика - мощь.

👀2🍾1👾1🤡1

8 May 2026, 07:57 UTC361 views7 reactionsread 8 August 2026

И следом - ещё очень похожие по эксплуатации local privilege escalation уязвимости с заражением pagecache https://github.com/V4bel/dirtyfrag , только в этот раз что-то пошло не так и фиксов ни в одном дистре ещё нет. tl;dr: sh -c "printf 'install esp4 /bin/false\ninstall esp6 /bin/false\ninstall rxrpc /bin/false\n' > /etc/modprobe.d/dirtyfrag.conf; rmmod esp4 esp6 rxrpc 2>/dev/null; echo 3 > /proc/sys/vm/drop_caches

👀3🥰2😱2

1 May 2026, 09:52 UTC372 views6 reactionsread 8 August 2026

https://copy.fail/ Уязвимость, позволяющая изменить данные в pagecache, с далеко идущими последствиями. Хочется изоляции - без виртуализации никуда.

👍2🤔21👨‍💻1

1 Apr 2026, 19:12 UTC442 views19 reactionsread 8 August 2026
Photo

Photo, posted without a caption

😁14🍾3💅2

18 Mar 2026, 19:27 UTC488 views15 reactionsread 8 August 2026
Photo

Красивые номера в PR и тикетах видели многие, а вот красивый хеш коммита - штука более редкая.

🔥10💅3🤓1🥰1

13 Mar 2026, 14:22 UTC660 views9 reactionsread 8 August 2026
Photo

Картина маслом: LLM бот увидел bounty за баг, и решил подзаработать, а чтобы не упустить шанс - стал каждый час требовать репродьюс. Жаль, что на этом всё и закончилось.

👌4🍾3👨‍💻1👻1

6 Mar 2026, 10:54 UTC465 views9 reactionsread 8 August 2026
Video

https://news.ycombinator.com/item?id=47258500 Очередной тредик про bitflips, как всегда: The common causes we discovered for the problem were: - overclocked CPU - bad memory wait-state configuration - underpowered power supply - overheating due to under-specced cooling fans or dusty intakes

🔥5👍2👾1🤝1

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

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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

“Yet another senior pomidor (by @gmelikov)” (@yetanotherit), 186 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/yetanotherit.

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.