Model Context Protocol 我看好 MCP 的发展前景,也看到了很多相关的文章,不过似乎不完全,所以我也写了。 https://t.me/iv?url=https://jimmy0w0.me/posts/model-context-protocol-zh-Hans/&rhash=194f9809bec0b3
Signed Jimmy 的代理人

Channel
@jimmy0w0
On this record: Growth · Engagement · Posts · Cite this entry
6subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002036652900 |
|---|---|
| Type | Channel |
| Username | @jimmy0w0 |
| Created | Between 1 November 2023 and 27 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 18 September 2026 |
| On Telegram | t.me/jimmy0w0 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 08:38 | 6 | -1 |
| 12 Aug 2026, 18:03 | 7 | no change |
| 7 Aug 2026, 21:30 | 7 | first reading |
18 posts held, back to 27 May 2024 — 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 18 posts for this entry, the most recent from 23 July 2025. An engagement rate over an empty window would be a number about nothing.
Model Context Protocol 我看好 MCP 的发展前景,也看到了很多相关的文章,不过似乎不完全,所以我也写了。 https://t.me/iv?url=https://jimmy0w0.me/posts/model-context-protocol-zh-Hans/&rhash=194f9809bec0b3
Signed Jimmy 的代理人
Google Authenticator: A Deep Dive into Exported Data Processing Data from a QR Code Exported by Google Authenticator. https://t.me/iv?url=https://jimmy0w0.me/posts/google-authenticator-qr-code-data-en/&rhash=194f9809bec0b3
Signed Jimmy 的代理人
处理 Google Authenticator 导出的 QR Code Google Authenticator 导出 QR Code 后的处理 https://t.me/iv?url=https://jimmy0w0.me/posts/google-authenticator-qr-code-data-zh-Hans/&rhash=194f9809bec0b3
Signed Jimmy 的代理人
Live stream finished (5 seconds)
Live stream started
Google Authenticator: A Deep Dive into Exported Data Processing Data from a QR Code Exported by Google Authenticator. https://t.me/iv?url=https://jimmy0w0.me/posts/google-authenticator-qr-code-data-en/&rhash=194f9809bec0b3
Signed Jimmy 的代理人
浅谈 Google Authenticator 的数据导出 QR Code Google Authenticator 导出 QR Code 后的处理 https://t.me/iv?url=https://jimmy0w0.me/posts/google-authenticator-qr-code-data-zh-Hans/&rhash=194f9809bec0b3
Signed Jimmy 的代理人
這不就來了嗎? 「我也是搞研發的 這裡面的東西懂」
Signed 🐱
少了一張 前情提要
Signed 🐱
哎哟睡不着了,想吃阿普唑仑
Signed 🐱
Sticker, posted without a caption
Signed 🐱
啊我就叛逆了,我过几个月直接把备案注销了
Signed 🐱
Showing the 12 most recent of 18 posts we hold for @jimmy0w0. 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.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“猫也会说话” (@jimmy0w0), 6 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/jimmy0w0.
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.