...ofc taking 4xgb10 REAPs is boring so let's debug a custom quant and a custom REAP
🔥1

Channel
@notatky
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
148subscribers
+2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001126245397 |
|---|---|
| Type | Channel |
| Username | @notatky |
| Created | 7 May 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 8 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/notatky |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 05:06 | 148 | +1 |
| 24 Aug 2026, 17:25 | 147 | +1 |
| 8 Aug 2026, 21:00 | 146 | no change |
| 7 Aug 2026, 19:09 | 146 | first reading |
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 8 August 2026. An engagement rate over an empty window would be a number about nothing.
43 reactions across 16 posts, in 14 distinct kinds. The most used accounts for 23.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 10 | 23.3% | |
| 😁 | 6 | 14.0% | |
| 👍 | 5 | 11.6% | |
| ❤ | 3 | 6.98% | |
| 👀 | 3 | 6.98% | |
| 🥰 | 3 | 6.98% | |
| 🦄 | 3 | 6.98% | |
| 🏆 | 2 | 4.65% | |
| 💯 | 2 | 4.65% | |
| 🫡 | 2 | 4.65% | |
| 👌 | 1 | 2.33% | |
| 👏 | 1 | 2.33% | |
| 🙏 | 1 | 2.33% | |
| 🤯 | 1 | 2.33% |
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 17 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 43 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 8 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.
...ofc taking 4xgb10 REAPs is boring so let's debug a custom quant and a custom REAP
🔥1
We're talking about self-improving AIs replacing SaaS, meantime I had recently talked to people who introduce SaaS to businesses still running on pen, paper, copiers and faxes. They don't feel in danger at all. Like, that market is /big/ Think outside the box^W bubble, lol
👍1
sorry not sorry
🦄2
meantime we've downloaded a-little-bit-quantized Kimi K3 checkpoint and now trying to fit it into that setup. Which is quite a quest. 900 GiB of weights, 8x128 GiB of RAM and 8x the OS/driver overhead, plus various CUDA buffers... funny side quest is it doesn't fit on any single 1TB SSD either :)
❤1🔥1
https://x.com/oleksandr_now/status/2084961336627253497?s=46
🔥1🤯1
i used to say "im good at finding nonstandard solutions but def not the daily ops guy" now I have a great example—was bored waiting for the rest of the cables to arrive, assembled the cluster with what i have—and now farming the XP off every trap on the map because the interconnect topology is VERY nonstandard ahahah. • Routed RoCE through G works—but large NCCL collectives are currently pathological. - Disabled …
🏆2
dear chat, do you know smth akin to the GRC Analyst Master Class but free? asking for a friend
Anthropic: safety safety safety! nobody except us can be trusted to use AI safely! Also Anthropic: we run untested SOTA models without monitoring. I mean, without classifiers-sure, but without monitoring? This is a public statement "our values are fake we want to control _users_"
👍2💯1
> oleksandr_now seems the natural guinea pig --Fable im flattered ahahah
😁2🦄1
80x RTX 5090s, omg. Anyone willing to sponsor 8x GB10s? The other 8 are on me, and 16 DGX Spark/Ascend GX10s should fit Kimi K3 too https://x.com/totheagi/status/2081855316443205717?s=20
(after reading the Liang Wenfeng investor meeting transcript) look ma, no 996; it's not even "google 20%" but 50% of free time and bottom-up research&exploration initiatives i def admire and look up to ppl who are able to calmly lead this way [including keeping the position that helps them to]
❤1👍1
just loaded Codex for "/goal implement <feature> without increasing LOC. all existing tests must pass unchanged" let's see how that goes 😉 upd: well, after two hours it carved out like 200 LOC but become completely overwhelmed and blocked from adding new code, like collapsed to complete word salad: > Reply yes to approve: openActor(maxStreams) with actor ID = self-stream public key-author filtered-durable state, …
🔥2🫡2👍1
Showing the 12 most recent of 20 posts we hold for @notatky. 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.
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.
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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“χаотичні нотатки” (@notatky), 148 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/notatky.
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.