причем я сам попросил - лень идти за totp
👏4🤡3🐳2🔥1😁1

Channel
@itpgchannel
On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
3,714subscribers
+115 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001567842955 |
|---|---|
| Type | Channel |
| Username | @itpgchannel |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/itpgchannel |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 00:39 | 3,714 | +29 |
| 1 Sept 2026, 13:25 | 3,685 | +5 |
| 29 Aug 2026, 14:16 | 3,680 | +24 |
| 26 Aug 2026, 10:23 | 3,656 | +18 |
| 23 Aug 2026, 09:13 | 3,638 | +7 |
| 19 Aug 2026, 16:46 | 3,631 | +13 |
| 16 Aug 2026, 19:46 | 3,618 | +12 |
| 12 Aug 2026, 22:15 | 3,606 | +5 |
| 9 Aug 2026, 21:52 | 3,601 | +3 |
| 6 Aug 2026, 23:26 | 3,598 | -1 |
| 6 Aug 2026, 08:21 | 3,599 | first reading |
27 posts held, back to 30 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 3 pages 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 27 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
1,374 reactions across 23 posts, in 27 distinct kinds. The most used accounts for 28.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 391 | 28.5% | |
| 🔥 | 370 | 26.9% | |
| 🤡 | 135 | 9.83% | |
| ❤ | 131 | 9.53% | |
| 👍 | 102 | 7.42% | |
| 💩 | 77 | 5.60% | |
| 🐳 | 39 | 2.84% | |
| 🤣 | 37 | 2.69% | |
| 💯 | 18 | 1.31% | |
| 🎉 | 16 | 1.16% | |
| 👏 | 14 | 1.02% | |
| 💊 | 10 | 0.728% | |
| 🆒 | 5 | 0.364% | |
| 🤩 | 5 | 0.364% | |
| 😇 | 4 | 0.291% | |
| 👎 | 3 | 0.218% | |
| 😱 | 3 | 0.218% | |
| 🤔 | 3 | 0.218% | |
| 👾 | 2 | 0.146% | |
| 😐 | 2 | 0.146% | |
| 7 further kinds | 7 | 0.509% |
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 27 of the 27 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 1,636 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 27 most recent posts we hold, published 30 July 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.
причем я сам попросил - лень идти за totp
👏4🤡3🐳2🔥1😁1
О, и антропики до этого догадались!
🔥24🤡1
#perf - это состояние души. Например, когда github actions тебе дает 20 джобов по 4 ядра на Linux, и 5 джобов по 3 ядра на macos, то ты делаешь так, чтобы эта халява никогда не простаивала! Хорошо иметь свою систему сборки https://t.me/itpgchannel/4282, в условном meson/cmake хрен бы так легко попилил свой CI.
💯10🔥7🤡7👾2❤1
https://github.com/pg83/shitty/releases TL;DR - новый релиз #shitty: * sixels * табы preview, пока без UI вкладок, только возможность создавать и переключаться между ними с клавиатуры
❤8🔥5😱3👍2🤡1🤣1
#trustme Получилось порядка 17к тестов (на КДПВ 10к нод, иногда нода больше одного теста). На старте trustme (бывший #mrustc) проходил только 2/3 из них, сейчас, после суток пыхтения, и фикса порядка 150 (!!!) багов, проходит уже 3/4. И это я еще не прогнал его с санитайзерами на полном корпусе тестов. В целом, не умаляя заслуг его автора (а он проделал титанический труд), это довольно много говорит о качестве кода…
❤15🔥8👍2🤡1
Чтобы запустить autoresearch для #trustme, нужен очень плотный корпус тестов, с целевой метрикой "сократи количество fail". В https://t.me/itpgchannel/4296 писал, как я "ограбил опенсорс", чтобы соорудить свой монструозный корпус тестов для #shitty. Прямо сейчас снова граблю опенсорс, на этот раз тащу к себе самые разнообразные тесты на компилятор rust! https://github.com/pg83/trustme/blob/master/PLAN.md - вот пла…
🔥23😁17👍8🤡5❤2👀1
https://www.opennet.ru/opennews/art.shtml?num=66036 TL;DR - Rust запретили AI в разработке. Запретили и запретили, долбоебы и долбоебы, кто бы сомневался. Но у меня под это дело как раз есть анонс нового проекта! Думаю, вы заметили, что мне нравятся всякие autoresearch #LLM штуки, типа моего #shitty, это когда я краду 5000 тестов на терминал в opensource, а потом говорю клоде "повтори"! https://t.me/itpgchannel/42…
🤡29🔥25😁15❤7👍4🐳3✍1🆒1
А вот и шелл для #shitty подоспел!
😁40🔥11🤩4❤2💯1
Четверг, а значит время проектов от подписчиков! 🌝 Тем, кто пропустил, что такое четверговые проекты от подписчиков, можно прочитать тут - https://t.me/tech_b0lt_Genona/4983 Слово автору @sowound --- Зачастую у софта практически нет никакого UX. Если в скрипте ошибка, то желаю тебе удачи в попытках понять, откуда она вообще взялась. Для Windows буквально нет ни одной bash-совместимой оболочки, а powershell — это …
😁27💩10👍7🤔3❤1
Выпустил новый релиз #shitty - https://github.com/pg83/shitty/releases! Всякие мелочи: * лигатуры и поддержка всратых Nerd иконок * toml config * произвольные переопределения кейбиндов * 1200 цветовых тем, цельнотянутых из iterm, #kitty, #alacritty, и везде, где нашел * фиксы и оптимизации Но самое важное в этом релизе, что я таки пошел на поводу у тех, кому не нравится название #shitty! Теперь в репозитории живу…
😁55❤19🤡9🔥8👍7💩6🐳3💯3
Число сообщений о серьезных киберуязвимостях продолжает расти. В июле 21 крупная технологическая организация опубликовала около 2500 CVE высокой и критической степени серьезности — примерно в 5 раз больше, чем ежемесячный рекорд до анонса Claude Mythos Preview. Источник
🤡12👍8🔥4❤2🤩1
Публикация на opennet порадовала меня уж лишь тем, как там корежило копилефтоблядей #GNU, любо-дорого!
😁31🤡19❤6💊5🔥3👍2😐2🐳1
Showing the 12 most recent of 27 posts we hold for @itpgchannel. 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.
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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“commit -m "better"” (@itpgchannel), 3,714 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/itpgchannel.
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.