❓ #问题求助 OpenCode Go的ds v4 flash速度究竟如何? https://meta.appinn.net/t/topic/90493
👍1

Channel
@appinnfeed
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
32,788subscribers
+3,186 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001073712343 |
|---|---|
| Type | Channel |
| Username | @appinnfeed |
| Description | 这里有小众软件和发现频道的内容更新,以及一个绑定的私有群组。 💬 吹水群:https://t.me/appinn 📖 RSS 订阅地址:https://feeds.feedburner.com/apipnntgfeed 📣 发现频道 @appinnfaxian 在这个频道发布广告(Buy ads on this channel): https://telega.io/c/appinnfeed |
| Created | 28 December 2016 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/appinnfeed |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 08:45 | 32,788 | +24 |
| 20 Aug 2026, 22:16 | 32,764 | +38 |
| 19 Aug 2026, 20:03 | 32,726 | +33 |
| 18 Aug 2026, 20:16 | 32,693 | +44 |
| 17 Aug 2026, 20:34 | 32,649 | +916 |
| 16 Aug 2026, 20:08 | 31,733 | +1,988 |
| 15 Aug 2026, 10:44 | 29,745 | +19 |
| 14 Aug 2026, 00:27 | 29,726 | +22 |
| 12 Aug 2026, 22:05 | 29,704 | +25 |
| 11 Aug 2026, 19:15 | 29,679 | +1 |
| 10 Aug 2026, 17:05 | 29,678 | +22 |
| 9 Aug 2026, 15:14 | 29,656 | +11 |
| 8 Aug 2026, 13:42 | 29,645 | +25 |
| 7 Aug 2026, 13:47 | 29,620 | +9 |
| 6 Aug 2026, 15:13 | 29,611 | +9 |
| 6 Aug 2026, 01:52 | 29,602 | no change |
| 5 Aug 2026, 23:53 | 29,602 | first reading |
195 posts held, back to 3 August 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 35 pagesof 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 74 of 195 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 22 August 2026 |
|---|---|
| Posts held | 195 (3 August 2026 – 22 August 2026) |
| Views total | 213,144 |
| Reactions total | 129 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Aug 2026, 17:13 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 22 August 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.
122 reactions across 59 posts, in 12 distinct kinds. The most used accounts for 36.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 44 | 36.1% | |
| ❤ | 36 | 29.5% | |
| 😁 | 11 | 9.02% | |
| 👎 | 9 | 7.38% | |
| 😘 | 5 | 4.10% | |
| 🥴 | 5 | 4.10% | |
| 👀 | 3 | 2.46% | |
| 💩 | 2 | 1.64% | |
| 🙈 | 2 | 1.64% | |
| 🤣 | 2 | 1.64% | |
| 🤨 | 2 | 1.64% | |
| 🐳 | 1 | 0.82% |
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 74 of the 195 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 129reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 195 most recent posts we hold, published 3 August 2026 to 22 August 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.
❓ #问题求助 OpenCode Go的ds v4 flash速度究竟如何? https://meta.appinn.net/t/topic/90493
👍1
📣 #发现频道 免费桌面护眼软件,蓝光过滤 + 可爱宠物久坐提醒,不锁屏不打扰 https://meta.appinn.net/t/topic/90482
💧 #小众软件 Windows 11 时间点还原默认开启,真后悔药:可恢复系统与用户文件数据 https://www.appinn.com/windows-11-point-in-time-restore-default/ 你有没有遇到过这种情况:桌面上保存了一个重要文件,清理电脑时顺手删除。几个小时后才发现,删掉的是正在使用的资料,回收站里也没有了… Windows 11 新加入的时间点还原(Point-i
❓ #问题求助 各位最近用 AdGuard 浏览器插件的时候有碰到页面炸布局的情况吗? https://meta.appinn.net/t/topic/90469
👍1
📣 #发现频道 GotifyInbox Gotify 消息推送桌面客户端 https://meta.appinn.net/t/topic/90457
📣 #发现频道 DownloadIt - FlashGot 复刻版 https://meta.appinn.net/t/topic/90452
❤1
💧 #小众软件 26/27 英超赛程日历,临时上线! https://www.appinn.com/26-27-premier-league-calendar/ Hi 各位,这是一份由青小蛙维护的2026~2027赛季英格兰足球超级联赛赛程、比分、进球日历,可订阅到手机/电脑日历应用中,会自动更新比分。@Appinn 终于赶在英超开赛前做好啦。 比较简单,订阅
非常有趣啊,有同学通过其数字签名确认,是 Apowersoft 出品... https://meta.appinn.net/t/89444/33
😁1
💧 #小众软件 本周赛博领鸡蛋(8.21~8.27):《卡牌末日》《阿尔比恩在线》《沙漠房车漫游》 https://www.appinn.com/eggs-26821/ 本周赛博领鸡蛋,Epic Games 共送出 2 款电脑游戏、1 款手机游戏。电脑游戏为《卡牌末日》《阿尔比恩在线》,手机游戏为《沙漠房车漫游》。 《卡牌末日》/ Cardpocalypse 《卡牌末
💧 #小众软件 superfile – 终端也需要一个好用的文件管理器 https://www.appinn.com/superfile-tui-files-explorer/ 在终端里找到一个文件,你会选择打开资源管理器,还是继续用 cd + ls 慢慢寻找? 终端非常适合执行命令,但在浏览、查找、整理文件时,图形界面的直观依然很有吸引力。 superfile 漂亮的现代终
📣 #发现频道 Epic手机喜加一 《Caravan SandWitch》截止8.27 https://meta.appinn.net/t/topic/90433
👍1
📣 #发现频道 IDM 智能管理器:按需控制 IDM 浏览器扩展开关的浏览器扩展 https://meta.appinn.net/t/topic/90432
Showing the 12 most recent of 195 posts we hold for @appinnfeed. 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 — 121,264 of 1,583,249entries 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.
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.
Named by 23 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.
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 9 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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“Appinn Feed|小众软件” (@appinnfeed), 32,788 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/appinnfeed.
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.