Channel
@prompt
On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
12,754subscribers
+102 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001572217002 |
|---|---|
| Type | Channel |
| Username | @prompt |
| Created | Between 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/prompt |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 19:04 | 12,754 | +5 |
| 11 Aug 2026, 18:04 | 12,749 | +16 |
| 10 Aug 2026, 17:41 | 12,733 | +18 |
| 9 Aug 2026, 17:51 | 12,715 | +12 |
| 8 Aug 2026, 18:45 | 12,703 | +11 |
| 7 Aug 2026, 21:36 | 12,692 | +23 |
| 7 Aug 2026, 00:34 | 12,669 | +15 |
| 6 Aug 2026, 02:50 | 12,654 | +2 |
| 6 Aug 2026, 02:32 | 12,652 | no change |
| 6 Aug 2026, 00:55 | 12,652 | first reading |
25 posts held, back to 12 June 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 16 pagesof Telegram’s post history, 20 posts per page.
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. It is computed over the 16 of 18 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 25 (12 June 2026 – 11 August 2026) |
| Views total | 96,867 |
| Reactions total | 67 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 12:15 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.
167 reactions across 22 posts, in 10 distinct kinds. The most used accounts for 61.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 103 | 61.7% | |
| 🤣 | 32 | 19.2% | |
| 👍 | 14 | 8.38% | |
| 🔥 | 5 | 2.99% | |
| 😱 | 3 | 1.80% | |
| 🤡 | 3 | 1.80% | |
| 👏 | 2 | 1.20% | |
| 🤔 | 2 | 1.20% | |
| 🥰 | 2 | 1.20% | |
| 😁 | 1 | 0.599% |
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 23 of the 25 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 170reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 25 most recent posts we hold, published 12 June 2026 to 11 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.
🤖 Someone built an LLM to translate Claude into English Claude's writing got so verbose that a dev made a Claude Code plugin that pipes its output through a local Gemma model to rewrite it in plain language. Two AIs. One just to decode the other. We're cooked. Source
❤2
🤖 1M hours of human video just bridged the embodiment gap Dyna-2 hit 87% zero-shot pass rate across unseen robots. Its VLA predecessor managed 46%. The edge: predicting future video frames, not just actions. More human data, better robot. Monotonically. Across four orders of magnitude. Scaling laws are no longer just an LLM thing.
🤖 Meta's back. New open-weight 30B dense model built for always-on local agents. Muse Glimmer, 30B dense, 256K context. Runs locally, targets persistent agent workflows. GGUF on day one. Meta going toe-to-toe with Qwen and DeepSeek in the OSS weight race. Quietly.
🔥4
🚨🔥 WordPress just patched a pre-auth XSS-to-RCE bug hiding in plain sight since v1 No login needed. One bad username field. Full shell on the server. CVE-2026-64638 hit every default WordPress install, 43%+ of the web. Emergency patch is out: update to 7.0.3 now. Source
👍4
🤖 Demis Hassabis is out as DeepMind CEO He's now chair + Alphabet's chief scientist. Koray Kavukcuoglu (former CTO) takes over the day-to-day. Jeff Dean also out after 27 years. Read: Google is pulling its AlphaFold guy back into pure research and handing the keys to someone who'll actually ship. Brutal timing with OpenAI and Anthropic sprinting.
🤖 More Qwen 3.8 sizes are coming, including a rumored 122B Alibaba's flipping the script. After signals it'd keep larger models closed, Qwen is now open-sourcing across the entire 3.8 lineup. Turns out Xi Jinping told Chinese AI labs to open source. And they did.
❤3
⚡️ Elon wants AI to skip source code and spit out raw binary He posted that the next step is AI generating optimized machine code directly, no source code at all. Compilers exist precisely because writing binary is wasteful and unverifiable. Every token spent on raw machine code is a token not spent on logic. Technically unfounded. But it's a great tweet.
❤7
🤖 Claude wrote a walkable jungle from scratch. No assets. Just code. 12,000 lines of procedurally generated terrain, foliage, and lighting. Pure runtime math, no textures imported. This is basically a demoscene demo written by an AI on request.
❤4
🤖 Qwen 3.8-27B is here, and open weights are coming for the Max too Alibaba just dropped Qwen 3.8-27B alongside Qwen 3.8-Max, their most capable model yet. And they're open-sourcing the Max weights next week. If 3.6 27B was already the local king, this thing's about to take the crown.
❤1
⚡️ DeepSeek V4-Flash drops, no countdown, same-day weights Outperforms V4-Pro preview and trades blows with GPT-5.5 on agentic evals. MIT license. Runs on two RTX 3060s or a 192GB unified memory box at full quality. GLM-5.2-level performance on hardware mortals actually own.
👍3❤1
⚡️ Chinese labs are shipping faster than anyone can benchmark. MiniMax, DeepSeek, Qwen, Moonshot. New drop every 48 hours and half the game is just keeping up. GPU constraints forced efficiency. Efficiency ships models. That's it.
❤9😁1
🤖 Claude Mythos cracked encryption. Weakened, but still. Anthropic's Claude Mythos Preview found novel attacks on a weakened AES variant and a post-quantum candidate (HAWK). One attack was 200 to 1,000x faster than any human-developed method. Current banking and comms are fine. But this is exactly how you benchmark what's coming next.
❤3👍2🤔2👏1🔥1
Showing the 12 most recent of 25 posts we hold for @prompt. 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 — 5,688 of 1,151,006entries 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.
Named by 48 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“prompt 🤖 AI News” (@prompt), 12,754 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/prompt.
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.