Telegram RegisterThe public register of Telegram

Channel

Находки в опенсорсе

@opensource_findings

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Citations · Handles named that no longer answer · Cite this entry

11,638subscribers

+21 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001233907704
TypeChannel
Username@opensource_findings
Created6 August 2019measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/opensource_findings

Growth

11,61611,63811,6276 August 2026 — 11,617 subscribers6 August 2026 — 11,617 subscribers6 August 2026 — 11,616 subscribers7 August 2026 — 11,622 subscribers8 August 2026 — 11,628 subscribers9 August 2026 — 11,631 subscribers10 August 2026 — 11,630 subscribers11 August 2026 — 11,635 subscribers12 August 2026 — 11,633 subscribers13 August 2026 — 11,638 subscribers6 August 202613 August 2026
10 measurements spanning 7 days, net +21. 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 11,613–11,641 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 12:1611,638+5
12 Aug 2026, 09:4611,633-2
11 Aug 2026, 07:5811,635+5
10 Aug 2026, 07:1611,630-1
9 Aug 2026, 08:3111,631+3
8 Aug 2026, 05:0511,628+6
7 Aug 2026, 04:5011,622+6
6 Aug 2026, 05:4011,616-1
6 Aug 2026, 03:0011,617no change
6 Aug 2026, 02:5311,617first reading

Engagement

20 posts held, back to 9 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 16 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
58.7%
avg views ÷ 11,638 subscribers
Avg views / post
6,830
4 posts measured
Reaction rate
2.63%
reactions ÷ views · ER floor
Posts in window
4
of 20 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 4 August 2026
Posts held20 (9 May 20264 August 2026)
Views total27,320
Reactions total718
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Aug 2026, 03:58 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.

What this channel posts

Video runtime
23s
Average length
23s

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

2,957 reactions across 20 posts, in 18 distinct kinds. The most used accounts for 27.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥82027.7%
👍78426.5%
56419.1%
😁1876.32%
🕊1725.82%
🤡913.08%
👎852.87%
🤯742.50%
🤔571.93%
💩421.42%
😱240.812%
🤮190.643%
👏140.473%
🥰90.304%
😢50.169%
👌40.135%
🎉30.101%
🙏30.101%

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 20 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 2,957reactions 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 9 May 2026 to 4 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
38
across the posts below
Posts paid on
15
of 20 we hold a reading for · 75%
Most on one post
10
single highest reading

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

Advertising

Ad load
10.0%
2 of 20 posts carry an ad marker
Regulatory tokens
2
posts carrying an erid · 2 distinct tokens
Median views · ads
8,040
over 2 measured posts
Median views · rest
9,580
over 18 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VfnxvSxct3110 July 202610 July 2026
2VfnxxwjcVp18 June 20268 June 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 20 most recent posts we hold, published 9 May 2026 to 4 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

4 Aug 2026, 11:14 UTC≈5,390 views199 reactions1 Starread 13 August 2026

Я попробовал uv, обплевался и вернулся на poetry Если вы последние полгода не читали чат, то вы не знаете, как сильно у меня горело после перехода на uv. Сейчас расскажу! Данный пост специально написан, чтобы и у вас тоже сгорело. Если к концу вы подойдете без боли в ... душе, то все было зря. Как все было? Обычно, я первый прыгаю пробовать все новые и модные штуки. Так было с Pipenv, когда он только появился. Что

91👎34👍18🔥18😱15🤔12💩5👏3

3 Aug 2026, 05:17 UTC≈5,300 views133 reactions1 Starread 13 August 2026

Итог стрима Что получилось? - Провести 3 часа в хорошей компании ✅ - Еще до стрима Claude нашел два бага в тестах: один серьезный, один более мелкий (пока мы тестировали сетап для трансляции) - На стриме был сделан 1 PR с фиксом серьезного бага: https://github.com/wemake-services/django-modern-rest/pull/1196 PR смерджен! - Сам фикс сначала был полностью навайбкожен, он вроде бы и правил баг, но с точки зрения меинт

80👍36🔥10🤔3🙏3👎1

1 Aug 2026, 09:02 UTC≈6,130 views143 reactions1 Starread 13 August 2026

Вайбкодим security компоненты в django-modern-rest (или нет) https://www.youtube.com/watch?v=laJQcNAqxc0 В django-modern-rest появилась большая задача: полностью мигрировать в себя dj-rest-auth. Ссылочка (мы ищем контрибьюторов, особенно специалистов в безопасности OAuth / MFA / Passkeys!): https://github.com/wemake-services/django-modern-rest/issues/1193 На что @fastnewsdev (как главный пропагандист ИИИ = "инжене

🔥105😁188👍7😱3💩2

31 Jul 2026, 07:48 UTC≈10,500 views243 reactions2 Starsread 13 August 2026

id() в питоне не выдает уникальные значения Наверняка, многие из вас, когда изучали питон читали, что id(obj) дает уникальный идентификатор объекта. Его даже назвали, блин, id 🌚️️ Но, все не совсем так. Сегодня будем срывать покровы с одной из самых простых и сложных механик в питоне. Что вообще такое id? Сначала, давайте посмотрим на то, как id() устроен: static PyObject * builtin_id_impl(PyModuleDef *self, Py

👍168🔥3322🤯9😁4👌3🤡2💩1

13 Jul 2026, 09:04 UTC≈8,630 views142 reactions3 Starsread 13 August 2026

Внутри питона есть ЕЩЕ виртуальные машины Мы все знаем, что сам питон - одна большая стековая виртуальная машина, которая выполняет опкоды. Их мы можем посмотреть через dis: >>> import dis >>> dis.dis('x + y') 0 RESUME 0 1 LOAD_NAME 0 (x) LOAD_NAME 1 (y) BINARY_OP 0 (+) RETURN_VALUE М

👍89🔥3216🤯3😢2

10 Jul 2026, 09:15 UTC≈8,040 views99 reactions2 Starsread 13 August 2026
Advertisementerid 2VfnxvSxct3

Подкаст про управление разработкой в новой реальности ВК | ТГ Меня пригласили поучаствовать в подкасте, чтобы обсудить разработку с ИИ и управление разработкой с ИИ. Участники: - Кирилл Меньшов, старший вице-президент и руководитель блока «Технологии» Сбера - Дмитрий Иванов, руководитель SourceCraft в Яндексе - Я, опенсорс разработчик Поговорили про важные вопросы: - Сможем ли программировать на русском? Или его

👍5816🤡12🔥5👏3💩2😁2👌1

6 Jul 2026, 11:50 UTC≈9,580 views206 reactionsread 13 August 2026

Наконец-то полезные фичи в питоне Многие знают, что я почти не добавляю новые фичи в CPython, я стараюсь выпилить существующие и править баге в тех, что у меня не получается убирать. Новые если и добавляю, то без масштабных обсуждений. Некоторые новые фичи встречают у меня сильный оптимизм: как новый встроенный sampling profiler. Вот тут видео про него кстати с прошедшего PyCon. Некоторые фичи встречают у меня пони

🔥145🤔2318👍10💩8👏1😁1

29 Jun 2026, 09:08 UTC≈9,540 views52 reactionsread 13 August 2026

Пользуясь случаем: у нас 10 июля митап в Нижнем Новгороде. https://pytho-nn.timepad.ru/event/4050146/ В программе 4 крутейших юбилейных доклада от гостей города и (даже!) нижегородца: - Артем Пашков, Нижний Новгород, Сообщество "Опенсорсеры", Как сообщество Опенсорсеры помогает open source проектам и разработчикам? Отвечу на главный вопрос: нужно ли лично вам занимать опенсорсом? И как начать? Расскажу про пробле

🔥3410👍8

29 Jun 2026, 08:51 UTC≈14,800 views143 reactionsread 13 August 2026

Если вы понимаете данный баг, то вы знаете питон лучше 95% людей А если нет, то вы многое узнаете про то, как работает память и почему мутабельностью стоит пользоваться с осторожностью. Недавно я увидел один из лучших багов в CPython за долгое время. А я видел много багов 🌚️️ Вот код, который делает две критичные безумные вещи (попробуйте их найти прежде, чем читать дальше): class Evil: def __eq__(self, other

👍62🔥51🤯1810👎1🤡1

25 Jun 2026, 13:14 UTC≈10,100 views244 reactions1 Starread 13 August 2026

Генерируем Rust код из Python и становимся крабами Проект "острый краб": https://github.com/kushaldas/spicycrab Вы же знаете, что вы узнаете про все важные штуки в питоне первыми? На ближайшем Language Summit в июле Кушал Дас - core-разработчик CPython - представит свой новый проект. Но зачем ждать июля, когда код открыт? Давайте смотреть и пробовать! В чем главная идея? - Пишем на типизированном Python - Получае

🕊165🔥35🤯15👍116🤔4😁4💩3

16 Jun 2026, 14:14 UTC≈8,860 views166 reactions2 Starsread 13 August 2026

Почему msgspec такой быстрый? Несколько дней назад я решил разобраться в устройстве msgspec. Получилось како бычно: я напал на него со своими PRами, мне через день выдали права на merge и release. Но самое главное: теперь я могу рассказать вам про внутреннее устройство самого быстрого сериализатора для json в питоне. Как быстро распарсить json? Традиционные парсеры json делают так: - Парсим весь json документ - Ис

87👍59🔥18🤡1😱1

8 Jun 2026, 15:41 UTC≈12,500 views261 reactions1 Starread 13 August 2026
Advertisementerid 2VfnxxwjcVp

Зеркало PyPI На нескольких проектах последние несколько дней сталкиваемся с проблемами с доступом к PyPI: как локально, так и в CI. Печально. All attempts to connect to pypi.org failed. Probable Causes: - the server is not responding to requests at the moment - the hostname cannot be resolved by your DNS - your network is not connected to the internet Если у вас есть такая же проблема, можете воспользоваться Py

👍79🤡70👎4720🤮19🔥16😁4👏3

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

Citation-graph rank

Citation-graph rank — 12,383 of 1,189,255entries 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

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

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

“Находки в опенсорсе” (@opensource_findings), 11,638 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/opensource_findings.

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.