https://github.com/NSRingo/MapKit/releases/tag/v4.7.0-beta1 注意:从这里获取的版本是静态的,不会随新的发布自动更新,只有发布路径带有 /releases/latest/download/ 的插件与模块才具有自动更新能力,仅供尝鲜
❤1
Signed ㅤ Miss. ㅤㅤChristine

Channel
@GetSomeFriesChannel
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry
19,841subscribers
+127 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001615844234 |
|---|---|
| Type | Channel |
| Username | @GetSomeFriesChannel |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 21 August 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 21 August 2026 |
| On Telegram | t.me/GetSomeFriesChannel |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Aug 2026, 22:27 | 19,841 | +7 |
| 20 Aug 2026, 18:43 | 19,834 | +7 |
| 19 Aug 2026, 20:46 | 19,827 | +5 |
| 17 Aug 2026, 18:49 | 19,822 | +2 |
| 16 Aug 2026, 18:35 | 19,820 | +15 |
| 15 Aug 2026, 07:05 | 19,805 | +13 |
| 13 Aug 2026, 22:49 | 19,792 | +21 |
| 12 Aug 2026, 16:43 | 19,771 | +8 |
| 11 Aug 2026, 15:44 | 19,763 | +5 |
| 10 Aug 2026, 15:32 | 19,758 | +7 |
| 9 Aug 2026, 17:21 | 19,751 | +12 |
| 8 Aug 2026, 16:52 | 19,739 | +9 |
| 7 Aug 2026, 16:20 | 19,730 | +4 |
| 6 Aug 2026, 15:55 | 19,726 | +12 |
| 6 Aug 2026, 05:16 | 19,714 | first reading |
23 posts held, back to 27 March 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.
| Window | Rolling 30 days · latest post in window 22 August 2026 |
|---|---|
| Posts held | 23 (27 March 2026 – 22 August 2026) |
| Views total | 84,010 |
| Reactions total | 254 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Aug 2026, 21:42 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. Below Telegram’s rounding threshold, so these counts are exact.
408 reactions across 21 posts, in 12 distinct kinds. The most used accounts for 55.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 225 | 55.1% | |
| 👍 | 117 | 28.7% | |
| 🤮 | 15 | 3.68% | |
| 🥰 | 13 | 3.19% | |
| 👎 | 10 | 2.45% | |
| 🦄 | 10 | 2.45% | |
| 💩 | 5 | 1.23% | |
| 🤔 | 5 | 1.23% | |
| 😱 | 3 | 0.735% | |
| 👏 | 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 21 of the 23 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 408reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 23 most recent posts we hold, published 27 March 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @GetSomeFriesChannel. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 23 most recent posts we hold for this entry, published 27 March 2026 to 22 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
https://github.com/NSRingo/MapKit/releases/tag/v4.7.0-beta1 注意:从这里获取的版本是静态的,不会随新的发布自动更新,只有发布路径带有 /releases/latest/download/ 的插件与模块才具有自动更新能力,仅供尝鲜
❤1
Signed ㅤ Miss. ㅤㅤChristine
📱 哔哩哔哩国际版 App 全球上线,安卓先行 iOS 即将推出 哔哩哔哩国际版 App 已全球上线,目前先推出 Android 版,iOS 版即将到来。该版本主打全球化内容分发、更好的本地化,以及免实名认证的便捷注册。 官方提示:下载左上角带地球图标的粉色 App 即为国际版,更多本地化优化与功能将陆续上线。 bilibili Creator Hub(@bilibili_create) Google Play 🌸 在花频道 · 茶馆水群 · 投稿通道
🤮15👎5❤2🔥2👍1💩1
Signed 抗倒伏小麦
#Test #Loon4Mac Loon for Mac 0.3.0(66)版本已准备好在 Mac OS上进行测试。 - 全新的 UI - 整个 App 使用 Appkit 完全重新实现,丢弃原来的 SwiftUI - 侧边栏支持展开收起 状态栏面板鼠标放在 menu 上会自动出现子面板 - 重构整个引导流程,激活、安装帮助工具更加方便安全 - 重构XPC 进程交互模块,主 app 和 NE 内核交互更加安全便捷 - 调整进程统计数据逻辑,更加精准高效 - 优化节点、策略组测速逻辑,减少节点过多导致的 UI 卡顿和 CPU 占用率高的问题 - 增加状态栏配置,可以自己设置显示内容、显示策略组的数量 - 增加 UI 主题,可以自己设置或者导入他人主题 - 优化插件详情页的 UI 设计 PS : 目前主要重新设计了一二级的展示内容的 UI,编辑配置的 UI 后续会更进 最新包下载地址:https://github.com/Lo…
👍13❤5
Signed ㅤ Miss. ㅤㅤChristine
iRingo: 🌤 WeatherKit v3.3.0 已发布 Created by @[delete] & @WordlessEcho & @001 & @Larry052210 Available in 🎈Loon(推荐), 🐿️Egern(推荐), 🏂Stash, 📈Surge(😁), 🚀Shadowrocket(仅 Rewrite 版), 🌀Quantumult X(仅本地版) Only for iOS 18, macOS 15, watchOS 11 or later What's New? 1. 新增加拿大 AQHI、香港 AQHI、AQHI-Multi(中国 / 中国+香港)及中国致死风险 AQHI(中国 / 中国+香港)六种空气质量健康指数算法,并可直接在插件与模块参数中选择; 2. 新增 WeatherKit 兼容的香港与中国 AQHI 本地标尺响应,包含多语言名称、健康风险等级、颜色渐变和健康建议;…
👍27❤6💩2👏1
Signed ㅤ Miss. ㅤㅤChristine
清晰一点的图
❤9
Signed ㅤ Miss. ㅤㅤChristine
Posted without readable text
👍6🥰1
Signed ㅤ Miss. ㅤㅤChristine
https://github.com/NSRingo/WeatherKit/releases/tag/v3.3.0-beta2 整合来自 @WordlessEcho 4.0 版本的空气质量重构 注意:从这里获取的版本是静态的,不会随新的发布自动更新,只有发布路径带有 /releases/latest/download/ 的插件与模块才具有自动更新能力,仅供尝鲜
🥰12❤3
Signed ㅤ Miss. ㅤㅤChristine
iRingo: 🌤 WeatherKit v3.2.0 已发布 Created by @[delete] & @WordlessEcho & @001 & @Larry052210 Available in 🎈Loon(推荐), 🐿️Egern(推荐), 📈Surge(😁), 🏂Stash, 🚀Shadowrocket(仅 Rewrite 版), 🌀Quantumult X(仅本地版) Only for iOS 18, macOS 15, watchOS 11 or later What's New? 1. 云函数版可以同时在 workers 与 pages 部署了,现在任何人都可自行部署,全部依赖均已改为 public package; 2. 新的 Rewrite 版(云函数版)提供 endpoint 设置,用户可根据需求进行切换; 3. 对天气预警数据的填补及页面修复,QWeather 第三方的天气预警页面现在被苹…
❤53
Signed ㅤ Miss. ㅤㅤChristine
更新后的天气预警信息将更加详细,但极端天气警报通知还未能探明是否可以触发。
👍34❤5
Signed ㅤ Miss. ㅤㅤChristine
https://github.com/NSRingo/WeatherKit/releases/tag/v3.2.0-beta5 1. 天气预警数据源改为从和风天气官方气象预警 API 接口,不再通过和风天气的城市 html 页面裁剪获得。 2. 简化插件模块语法,不再需要重定向 html 页面。 3. 现在同步支持填补天气 app 内的天气预警板块了,在中国地区将会显示更丰富准确的天气预警信息内容。
👍15❤2
Signed ㅤ Miss. ㅤㅤChristine
https://github.com/NSRingo/WeatherKit/releases/tag/v3.2.0-beta4 1. 修复了模块正则中参数写反导致匹配不到无法触发的问题 2. 将天气预警 api 的改写移到了 request 中以加速响应速度并解决意外跳转到 developer.apple.com 的问题
🦄10❤6
Signed ㅤ Miss. ㅤㅤChristine
https://github.com/NSRingo/WeatherKit/releases/tag/v3.2.0-beta3 此版本为候选正式版,如无问题将作为正式版发布,请各位测试反馈。
❤1
Signed ㅤ Miss. ㅤㅤChristine
Showing the 12 most recent of 23 posts we hold for @GetSomeFriesChannel. 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 — 217,745 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.
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.
Named by 5 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.
@GetSomeFriesChannel 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.
References a handle that is not a live channel — we have no record it ever was one.
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 21 August 2026 — this entry's latest reading, not the date you are reading this.
“🍟 整点薯条: 频道” (@GetSomeFriesChannel), 19,841 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/GetSomeFriesChannel.
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.