Telegram RegisterThe public register of Telegram

Channel

Cross Join - канал о разработке

@crossjoin

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

3,808subscribers

-3 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-1001349292097
TypeChannel
Username@crossjoin
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live11 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/crossjoin

Growth

3,8083,8113,809.56 August 2026 — 3,811 subscribers7 August 2026 — 3,810 subscribers11 August 2026 — 3,808 subscribers6 August 202611 August 2026
3 measurements spanning 4 days, net -3. 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 3,808–3,811 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 02:513,808-2
7 Aug 2026, 17:013,810-1
6 Aug 2026, 21:183,811first reading

Engagement

15 posts held, back to 20 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 4 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
45.0%
avg views ÷ 3,808 subscribers
Avg views / post
1,720
5 posts measured
Reaction rate
2.90%
reactions ÷ views · ER floor
Posts in window
5
of 15 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 5 August 2026
Posts held15 (20 May 20265 August 2026)
Views total8,577
Reactions total249
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 06:11 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

475 reactions across 14 posts, in 19 distinct kinds. The most used accounts for 26.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍12726.7%
💯9820.6%
🔥8918.7%
🤣479.89%
😁296.11%
🤡234.84%
224.63%
🌚112.32%
🐳81.68%
👎30.632%
💊30.632%
🤯30.632%
20.421%
🖕20.421%
🗿20.421%
😭20.421%
🥰20.421%
🙈10.211%
🤬10.211%

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

Measured over the 15 most recent posts we hold, published 20 May 2026 to 5 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

5 Aug 2026, 14:27 UTC797 views23 reactionsread 8 August 2026
Forwarded from @doowhile

Типовые косяки агентов (август 2026) У меня есть сложный проект, в котором 99% кода написано AI (код уровня подсистем ядра Linux и секурити: eBPF LSM, TPROXY, fanotify). На нём отлично видно, как кодинговые агенты лажают. Наиболее типичные ошибки, которые я замечаю: - Автоматические тесты через агента тестируют не реальные сценарии. Например, у юзера стартует один сервис, а в плейбуке в момент тестирования создает

👍13💯10

Signed Anton Okolelov

4 Aug 2026, 07:03 UTC≈1,010 views42 reactionsread 8 August 2026
Photo

RYBE — одежда с твоим языком программирования (JavaScript, Python, QA, SQL, ML-engineer, Rust и другие) Где два айтишника могут познакомиться? В офисе и на конференции. Нам этого мало. Мы захотели объединить людей, у которых одни интересы. Дать возможность узнать друг друга. В метро, на прогулке, в офисе, на конференции, в походе, в баре, в самолёте. В каком-то смысле это мерч для твоего языка программирования. А

🤡196🌚5👎3👍2🖕2🗿2😭2

Signed Anton Okolelov

31 Jul 2026, 10:19 UTC≈1,800 views48 reactionsread 8 August 2026
Photo

GitHub добавил stacked pull requests GitHub запустил публичное тестирование stacked pull requests — цепочек связанных PR, которые нужно сливать по порядку. main └ branch-1 → PR 1 └ branch-2 → PR 2 └ branch-3 → PR 3 Например: PR 1 добавляет новую структуру данных; PR 2 использует её в API; PR 3 добавляет интерфейс. Такую цепочку можно было собрать и раньше, но следить за ветками, их порядком и обновл

🔥41👍52

Signed Anton Okolelov

24 Jul 2026, 08:38 UTC≈2,570 views103 reactionsread 8 August 2026

Прогать с агентом зачастую выматывает сильнее, чем без него. Сначала надо сгенерить код. Это кажется просто, но перед этим действием нужно уже провести много работы, продумать требования и нюансы (ибо магии нет: говно на входе = говно на выходе). План-хуян. Потом наконец генеришь и даёшь другому агенту на ревью. Если код сложный, то в 99% случаев что-то вылезает. Ладно, чинишь. Даёшь другому агенту посмотреть. Вы

💯75👍21🤣421

Signed Anton Okolelov

16 Jul 2026, 06:17 UTC≈2,400 views33 reactionsread 8 August 2026

https://deployhoroscope.com/

😁26🤡4👍2🙈1

Signed Anton Okolelov

7 Jul 2026, 06:15 UTC≈3,020 views21 reactionsread 8 August 2026

Apple запилила свой докер apple/container — это CLI-инструмент для создания и запуска Linux-контейнеров на Mac. Релиз 1.0 был пару недель назад. Написан на Swift, разработан для Apple silicon. Работает с OCI-совместимыми образами, то есть умеет тянуть и пушить образы из обычных container registry. Apple прямо описывает его как инструмент для запуска Linux containers as lightweight virtual machines на Mac. Docker De

🔥183

Signed Anton Okolelov

29 Jun 2026, 07:36 UTC≈2,620 views13 reactionsread 8 August 2026

Оказывается, новый http-метод QUERY опубликован как RFC 10008

🔥13

Signed Anton Okolelov

22 Jun 2026, 16:15 UTC≈3,310 views60 reactionsread 8 August 2026

Что меня бесит в ИИ - это то, что как ему ни описывай задание, хоть максимально подробно и с утверждением плана, всё равно есть пространство для манёвра, где агент сам принимает решение, о котором ты не узнаешь, пока не получишь граблями по башке. Никакой спек-дривен девелопмент не поможет. Ты не можешь описать вообще все нюансы в мире, проще тогда код написать самому на формальном языке (языке программирования).

👍45💯13🌚2

Signed Anton Okolelov

20 Jun 2026, 07:47 UTC≈2,530 views48 reactionsread 8 August 2026
Photo

Вайбкодеры объясняют про айти. Это ржака Прод у них по ночам самообновляется и падает, капец

🤣43🌚4🤬1

Signed Anton Okolelov

19 Jun 2026, 12:26 UTC≈2,610 views6 reactionsread 8 August 2026

Посоветуйте плиз подкасты айтишные, такие, чтоб полезно было. Какую-то дельную мысль чтобы можно было вынести. Я слушаю "Организованное программирование", "Три тимлида заходят в бар", "Подлодка". Другие тоже есть в плейлисте, но они скорее развлекательные, чем полезные. Вдруг что-то упускаю. По-русски, по-английски или по-чешски (ну, а вдруг)

6

Signed Anton Okolelov

14 Jun 2026, 06:01 UTC≈2,520 views13 reactionsread 8 August 2026
Photo

Вот такой получился график % кода, написанного с помощью ии-агентов в динамике. Очень, конечно, быстро всё меняется. Еще в начале декабря только избранные писали весь код ии-шкой, а сейчас это норма. А прошло каких-то жалких полгода. И ничего не устаканилось, динамика по-прежнему бешеная. На рынке труда тоже происходит что-то странное - с одной стороны массовые увольнения программистов "из-за AI" в бигтехах, с друг

👍10💊3

Signed Anton Okolelov

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

Citation-graph rank

Citation-graph rank — 209,889 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

Named by 1 registered channel — 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.

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

“Cross Join - канал о разработке” (@crossjoin), 3,808 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/crossjoin.

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.