Telegram RegisterThe public register of Telegram
Telegram profile photo for brain_leakage_etc

Channel

brain_leakage_etc

@brain_leakage_etc

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

130subscribers

+2 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-1001735095259
TypeChannel
Username@brain_leakage_etc
DescriptionНе мысли, но мыслишки некоего @astynax. Можно сказать то, что не получилось дописать до средней длины публикаций в @brain_dump_etc
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held3
On Telegramt.me/brain_leakage_etc

Growth

1281301297 Aug 2026, 17:11 — 128 subscribers8 Aug 2026, 14:53 — 130 subscribers9 Aug 2026, 01:16 — 130 subscribers7 Aug 2026, 17:119 Aug 2026, 01:16
3 measurements spanning 1 day, net +2. 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 128–130 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 01:16130no change
8 Aug 2026, 14:53130+2
7 Aug 2026, 17:11128first reading

Engagement

17 posts held, back to 10 February 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
186.7%
avg views ÷ 130 subscribers
Avg views / post
243
7 posts measured
Reaction rate
1.41%
reactions ÷ views · ER floor
Posts in window
7
of 17 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 7 August 2026
Posts held17 (10 February 20267 August 2026)
Views total1,699
Reactions total24
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 01: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.

What this channel posts

Photos
24
Videos
2
Links
35

Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

58 reactions across 13 posts, in 6 distinct kinds. The most used accounts for 39.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2339.7%
1627.6%
😱1119.0%
🤯46.90%
👍23.45%
🤔23.45%

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

Measured over the 17 most recent posts we hold, published 10 February 2026 to 7 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

7 Aug 2026, 13:20 UTC233 views2 reactionsread 9 August 2026

Копаюсь дальше в профиле Safari 🔬 В процессе написал программку, которая дампает plist в JSON, потому что кое-что у Safari в plists хранится — у Apple ещё со времён Next любовь к property lists. Благо, для Rust есть готовая либа, которая умеет читать и XML-вариант и бинарный. Так что я просто сделал plist->raw_dict->JSON, а дальше с jq развлекался. Ну да это всё цветочки. Теперь по ягодкам. У Safari в History.db ес

🤔2

7 Aug 2026, 08:25 UTC801 views5 reactionsread 9 August 2026

Снова порадовался тому, что Safari хранит историю в SQLite, хоть и добраться до файла не так уж и просто из-за огораживания macOS. У меня отключена очистка истории в настройках браузера, уж и не помню с каких пор. И когда я перключаю настройку в "забывать всё, спустя год", Safari говорит, мол, ты точно хочешь удалить 100000 записей? При этом сам Safari колдобится от такого объёма истории, но продолжает терпеть, раз

🔥4👍1

31 Jul 2026, 11:03 UTC146 views3 reactionsread 9 August 2026

Вообще всё это мне вернуло слегка те ощущения из времени, когда я писал для себя всякие GUI-надстройки для Windows на Delphi. Правда, такого уровня удобства "от мысли, до первого запуска" так никто и не достиг с тех пор, только усложнили всё. Я уж молчу про возможность в оффлайне всё делать, имея и всю документацию на руках с ворохом примеров на все случаи жизни. Нейросетки позволяют превозмочь ступор чистого листа

3

31 Jul 2026, 10:57 UTC126 views1 reactionsread 9 August 2026

И, да, чтобы получиться список окон на текущем мониторе на активном Space, надо потыкать постоянной отгнивающий приватный API, а публичного и стабильного просто нет. При этом Acessibility API простойные, но им тоже как-то наплевать на "текущий десктоп того монитора, на котором сейчас фокус", официально есть только способ перечислить окна, видимые и не только, но ника не поэкраново. В итоге все открытые и не очень реш

👍1

31 Jul 2026, 10:50 UTC119 views4 reactionsread 9 August 2026

Вчера не смог удержаться, решил написать свою переключалку окон для macOS. Потому что иcкоробочный вариант переключает окошки, лежащие на всех десктопах, мне это неудобно. Да, есть какие-то аналоги, которые в той или иной степени платные или навязчиво просят денег даже в бесплатном режиме. И все какие-то толстые. А мне не хватает dmenu/rofi. Решил в итоге свою версию сделать. Конечно же решил вайбкодить, поэтому ско

🔥4

29 Jul 2026, 12:50 UTC109 views7 reactionsread 9 August 2026
Photo

Жёлтые тюльпа-аны Это не для зву-ука! Красные тюльпа-аны Вам не композит!

🔥4🤯2😱1

21 Jul 2026, 08:29 UTC165 views2 reactionsread 9 August 2026

Активно начал умирать второй динамик в макбуке. Прожил на полгода дольше собрата. Точнее, не динамик, а усилитель. Скоро мой ноут будет немым, разве что порт наушниковый звучать продолжит и BT ещё

😱2

1 Jul 2026, 11:52 UTC249 views4 reactionsread 9 August 2026

А ещё можно через TRAMP запускать фрагменты кода из вашего локального Org файла на удалённых машинах и спутывать (tangle) ваши конфиги тоже в удалённые файлы. При этом можно на одной машине выполнить скрипт, результат которого подставить в конфиг, заливаемый на другую машину — простор для вариаций широчайший! Собственно, Literate Ops вокруг этого всего и построен 😎

🔥4

1 Jul 2026, 10:32 UTC229 views11 reactionsread 9 August 2026

Вчера собрал в докере python, uv, LSP сервер (pyrefly, через uv tool install). Запустил контейнер. В Emacs зашёл по пути /docker:urly-swan/app/foo.py и открылся файл в контейнере, как будто локальный. Вызвал eglot— тот запустил и подконнектился к LSP-серверу в контейнере. Сервер увидел сорцы, зависимости и остальное. Потом я вызвал eshell при активном буфере с файлом в контейнере — и shell открылся тоже внутри ко

🔥65

13 Jun 2026, 05:40 UTC238 viewsread 9 August 2026

https://unix.foo/posts/it-will-never-be-the-year-of-the-linux-desktop/ The problem is that Linux can make almost anything exist, but it cannot make almost everyone agree to care about it at the same time. Увы и ах, всё так и есть...

4 Jun 2026, 08:38 UTC282 views2 reactionsread 9 August 2026

>>> from pydantic import BaseModel, BeforeValidator >>> from typing import Annotated >>> type CommaSeparated[T] = Annotated[list[T], BeforeValidator(lambda v: v.split(","))] >>> class Buckets(BaseModel): ... REQUEST_DURATION_BUCKETS: CommaSeparated[float] | None = None ... >>> import os >>> Buckets.model_validate(os.environ) Buckets(REQUEST_DURATION_BUCKETS=None) >>> >>> os.environ["REQUEST_DURATION_BUCKETS"] = "

1🔥1

14 May 2026, 09:06 UTC367 views0 reactionsread 9 August 2026

Первый раз наткнулся на то, что объявление в классе метода def list(self, ..) ломает тайпчекинг и код просто падает на вычислении аннотаций. Потому что в области видимости класса теперь list — это дескриптор метода экземпляра. То есть произошло затенение (shadowing), которое почти никак не видно в самом коде, потому что вызывается-то метод через точку! А вот аннотации ломаются, потому что они-то в пространстве имён

Showing the 12 most recent of 17 posts we hold for @brain_leakage_etc. 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 — 764,024 of 1,480,944entries 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.

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

“brain_leakage_etc” (@brain_leakage_etc), 130 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/brain_leakage_etc.

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.