Telegram RegisterThe public register of Telegram
Telegram profile photo for Dev Math

Channel

Dev Math

@easy_dev_math

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

663subscribers

+155 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003804944770
TypeChannel
Username@easy_dev_math
CreatedBetween 1 February 2026 and 10 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 November 2026
Measurements held15
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/easy_dev_math

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 11 August 2026 and assigned it the closest of 31 fixed categories, at 53% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (1 of the pairs behind the counts below)
Posted firstThenOverlapGap
@dev_game/20145 Aug 2026, 13:09 UTC@easy_dev_math/148 · this entry5 Aug 2026, 13:09 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@dev_game5 (5/5 hand-verifiable sample passed)1.005 minutesthis entry (4–1)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 1 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 18 comparable posts for this entry, running 10 July 2026 to 6 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @easy_dev_math — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

506663584.56 August 2026 — 508 subscribers6 August 2026 — 506 subscribers6 August 2026 — 506 subscribers14 August 2026 — 516 subscribers22 August 2026 — 522 subscribers29 August 2026 — 530 subscribers5 September 2026 — 544 subscribers14 September 2026 — 558 subscribers27 September 2026 — 609 subscribers7 October 2026 — 649 subscribers14 October 2026 — 657 subscribers22 October 2026 — 662 subscribers30 October 2026 — 660 subscribers6 November 2026 — 661 subscribers15 November 2026 — 663 subscribers6 August 202615 November 2026
15 measurements spanning 101 days, net +155. 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 482–687 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Nov 2026, 02:08663+2
6 Nov 2026, 20:16661+1
30 Oct 2026, 13:34660-2
22 Oct 2026, 15:41662+5
14 Oct 2026, 20:21657+8
7 Oct 2026, 17:14649+40
27 Sept 2026, 08:38609+51
14 Sept 2026, 03:01558+14
5 Sept 2026, 19:41544+14
29 Aug 2026, 04:07530+8
22 Aug 2026, 15:47522+6
14 Aug 2026, 17:58516+10
6 Aug 2026, 18:34506no change
6 Aug 2026, 12:00506-2
6 Aug 2026, 03:49508first reading

Engagement

20 posts held, back to 10 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 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

185 reactions across 19 posts, in 7 distinct kinds. The most used accounts for 73.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥13573.0%
❤3217.3%
👍94.86%
😱52.70%
🫡21.08%
👎10.541%
🤝10.541%

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 185 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 10 July 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, 07:40 UTC413 views6 reactionsread 6 August 2026

В Fallout 3 нет ни одного поезда https://youtube.com/shorts/0Dw4ciULxYQ?si=2GqaYJOx-ryyU72f Поездка на метро есть — в дополнении Broken Steel. А поезда нет: движок не умеет катать по миру объект, внутри которого сидит игрок. Он умеет ровно две вещи — водить персонажа и надевать на него предметы. Поэтому вагон сделали одеждой. В файлах он так и лежит: недоступная броня на слот правой руки. Игрок садится — дальше всё…

🔥6

5 Aug 2026, 13:09 UTC120 views10 reactionsread 6 August 2026

Ребята... Мне нужна ваша помощь https://dev-math.ru/support/ Сегодня наверное будет самое сложное для меня. Всегда хочется казаться крутым и что всё получается. Но пора смириться с тем, что рынок на котором я работал последние 7 лет мертв. И с одной стороны это грустно, так как было убито столько времени и сил в развитие своего дела. А с другой это новая возможность. Всем привет. Меня зовут Гриша Дядиченко. Ну про …

❤7🔥3

3 Aug 2026, 12:26 UTC214 views7 reactionsread 6 August 2026
Photo

Гладкость сферы вы видите по свету, а не по форме Мысленный эксперимент: возьмите шарик и покрасьте краской, которая поглощает падающий свет целиком. Что вы увидите? Не чёрный шар — плоское чёрное пятно. Отражать нечего, перетекания из света в тень нет, и шарообразность из картинки просто исчезает. Эксперимент, кстати, не такой уж мысленный. У покрытий вроде Vantablack, забирающих больше 99,9% видимого света, ровно…

🔥7

31 Jul 2026, 15:31 UTC889 views16 reactionsread 6 August 2026
Photo

Почему далёкая текстура мерцает https://dev-math.ru/articles/textures/ Мне очень нравится конечно составлять эти статьи, так как помимо описаний для понимания компьютерной графики, для меня они являются погружением в ностальгическое прошлое. Как всё было придумано и зачем. В статье разберем: - почему тексель — не пиксель и что на самом деле делают nearest и билинейная фильтрация; - откуда берётся мерцание вдали — …

🔥16

31 Jul 2026, 14:53 UTC300 views23 reactionsread 6 August 2026
Photo

Статья немного задерживается, так как автор в ловушке

❤18😱5

29 Jul 2026, 06:00 UTC346 views9 reactionsread 6 August 2026
Photo

Пол вдали превратился в кашу? Смотрите вдоль пола — и метрах в десяти плитка перестаёт быть плиткой. Не мерцает, не рябит, а ровно и мутно мылит, как будто туда забыли положить текстуру. При этом та же самая текстура на стене прямо перед носом читается прекрасно, и под ногами всё резко. Мылит именно то, что уходит вдаль под острым углом: пол, дорога, длинная стена сбоку. Дальше начинается знакомый заход. Раз мыло —…

🔥4❤3🫡2

28 Jul 2026, 05:04 UTC330 views3 reactionsread 6 August 2026

10 000$ за баг в GTA https://youtube.com/shorts/3iJa_wPmGKM?si=pdZ1e-VWVgGtrMhh Семь лет GTA Online грузилась по пять минут — на любом железе. Чинить взялся не Rockstar, а игрок под ником t0st взялся, и хватило ему выходных. И получил за это 10 000$. Оказалось, при каждом входе игра разбирала список из 63 тысяч товаров так, что на каждой позиции пересчитывала всю строку заново. Плюс проверка каждого с каждым на дуб…

🔥2👎1

27 Jul 2026, 14:20 UTC321 views10 reactionsread 6 August 2026
Photo

Фильтрация текстур Подошли в игре вплотную к стене — и вместо кирпича размытое пятно. Можно подумать: «фильтрация мылит, поставлю point». Ставите — мыло уходит, приходят квадратики. Ощущение, что выбираешь между двумя видами испорченной картинки. Так и есть, и вот почему. Текстура для шейдера — не картинка, а функция: подали координату, получили цвет. Только в памяти лежит конечный массив, и значение каждого тексел…

🔥7👍3

24 Jul 2026, 08:56 UTC≈1,150 views7 reactionsread 6 August 2026
Photo

Треугольник становится пикселями https://dev-math.ru/articles/raster/ Вершина добралась до экрана — три точки в пиксельных координатах. Но сам треугольник ещё не закрашен, а на этом коротком отрезке конвейера живёт своя пачка знакомых багов. Разбираем: — почему тонкий провод вдали мерцает и рвётся; — и почему добавить ему полигонов бесполезно; — отчего далёкие поверхности дерутся полосами друг сквозь друга — и при…

🔥6🤝1

23 Jul 2026, 07:16 UTC369 views5 reactionsread 6 August 2026

Мобильный рендер: Дело не в мощности GPU https://youtube.com/shorts/6WtXTERxLaI?si=65mL_ZQZno6b0fdO Так как сейчас у нас недели разбора графики, то я решил попробовать и видосы поделать, как более простой формат подачи информации нежели статьи. Про шину помнить очень важно. Как она загружается и тому подобное. В статье про дроуколлы это разбиралось. Просто где-то с 2017 года я в основном разбирался в том, как запус…

🔥5

22 Jul 2026, 09:28 UTC324 views11 reactionsread 6 August 2026
Photo

Поговорим про Overdraw Сложная сцена проседает по fps. Первым делом вы идёте резать полигоны: упрощаете меши, расставляете LOD'ы, чистите вершины. Треугольников стало заметно меньше — а кадр не полегчал. Профайлер показывает, что видеокарта всё время сидит в пиксельном шейдере, а не в геометрии. Дело в том, что один пиксель за кадр закрашивается не по разу. Поставьте три объекта друг за другом по глубине: дальше вс…

🔥11

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

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

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.

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

“Dev Math” (@easy_dev_math), 663 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/easy_dev_math.

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.