Channel
@Cronfox
On this record: Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry
1,191subscribers
-2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001205857022 |
|---|---|
| Type | Channel |
| Username | @Cronfox |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/Cronfox |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 12:31 | 1,191 | -3 |
| 7 Aug 2026, 08:23 | 1,194 | +1 |
| 6 Aug 2026, 21:16 | 1,193 | no change |
| 6 Aug 2026, 21:05 | 1,193 | first reading |
20 posts held, back to 27 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 1 pageof 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 4 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 20 (27 July 2026 – 6 August 2026) |
| Views total | 5,897 |
| Reactions total | 14 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 21:16 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.
14 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 57.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤣 | 8 | 57.1% | |
| 👍 | 5 | 35.7% | |
| ❤ | 1 | 7.14% |
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 4 of the 20 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 14reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 27 July 2026 to 6 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.
这下彻底死心了：甲骨文发布通知 免费VPS必须在8月18日前主动降配 否则删鸡 https://www.landian.news/archives/114212.html 在通知发布后存量用户的虚拟机如何处理？按照当时甲骨文的说法，用户应该主动缩减实例的规格以满足最新的永久免费政策。不过当时也有网友联系甲骨文客服咨询这件事，客服给出的答复是存量用户可以继续共享最高 4 颗内核 + 24GB 内存，而新开通的永久免费账户只能获得 2 颗内核 + 12GB 内存。 因此当时主动缩减实例规格的用户其实是亏了，因为如果没有主动缩减实例规格的话或许还可以继续获得更多的 CPU 核心和内存，只是现在甲骨文开始批量向用户发送通知：必须在 8 月 18 日前主动缩减配额，否则虚拟机将会被甲骨文终止。
🤣2
因为我昨天一气之下就是这么干的 用的也不是顶级模型
另外之前moyix在推特说“现在买外设之前已经不再检查是否有 Mac/Linux 驱动了，因为用 LLM 可以在几小时内从 Windows 二进制驱动逆向工程出一个可用的替代驱动。” 这个是真的 但是如果你真的想这么玩 前提条件就是 这个外设是基于 串口/HID/WinUSB/LibUSB 的
现在，鸿蒙电脑能不能作为主力机？ 首先如果你是游戏玩家那我建议你需要额外准备游戏设备 然后分为几个情况 1. 你是与鸿蒙相关的开发者，是下面的子集 可以当主力机，但是需要承担目前生态不成熟的风险与只能做鸿蒙开发机器的准备 2. 你是学习计算机科学与技术专业的学生 得看HDC2026上Jetbrains大饼画出来了吗，然后如果你需要用一些奇怪东西不好意思你要么虚拟机要么...承担风险 例如，你需要用该死的...keil mdk 3. 你可以选择macbook 但是不依赖苹果生态或特有软件的学生 勉强可以作为主力，但同样要承担风险 4. 你是学习其他理工科的学生 gg 5. 你是学艺术类的 软件跟不上，同样gg
👍5
Photo, posted without a caption
感谢DSv4 Flash，我搞了个配影刃3无线的奥特极速网页版
今天捡漏出了俩大红 一共20块 一个AKG K92耳机(应该是正品) 一个ROG战刃3标准版(肯定是正品，但滚轮似乎有点间歇性问题)
好了 flash已出
所以 有吃🦊的吗
他们需要一个有明确经验的 所以gg
主业是...补钙 还是增高那种
🤣3
接了个面试 似乎是个药厂
Showing the 12 most recent of 20 posts we hold for @Cronfox. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
你有GiffGaff吗
The shares total 104%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 27 July 2026 to 6 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Cronfox's Channel” (@Cronfox), 1,191 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/Cronfox.
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.