Channel
@blk_st8
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
35subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002926079397 |
|---|---|
| Type | Channel |
| Username | @blk_st8 |
| Created | Between 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/blk_st8 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 00:00 | 35 | no change |
| 7 Aug 2026, 19:12 | 35 | first reading |
19 posts held, back to 1 May 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 pageof 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 19 posts for this entry, the most recent from 13 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 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.
Measured directly from 5 videos 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.
11 reactions across 8 posts, in 4 distinct kinds. The most used accounts for 36.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🥰 | 4 | 36.4% | |
| 🔥 | 3 | 27.3% | |
| ❤🔥 | 2 | 18.2% | |
| 🐳 | 2 | 18.2% |
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 8 of the 19 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 11reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 1 May 2026 to 13 June 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.
یه ایجنت تحت ترمینال بهتون معرفی میکنم به اسم oh my pi یا همون omp یکسری تصال به lsp و toolها داره و بهش دستور (!) میدید و میره با LLMکال های متفاوت،میسر راه میچینه و کار رو انجام میده. https://github.com/can1357/oh-my-pi با تشکر از @blk_st8 بابت معرفی.
🥰1
MiniMax M3 launches on NVIDIA platform with Free Endpoint MiniMax M3 is now on NVIDIA infrastructure, offering multimodal text, image, and video reasoning with 428B parameters and 1M-token context. Built for enterprise workloads, it delivers faster inference and native multimodal training. 🗞 #nvidia @testingcatalog
NVIDIA ❤️ MiniMax MiniMax M3 weights are now available on Huggingface, and NVIDIA now offers a Free Endpoint on its platform for testing. Testing time 👀
بالاخره بعد از ۸۸ فاکینگ روز ۳۳ درصد وصل شدن.
🥰2
🍿 Hermes just got 10x better... 🔗 https://www.youtube.com/watch?v=8iZUyE7SlXo @blk_st8
Photo, posted without a caption
🤖 Anthropic updates Claude Code with multi-agent management Anthropic updated Claude Code to manage multiple agents simultaneously in one window. It sorts tasks into done, in progress, and needing user input. Claude Code splits tasks automatically and no longer requires external AI managers. The new /goal command lets agents work continuously toward a set goal without repeated prompts. 📊@tech
🦭 An awesome regex visualization tool regex-vis.com https://x.com/i/status/2051429737764102258
🔥1
🤖 Anthropic is quietly turning Claude into a self-improving AI workforce The company just upgraded Claude Managed Agents with features that make AI agents feel much less like chatbots… and much more like autonomous employees. The wildest feature is called “Dreaming.” When idle, agents can now revisit past sessions, analyze mistakes, detect patterns, and reorganize memories to improve future performance, essentiall…
🏘 Nvidia wants to turn homes into AI data centers Instead of building giant server farms, startup Span is testing a strange new idea with Nvidia and homebuilder PulteGroup: installing mini AI compute hubs directly onto houses. The system, called XFRA, places a box with around 16 Blackwell GPUs outside the home. Span’s smart panel sends unused household electricity to the GPUs for AI workloads. So your house could …
دوستان این ESP32 رو دریابید خیلی چیزای باحالی میشه باهاش درست کرد و خیلی هم ارزونه؛ اگه ایده خوبی باهاش پیاده بشه توی ایران میترکونه این خارجیا یکم اوسگولن این یارو اومده یه داشبورد درست کرده باقی مونده اعتبار کلادش رو نشون میده خیلی ایده های جالب دیگه ای میشه باهاش زد، از روی همین پروژه که عکسش بالاست هم میتونید ایده بگیرید یا شخصی سازیش کنید: github.com/HermannBjorgvin/Clawdmeter @Linuxor
اگه Obsidian پرسن هستین، این کارهارو یادتون نره روش انجام بدین تا خیلی حرفهای و خفن بشه. 🔥 https://youtu.be/ZQTj8ZSDFw4?si=LwqjY31DmECXfNsC
🔥1
Showing the 12 most recent of 19 posts we hold for @blk_st8. 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.
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.
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.
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.
“blkst8” (@blk_st8), 35 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/blk_st8.
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.