📣 #发现频道 〖开发者自荐〗抽屉柜 Drawer:一个完全留在自己电脑里的 Windows 数字抽屉 https://meta.appinn.net/t/topic/92989
👍1

Channel
@appinnfeed
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
33,700subscribers
+4,098 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 | 4 October 2026 |
| Measurements held | 36 |
| Confirmed unchanged | 1 time, most recently 4 October 2026 |
| On Telegram | t.me/appinnfeed |
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 9 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Oct 2026, 22:57 | 33,700 | +144 |
| 27 Sept 2026, 16:00 | 33,556 | +195 |
| 17 Sept 2026, 17:19 | 33,361 | +55 |
| 15 Sept 2026, 12:39 | 33,306 | +35 |
| 13 Sept 2026, 20:18 | 33,271 | +16 |
| 12 Sept 2026, 00:19 | 33,255 | +21 |
| 9 Sept 2026, 12:21 | 33,234 | +206 |
| 6 Sept 2026, 03:42 | 33,028 | +13 |
| 3 Sept 2026, 20:55 | 33,015 | +25 |
| 2 Sept 2026, 08:54 | 32,990 | +13 |
| 1 Sept 2026, 10:33 | 32,977 | +23 |
| 31 Aug 2026, 07:03 | 32,954 | +17 |
| 30 Aug 2026, 06:03 | 32,937 | +20 |
| 29 Aug 2026, 03:17 | 32,917 | +22 |
| 28 Aug 2026, 01:54 | 32,895 | +23 |
| 27 Aug 2026, 04:42 | 32,872 | +6 |
| 26 Aug 2026, 05:54 | 32,866 | +23 |
| 25 Aug 2026, 04:52 | 32,843 | +20 |
| 24 Aug 2026, 01:03 | 32,823 | +35 |
| 22 Aug 2026, 08:45 | 32,788 | first reading |
574 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 103 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 74 of 243 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 October 2026 |
|---|---|
| Posts held | 574 (3 August 2026 – 6 October 2026) |
| Views total | 212,343 |
| Reactions total | 172 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Oct 2026, 20:27 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 6 October 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.
408 reactions across 165 posts, in 20 distinct kinds. The most used accounts for 40.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 164 | 40.2% | |
| ❤ | 89 | 21.8% | |
| 😁 | 46 | 11.3% | |
| 👎 | 23 | 5.64% | |
| 🤯 | 15 | 3.68% | |
| 🐳 | 14 | 3.43% | |
| 🤡 | 11 | 2.70% | |
| 🤔 | 8 | 1.96% | |
| 💩 | 5 | 1.23% | |
| 😘 | 5 | 1.23% | |
| 🥴 | 5 | 1.23% | |
| 🔥 | 4 | 0.98% | |
| 🤣 | 4 | 0.98% | |
| 👀 | 3 | 0.735% | |
| 🤬 | 3 | 0.735% | |
| ☃ | 2 | 0.49% | |
| 🙈 | 2 | 0.49% | |
| 🤨 | 2 | 0.49% | |
| 🤷♂ | 2 | 0.49% | |
| 🙏 | 1 | 0.245% |
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 199 of the 574 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 415 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 574 most recent posts we hold, published 3 August 2026 to 6 October 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.
📣 #发现频道 〖开发者自荐〗抽屉柜 Drawer:一个完全留在自己电脑里的 Windows 数字抽屉 https://meta.appinn.net/t/topic/92989
👍1
📣 #发现频道 【开发者自荐】受够了臃肿,自己写了一个干净纯粹的播放器(兼容win7) https://meta.appinn.net/t/topic/92981
👍2
📣 #发现频道 〖开发者自荐〗MultiTool Office:一个轻量、现代的 Windows AI 办公工作台 https://meta.appinn.net/t/topic/92980
👍1
❓ #问题求助 GITHUB又又又打不开了 https://meta.appinn.net/t/topic/92977
📣 #发现频道 【开发者自荐】会钟:开会投屏的发言计时器,手机控场、大屏同步 https://meta.appinn.net/t/topic/92973
💧 #小众软件 Windows 11 终于认识波浪线 ~ 了:和 Linux、macoS 一样直达用户目录 https://www.appinn.com/windows-11-tilde-user-folder/ 如果你用过 Linux 或 macOS,肯定见过 ~,只需要在终端中输入 ~/Downloads 就代表着当前用户的下载目录。 好处是方便,非常方便。 不需要去输入完整的路径,也不需要去考虑当前用户名是什么。 比如用户名为 Appinn,那么 ~ 分别代表: Linux:/home/appinn macOS:/Users/appinn 所以无论用户名是什么,都可以直接用: cd ~/…
👍12
📣 #发现频道 飞跃视频工具 – 在电脑本地批量完成视频包装:水印、落版、改尺寸、规范命名、可记忆方案以及多方案输出 [macOS]+[windows]均可用 https://meta.appinn.net/t/topic/92964
👍1
📣 #发现频道 【开发者自荐】在GPT打工的大肥鱼:陪你等 thinking 的 Codex 桌宠(macOS) https://meta.appinn.net/t/topic/92960
📣 #发现频道 【开发者自荐】A13Rollcall V6.8| 基于自研第六代A13抽取引擎开发的面向中小学课堂点名抽背系统 https://meta.appinn.net/t/topic/92956
❓ #问题求助 想问一下有没有免费的没有水印HTML半动态托管 https://meta.appinn.net/t/topic/92953
❓ #问题求助 有没有同步软件可以只记录差异部分(记录要删除文件, 复制新增/改变的文件)来实现两地文件同步? https://meta.appinn.net/t/topic/92950
触发 Google 账号自拍验证注册
Showing the 12 most recent of 574 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.
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 27 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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 4 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 29 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 4 October 2026 — this entry's latest reading, not the date you are reading this.
“Appinn Feed|小众软件” (@appinnfeed), 33,700 subscribers as measured 4 October 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.