▎Gudong! · 荷塘有鲤 v2.0 一口养在桌面上的水彩荷塘:开场就是 8 条成年大锦鲤(红白 / 昭和 / 乌鲤 / 丹顶…) 在荷叶间游,可以喂食、可以亲手画鱼、画多少条都行,水面有风吹涟漪, 它钉在桌面图标层下面——不挡图标、不占任务栏,开机即在。 确实挺好看的,苏雅。偏水墨风格,动态游动,水波很真实。当背景板也不错。 不过缺点就是不支持双频设备,目前还是只能显示在一个屏幕上,期待作者后续升级。 #壁纸 #主题 #桌面 #windows 地址:点我下载
👍3

Channel
@feiyu123
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
64,337subscribers
+3,980 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001537708370 |
|---|---|
| Type | Channel |
| Usernames | @catlucky3 @feiyu123 |
| Description | 分享一些工具,软件,浏览器插件脚本,网站,歌曲,互联网相关资讯,开源项目,碎碎念的想法 等等。 投稿互推合作机器人: @feiyutian_bot |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 132 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/feiyu123 |
Software piracy — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 12 Nov 2026, 16:08 | 64,337 | +14 |
| 12 Nov 2026, 08:16 | 64,323 | +148 |
| 10 Nov 2026, 09:00 | 64,175 | +8 |
| 10 Nov 2026, 08:00 | 64,167 | +103 |
| 8 Nov 2026, 22:10 | 64,064 | +5 |
| 8 Nov 2026, 17:18 | 64,059 | +138 |
| 7 Nov 2026, 11:26 | 63,921 | no change |
| 7 Nov 2026, 11:25 | 63,921 | +95 |
| 6 Nov 2026, 13:24 | 63,826 | +8 |
| 6 Nov 2026, 07:49 | 63,818 | +43 |
| 5 Nov 2026, 12:35 | 63,775 | +1 |
| 5 Nov 2026, 06:11 | 63,774 | +19 |
| 4 Nov 2026, 13:08 | 63,755 | +16 |
| 4 Nov 2026, 07:27 | 63,739 | +22 |
| 3 Nov 2026, 16:17 | 63,717 | +10 |
| 3 Nov 2026, 09:07 | 63,707 | +21 |
| 2 Nov 2026, 17:38 | 63,686 | +19 |
| 2 Nov 2026, 10:59 | 63,667 | +68 |
| 1 Nov 2026, 15:20 | 63,599 | +16 |
| 1 Nov 2026, 07:58 | 63,583 | first reading |
198 posts held, back to 29 July 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 233 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.
| Window | Rolling 30 days · latest post in window 13 November 2026 |
|---|---|
| Posts held | 198 (29 July 2026 – 13 November 2026) |
| Views total | 276,237 |
| Reactions total | 407 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 2026, 14:29 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 13 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
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.
842 reactions across 175 posts, in 10 distinct kinds. The most used accounts for 48.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 406 | 48.2% | |
| ❤ | 317 | 37.6% | |
| 👏 | 27 | 3.21% | |
| 👌 | 25 | 2.97% | |
| 🥰 | 22 | 2.61% | |
| 🔥 | 20 | 2.38% | |
| 🎉 | 7 | 0.831% | |
| 😭 | 7 | 0.831% | |
| 💩 | 6 | 0.713% | |
| 💯 | 5 | 0.594% |
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 194 of the 198 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 842 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 198 most recent posts we hold, published 29 July 2026 to 13 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Measured over the 198 most recent posts we hold, published 29 July 2026 to 13 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Telegram’s own ‘edited’ marker: 7 of 69 posts held from the last 30 days (10.1%) 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).
▎Gudong! · 荷塘有鲤 v2.0 一口养在桌面上的水彩荷塘:开场就是 8 条成年大锦鲤(红白 / 昭和 / 乌鲤 / 丹顶…) 在荷叶间游,可以喂食、可以亲手画鱼、画多少条都行,水面有风吹涟漪, 它钉在桌面图标层下面——不挡图标、不占任务栏,开机即在。 确实挺好看的,苏雅。偏水墨风格,动态游动,水波很真实。当背景板也不错。 不过缺点就是不支持双频设备,目前还是只能显示在一个屏幕上,期待作者后续升级。 #壁纸 #主题 #桌面 #windows 地址:点我下载
👍3
▎BiliFlow v0.8.11 免费开源的 B 站视频下载工具 把喜欢的作品,带回自己的收藏空间 视频下载、批量归档与直播录制,让每一次喜欢,都有一份触手可及的本地收藏。 支持windows,macos和linux #下载 #bilibili #直播录制 #GitHub 地址:GitHub
👍3🔥1🥰1
#短讯 2026年11月11日光棍节开放注册 上午的一轮错过了,本轮 20:00 -- 22:00 点我注册
👍7😭2
#互推 【苹果限免】 App Store 限免应用 & ... 【炒币资讯】币圈快讯 【二次元美图】公诸同好 | 二次元美图分享 🅥 【资源分享】资源分享客栈-Applnn 【小说分享】Lemaned的宝藏书屋(轻小说书库) 【科技热点】APPDO的互联网记忆 【医学期刊】来一点医学科学前沿🤯🤯🥹🥹 【资源分享】飞鱼资源分享|冲浪指南|软件工具 【机场测评】小众机场测评 Powered by @Summer_Clear_Sky_Bot
❤3👍2
▎Mynah v0.1 开源数字人项目,一张肖像就能做成数字人,支持实时语音对话和表情动作。内置了 Luna、Nova 半身形象,可以直接在控制台里发布成频道。 对硬件要求比较高,至少需要6GB的显存,本机没有显卡,也可以只跑核心服务和控制台,把数字人引擎放到远程 GPU 机器上。 很适合研究学习,做自己的工作流,让数字人口播,对话,视频带货,知识库问答。 #GitHub #ai #数字人 地址: GitHub
🔥4❤2
▎GitHub 中文化 v1.6 把 GitHub 界面翻译成简体中文、繁体中文的浏览器扩展 只翻译界面,不碰用户内容:自述文件、评论、代码、提交消息、存储库名、用户名、自定义标签名等保持原文 这个插件相对油猴脚本的是加载更快,更加无感的切换,看不到画面的闪顿感。 目前支持chrome,edge,firefox,和其他支持chrome内核的浏览器都可以。可以从GitHub页面进入对应的浏览器下载。 #GitHub #翻译 #效率 #工具 地址:GitHub
▎第一试卷网下载器 可以通过条件筛选,关键词搜索下载第一试卷网的试卷,然后进行下载打印。 从一年级到九年级各科试卷都有,人教版,北师大版,苏教版,等各个地区学校的试卷都收录其中。 感觉画风很像ai做的,不过无论是ai还是古法编程,能实现自己想要的功能都永远是第一要义,目前支持win10和11版本。 #下载 #学习 #windows #知识 地址:点我下载
👏3❤1👌1👍1💯1
🚀 CrossWall (克洛斯) 高速大流量机场 每天一毛钱,看遍全世界 ➕ 超值套餐:20/月·857GB|60/年·每月285GB|75元·500GB永久包 🌩 高速线路:国际优质线路,高清播放、极速下载 ✈️ 全球节点:13个地区,30+节点,支持 Netflix / TikTok / Disney+ ⚙ 智能调度:独家DNS负载均衡,多人使用依旧流畅 📍 广泛适用:新疆、河南、江苏、福建等地区可用 📱 多端支持:手机、电脑、平板,一键连接 🔗 官网 | 💬 群组
👍3❤1👌1
飞鸟VPN | 一键解锁全球网络 覆盖全球 | 100+ 高速节点,多端同时在线 极致体验 | 5Gbps 高速专线,高清秒开无广告 安全可靠 | 专业加密隧道,隐私无忧 便捷支付 | 支持微信 / 支付宝 / USDT 全平台支持 | Windows / Mac / iOS / Android 免费试用:https://jl.vpnvpn.com 飞鸟官方客服:@feiniaojsbot @fnotoy
👍3
⭐️红杏云,新用户套餐8.8折,支持月付和一次性购买流量,不限制设备,稳定更新,已经运营3年多的机场。Netflix/Disney/ChatGPT流媒体全解锁,不限设备, 可以使用专属客户端更加稳定,让你不失联。 优惠码:hx2026 官网:https://hongxingdl.com
👍2
#系统推送 中文TG搜索bot,输入搜索关键词点击发送, 点击下方按钮,进行搜索
👍3
▎图片背景消除工具 v0.3.1 免费开源的图片背景消除工具。 将图片中无关背景元素批量式一并快速去除,全程本地化处理,适合处理隐私类图片、产品设计素材等日常抠图需求场景。 完全本地处理,有不同场景的模型,模型安装后可无网使用,不需要注册付费登录,也可以直接在网页上体验 仅支持 Win 10 ~ 11 64 位系统;苹果至高 macOS 27 M / A / intel 平台系统;Linux 涵盖支持 Ubuntu / Debian 等系统。 #抠图 #背景 #效率 #GitHub 地址:GitHub
👍2👌1🔥1
Showing the 12 most recent of 198 posts we hold for @feiyu123. 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.
@feiyu123 edited 4 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
We recorded 64 posts on @feiyu123 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
Named by 32 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
@feiyu123 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“飞鱼资源分享|冲浪指南|软件工具” (@feiyu123), 64,337 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/feiyu123.
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.