Natural conversation includes interruptions and talking over people, which is hard for an LLM to model as a single autoregressive sequence. I’m sure you can get pretty far by creating a text sequence with movie-script like breaks mid sentence, but it seems like the real solution would involve parallel streams of listening and thinking with talking queued up for pauses or rising to an interruption priority. Intermixin…

Channel
John Carmack
@ID_AA_Carmack
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
9subscribers
+2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002887869400 |
|---|---|
| Type | Channel |
| Username | @ID_AA_Carmack |
| Created | 12 August 2025 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/ID_AA_Carmack |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 15:16 | 9 | +2 |
| 12 Aug 2026, 16:32 | 7 | no change |
| 6 Aug 2026, 08:22 | 7 | first reading |
Engagement
13 posts held, back to 12 August 2025 — 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 13 posts for this entry, the most recent from 12 August 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 56s
- Average length
- 56s
Measured directly from 1 video 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.
Recent posts
Does @TheFIREorg have a position on cases like Collective Shout pressuring payment processors to pressure aggregators like Steam to remove content? Not a regulatory question, but still in the wheelhouse of expression suppression.
Trista turned the formal dining room into a library for me at our new house, and I love it! We still have separate shelving for paperbacks, magazines, and graphic novels, and a few more bookshelves in my Fortress of Solitude, but this is the most books I have ever had shelved in one place. I have never thrown a book away in my life, but I know there are many books that have somehow been lost in moves over the years…
I can’t pass a bookstore without picking something up, but mainstream book publishing is dominated by what I consider “female authorial voice” (sometimes even from the remaining male authors), and my tastes are a little out of step with it. Robert E. Howard’s pulp fiction of a century ago is quite a palate cleanser. Everyone knows Conan, and I have read some Solomon Kane, but I was completely unfamiliar with his we…
https://t.co/usxPJRZXNP
While noting some compression artifacts in a water scene on TV, I started thinking— for a given set of compression parameters, what is “the most cursed macroblock”. Not the worst looking, which is a squishy perceptual metric, but the set of pixels that takes the most bits to encode. With all the non-linearity in pixel quantization and entropy encoding, finding that is actually non-trivial.
I had several phrases highlighted in bold on a post that I saved to drafts, but when I returned to post it, the formatting was gone.
Are modern recommendation systems treated like a reinforcement learning problem, with a sum of discounted future rewards, or as strictly single step transactions? Many products do significant offline data analysis on actions taken to inform changes, but it seems under appreciated how much more powerful making policy changes on a live, massively parallel set of independent environments/users is. Offline RL is fundam…
I find it surprising when decisions about things like the number of runs with different random seeds wind up with “round numbers” like 10 or 50 instead of system friendly powers of two like 8 or 32. You know something about the background of a programmer by their constants!
I like em dashes, and I hate that some people now take them as evidence of text being AI generated.
https://x.com/ID_AA_Carmack/status/1935353905149341968?t=DCpR-Vh7oLv8eE-HYKDfqg&s=19 This is interesting — a compiler/runtime that makes almost all standard C/C++ code completely memory safe. The performance overhead is not negligible, but there are plenty of cases where “rewrite it in rust” still isn’t a practical solution.
I never saw an official video, so here is my little bit from the induction of Quake into the Strong Museum’s World Video Game Hall of Fame last month.
Showing the 12 most recent of 13 posts we hold for @ID_AA_Carmack. 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 — 222,530 of 1,481,217entries 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.
Mentions
Named by 6 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.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@ID_AA_Carmack named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 13 August 2026 – 13 August 2026
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“John Carmack” (@ID_AA_Carmack), 9 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/ID_AA_Carmack.
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.