Dave Kleiman SHA-256_.mp4
Signed Ramon Quesada. † 🙏

Channel
@DaveKleiman
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
19subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001306045264 |
|---|---|
| Type | Channel |
| Username | @DaveKleiman |
| Description | Dave Kleiman - testigo wp 26 april 2013 https://t.me/DaveKleiman Dave & Craig Tulip Trading Trust. https://t.me/KleimanVsCSW http://www.davekleiman.com/ https://marc.info/?w=2&r=1&s=Dave+Kleiman&q=a https://ramonquesada.com |
| Created | Between 1 March 2018 and 31 July 2021— 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/DaveKleiman |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 17:01 | 19 | no change |
| 6 Aug 2026, 21:07 | 19 | first reading |
20 posts held, back to 9 April 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 20 posts for this entry, the most recent from 15 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 2 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.
Dave Kleiman SHA-256_.mp4
Signed Ramon Quesada. † 🙏
Dave Kleiman SHA-256 2 fuentes 15 jun 2026 (Audio 20 min) El documento técnico RFC 4880 establece el estándar oficial para el formato de mensajes de OpenPGP, detallando los protocolos de criptografía, firmas digitales y gestión de claves. Esta normativa técnica define cómo se estructuran los paquetes de datos para garantizar la confidencialidad y la integridad de la información en entornos digitales. Entre sus auto…
Signed Ramon Quesada. † 🙏
Dave Kleiman SHA-256 2 fuentes 15 jun 2026 (Audio 20 min) El documento técnico RFC 4880 establece el estándar oficial para el formato de mensajes de OpenPGP, detallando los protocolos de criptografía, firmas digitales y gestión de claves. Esta normativa técnica define cómo se estructuran los paquetes de datos para garantizar la confidencialidad y la integridad de la información en entornos digitales. Entre sus autor…
Signed Ramon Quesada. † 🙏
Dave emailed me the Peter Thiel, Facebook investor "bubble" video on Dec. 23, 2007. Dave Kleiman signed it using SHA-256, Bitcoin's core hash function, 38 days after Hal Finney co-authored the standard that adopted it. rfc-editor.org/info/rfc4880 https://x.com/i/status/2066156887347798133
Signed Ramon Quesada. † 🙏
Con o sin éxito, un amigo me acaba de enviar esto por correo electrónico: Asunto: Re: Una parábola moderna Una empresa japonesa (Toyota) y una estadounidense (General Motors) decidieron organizar una carrera de canoas en el río Misuri. Ambos equipos entrenaron intensamente para alcanzar su máximo rendimiento antes de la carrera. El día de la competición, los japoneses ganaron por una amplia ventaja. Los estadouni…
Signed Ramon Quesada. † 🙏
w or not, a friend just e-mailed it to me: Subject: Fw: A Modern Parable A Japanese company (Toyota ) and an American company (General Motors) decided to have a canoe race on the Missouri River. Both teams practiced long and hard to reach their peak performance before the race. On the big day, the Japanese won by a mile. The Americans, very discouraged and depressed, decided to investigate the reason for the cru…
Signed Ramon Quesada. † 🙏
A Modern Parable | WindowsBBS https://www.windowsbbs.com/threads/a-modern-parable.62431/
Signed Ramon Quesada. † 🙏
Photo, posted without a caption
Signed Ramon Quesada. † 🙏
https://x.com/i/status/1957451852104028381
Signed Ramon Quesada. † 🙏
Satoshi Nakamoto Unmasked: The Byzantine General Full Documentary https://youtube.com/watch?v=IophSL7U01U&is=Y-isWaFPaigfvB4q
Signed Ramon Quesada. † 🙏
Photo, posted without a caption
Signed Ramon Quesada. † 🙏
https://x.com/i/status/2049827417100062846
Signed Ramon Quesada. † 🙏
Showing the 12 most recent of 20 posts we hold for @DaveKleiman. 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 — 1,008,130 of 1,340,412entries 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 5 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.
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.
@DaveKleiman 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.
References a handle that is not a live channel — we have no record it ever was one.
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.
“401 Dave Kleiman 2013” (@DaveKleiman), 19 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/DaveKleiman.
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.