最近讨论群里广告有点猖獗,开了入群验证试试,如果有被误封的请私聊找我解(希望不会有)

Channel
Yunfi Channel
@YunfiChannel
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
121subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001927185100 |
|---|---|
| Type | Channel |
| Username | @YunfiChannel |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/YunfiChannel |
Topic
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 26 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 16:57 | 121 | +1 |
| 24 Aug 2026, 14:25 | 120 | +1 |
| 16 Aug 2026, 19:07 | 119 | -1 |
| 9 Aug 2026, 04:01 | 120 | no change |
| 7 Aug 2026, 11:43 | 120 | first reading |
Engagement
13 posts held, back to 11 July 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 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 13 posts for this entry, the most recent from 20 May 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
18 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 55.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🥰 | 10 | 55.6% | |
| 👍 | 7 | 38.9% | |
| ❤ | 1 | 5.56% |
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 7 of the 13 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 18 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 11 July 2025 to 20 May 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.
Recent posts
由于微软又更改了 edge tts 接口的认证,所以自部署大声朗读的用户需要更新部署才能继续使用 影响 ms-ra-forwarder-for-ifreetime 和 read-aloud 用户,包括任何部署方式 (Vercel,Cloudflare Workers, Docker)。 对于 Vercel 和 Cloudflare Workers,一般同步自己的fork会自动触发更新(不行的话就重新部署一遍吧),docker 用户重新 pull 更新的镜像再重新启动 container 即可 #项目更新 #readaloud
同步功能上线了!可以尝试使用了,每次更改配置后点击同步按钮,即可自动分析需要上传/下载,方便地在多台设备间同步配置(再也不用手动导出、复制到另一台设备再导入了) 功能上还有不少东西可以做,比如配置更改后自动尝试同步;冲突时首先尝试使用类似 git 的3-Way merge 解决等等,过段时间我看看使用情况再决定加不加这些功能吧 https://imageport.app/zh/settings/profile GitHub: https://github.com/yy4382/s3-image-port #s3imageport #项目更新
🥰3
S3 image port 的多设备间设置同步应该很快就能写完了,端到端加密,我会提供一个默认的同步后端和数据库,可以直接使用 由于用户不多(哭),所以估摸着这个同步服务可以比较长久的一直提供下去,不过作为 local first 的应用,即使没有同步(默认也不会开启)也不影响使用 整个同步模块大概新增了 3000 多行代码,是这个项目里最复杂的一个模块了,各种情况应该是考虑的是比较充分了,基本上可以自动判断应该上传还是下载(覆盖本地时有确认),即使冲突了也有一个比较直观的 diff viewer 目前就差本地化没做了,这周应该可以做完
S3 Image Port 25年11月更新 这段时间在功能和界面上主要更新了以下内容: 1. 键(名称)模版(Key template)可以设置多个(作为预设),在上传时可以针对每个图片方便地切换使用这些模版。 2. 图片重命名功能。 3. 重新设计的文档。 4. 对于上传时的配置修改卡片和图库中的图片卡片的样式和功能革新 同时,还带来了大量引擎盖下的优化和重构,如抛弃 Next.js,配置内容的储存方式更新,使用浏览器运行测试等。 https://imageport.app BTW S3 Image Port 项目很快就要两岁了,感谢大家支持!喜欢的话可以点个 Star GitHub #s3imageport #项目更新
❤1👍1
Channel photo updated
给 TTS Importer 添加了“开始之前”引导,让用户了解第一步应该做什么 以及其他小更新,如完善报错信息,给出常见报错解决方案等 #ttsimpoter #项目更新
👍2🥰1
用来快捷切换搜索引擎的小书签项目 Search Engine Switch 新支持了两个搜索引擎(?): ChatGPT 和 Claude #项目更新
TTS Importer 现在也支持Azure 官方 API 版本的一次导入多个语音了,可以一次直接把所有中文语音的所有语音风格导入好 网页 App GitHub #ttsimporter #项目更新
👍2
S3 Image Port 达到100 star了!感谢各位支持💝 Read-aloud 现在 98 star,各位看我的小眼神👀 #s3imageport #readaloud
🥰2👍1
TTS Importer 现在在导入 read aloud 的语音时,可以一次导入多个语音了(全部发音人,或者所有中文发音人) 支持阅读和爱阅记 #ttsimporter #readaloud #项目更新
👍1
https://x.com/yunfini/status/1955559177553920408?s=46 是个 thread
Showing the 12 most recent of 13 posts we hold for @YunfiChannel. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Mentions
Named by 1 registered channel — 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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Yunfi Channel” (@YunfiChannel), 121 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/YunfiChannel.
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.