MMSpace 蒙蒙空间 #虚拟机 #开源鸿蒙 #安卓 #Android #OpenHarmony #desktop #桌面 给安卓手机装上 MMSpace,就能体验 OpenHarmony/开源鸿蒙 的桌面和应用。 无需 Root,无需刷机,原来的安卓系统照常使用。 (MM是蒙蒙的简写,蒙蒙是谁,「鸿蒙」的蒙,你也可以叫它为蒙蒙空间) 基于 OpenHarmony 7.0 发布地址: https://github.com/corespaceteam/MMSpace
❤4💯1

Channel
@Qiao_blog
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
8,220subscribers
+149 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001846056805 |
|---|---|
| Type | Channel |
| Username | @Qiao_blog |
| Description | 电报资源集 t.me/addlist/J7qyAY1cu-JlYzQ9 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 November 2026 |
| Measurements held | 28 |
| Confirmed unchanged | 1 time, most recently 19 November 2026 |
| On Telegram | t.me/Qiao_blog |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 96% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Nov 2026, 15:37 | 8,220 | +7 |
| 14 Nov 2026, 08:10 | 8,213 | +10 |
| 9 Nov 2026, 00:00 | 8,203 | +7 |
| 5 Nov 2026, 19:50 | 8,196 | +10 |
| 2 Nov 2026, 10:17 | 8,186 | +6 |
| 30 Oct 2026, 07:06 | 8,180 | +8 |
| 27 Oct 2026, 11:16 | 8,172 | +17 |
| 24 Oct 2026, 01:38 | 8,155 | +2 |
| 20 Oct 2026, 19:50 | 8,153 | +7 |
| 17 Oct 2026, 14:40 | 8,146 | -9 |
| 15 Oct 2026, 00:49 | 8,155 | +3 |
| 12 Oct 2026, 03:21 | 8,152 | +9 |
| 5 Oct 2026, 11:16 | 8,143 | +13 |
| 27 Sept 2026, 06:42 | 8,130 | +9 |
| 18 Sept 2026, 08:38 | 8,121 | -5 |
| 13 Sept 2026, 17:40 | 8,126 | +55 |
| 9 Sept 2026, 12:21 | 8,071 | +5 |
| 3 Sept 2026, 20:16 | 8,066 | +5 |
| 31 Aug 2026, 03:43 | 8,061 | -8 |
| 27 Aug 2026, 17:15 | 8,069 | first reading |
64 posts held, back to 26 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 52 pages of 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 9 of 14 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 18 November 2026 |
|---|---|
| Posts held | 64 (26 June 2026 – 18 November 2026) |
| Views total | 19,757 |
| Reactions total | 38 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 19 Nov 2026, 20:04 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.
Lifetime counters from Telegram’s own channel header, read 19 November 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 15 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.
126 reactions across 37 posts, in 14 distinct kinds. The most used accounts for 27.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 35 | 27.8% | |
| 😁 | 24 | 19.0% | |
| ❤ | 23 | 18.3% | |
| 💘 | 10 | 7.94% | |
| 🥰 | 8 | 6.35% | |
| 🤯 | 7 | 5.56% | |
| 🤪 | 6 | 4.76% | |
| 💯 | 4 | 3.17% | |
| 👏 | 2 | 1.59% | |
| 🕊 | 2 | 1.59% | |
| 🫡 | 2 | 1.59% | |
| 👎 | 1 | 0.794% | |
| 🤨 | 1 | 0.794% | |
| 🤷♂ | 1 | 0.794% |
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 40 of the 64 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 126 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 64 most recent posts we hold, published 26 June 2026 to 18 November 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.
Telegram’s own ‘edited’ marker: 4 of 14 posts held from the last 30 days (28.6%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
MMSpace 蒙蒙空间 #虚拟机 #开源鸿蒙 #安卓 #Android #OpenHarmony #desktop #桌面 给安卓手机装上 MMSpace,就能体验 OpenHarmony/开源鸿蒙 的桌面和应用。 无需 Root,无需刷机,原来的安卓系统照常使用。 (MM是蒙蒙的简写,蒙蒙是谁,「鸿蒙」的蒙,你也可以叫它为蒙蒙空间) 基于 OpenHarmony 7.0 发布地址: https://github.com/corespaceteam/MMSpace
❤4💯1
🖥 Motty 是一款免费开源的原生 SSH 客户端,SSH、SFTP、端口转发、VNC/RDP 远程桌面和 AI 助手全在一个窗口里。 基于 Go 和 Viva 框架,不用 Electron,启动不到一秒;支持 macOS、Windows 和 Linux,Apache-2.0 许可,不需要账号。 🔗 https://motty.page/zh
Photo, posted without a caption
👍3
发现一个 mihomo 客户端,这交互逻辑绝了呀,好好玩 💯 Bowel 是一款基于 mygo 的 macOS、Windows 和 Linux mihomo 客户端,具有以下特性 1. 超赞的视觉风格和动画效果 2. 直接支持 URL,也支持订阅 3. 使用摄像头或屏幕扫描二维码 4. 为不同通道提供智能路由 发布页 https://github.com/21stware/bowel
👍5❤2👎1😁1
Photo, posted without a caption
#符文化传承 #玄学 ▎Source
😁6👍1
赤喵杯季军赛MO完整版 奥哈拉来人啦!!#海贼王#赤喵杯#这也能开播 ▎Source
作者不明情况失联别人逆向出来的Multitts https://github.com/xiyuqiangshou/multitts-reverse
❤2
HyperOS 还是太抽象了。 最近发现 ChatGPT 点「使用 Google 登录」一直转圈,账号列表死活不出来,用邮箱登录也是一样,压根进不去登录流程。 抓日志才发现,Google 已经返回候选凭据,卡死的是小米自己的凭据选择器 MiuiCredentialManager 4.0.4.1: com.android.credentialmanager/.CredentialSelectorActivity 系统给它发了一个约 557 KiB 的启动事务,直接报 Binder buffer full 和 TransactionTooLargeException。拉起新进程重试,还是失败,最后就卡死了。 整个过程: ChatGPT 登录页 → CredentialManager 预取 Google ID Token → GMS 返回账号候选和头像 → 小米凭证选择器启动事务过大 → CredentialSelectorAc…
❤2😁2
大量性能优化 支持旧版本砸壳 支持多区域识别 优化交互逻辑 修复了部分解密失败 以及。。。很多小细节 自行体验吧 @IPADumpBot 有啥问题欢迎反馈
因科特鼠标驱动 #驱动 #driver #github #鼠标 #工具 #tools 跑路了网页驱动用不了 https://github.com/oexi/incott-driver-desktop
关于Google play上面的常用链接 #Google #playstore #APP #update 在许多 Android 设备(国产 ROM 或未完全内置完整谷歌框架的手机)上,这些系统组件应用在 Play 商店中往往会被隐藏,通过以下直接链接可以快速进行更新或手动安装 一、 Google 核心框架与系统组件 这两个是谷歌服务运行与网页渲染的核心基础: ❶ Google Play 服务 (Google Play Services) https://play.google.com/store/apps/details?id=com.google.android.gms ❷ Android System WebView https://play.google.com/store/apps/details?id=com.google.android.webview ③ Google Play 商店 (Google Play S…
👍4😁2
Showing the 12 most recent of 64 posts we hold for @Qiao_blog. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 2 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.
@Qiao_blog 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.
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 5 seed channels' Telegram-generated recommendation lists 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 19 November 2026 — this entry's latest reading, not the date you are reading this.
“喬苑” (@Qiao_blog), 8,220 subscribers as measured 19 November 2026. Telegram Register, tgregister.com/channel/Qiao_blog.
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.