Telegram RegisterThe public register of Telegram
Telegram profile photo for 🌾 整点小麦:iOS/macOS App

Channel

🌾 整点小麦:iOS/macOS App

@GetSomeTriticumChannel

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

1,054subscribers

+18 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002412512905
TypeChannel
Username@GetSomeTriticumChannel
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live20 November 2026
Measurements held23
Confirmed unchanged1 time, most recently 20 November 2026
On Telegramt.me/GetSomeTriticumChannel

Topic

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 19 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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.

Growth

1,0361,0581,0477 August 2026 — 1,036 subscribers8 August 2026 — 1,036 subscribers11 August 2026 — 1,039 subscribers15 August 2026 — 1,041 subscribers17 August 2026 — 1,044 subscribers20 August 2026 — 1,045 subscribers24 August 2026 — 1,043 subscribers27 August 2026 — 1,039 subscribers30 August 2026 — 1,041 subscribers3 September 2026 — 1,042 subscribers8 September 2026 — 1,045 subscribers12 September 2026 — 1,048 subscribers16 September 2026 — 1,051 subscribers25 September 2026 — 1,053 subscribers4 October 2026 — 1,056 subscribers23 October 2026 — 1,057 subscribers25 October 2026 — 1,058 subscribers28 October 2026 — 1,057 subscribers1 November 2026 — 1,058 subscribers3 November 2026 — 1,057 subscribers6 November 2026 — 1,058 subscribers9 November 2026 — 1,056 subscribers20 November 2026 — 1,054 subscribers1,0547 August 202620 November 2026
23 measurements spanning 105 days, net +18. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,033–1,061 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 23
Measured (UTC)SubscribersChange
20 Nov 2026, 14:171,054-2
9 Nov 2026, 23:171,056-2
6 Nov 2026, 16:571,058+1
3 Nov 2026, 17:061,057-1
1 Nov 2026, 00:371,058+1
28 Oct 2026, 17:181,057-1
25 Oct 2026, 17:001,058+1
23 Oct 2026, 00:401,057+1
4 Oct 2026, 18:351,056+3
25 Sept 2026, 00:221,053+2
16 Sept 2026, 11:191,051+3
12 Sept 2026, 13:361,048+3
8 Sept 2026, 15:201,045+3
3 Sept 2026, 02:561,042+1
30 Aug 2026, 23:381,041+2
27 Aug 2026, 21:141,039-4
24 Aug 2026, 16:161,043-2
20 Aug 2026, 16:121,045+1
17 Aug 2026, 19:041,044+3
15 Aug 2026, 02:181,041first reading

Engagement

19 posts held, back to 18 May 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 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

20 reactions across 9 posts, in 3 distinct kinds. The most used accounts for 70.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1470.0%
👍525.0%
🔥15.00%

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 9 of the 19 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 20 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 18 May 2026 to 31 July 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.

Recent posts

27 Jul 2026, 02:28 UTC728 viewsread 8 August 2026

# Alhaitham 下一版本更新 Alhaitham App Proxy 0.1 (20) 已发布 https://testflight.apple.com/join/KVmQFXAA Alhaitham DNS Proxy 0.4 (81) 已发布 https://testflight.apple.com/join/r8yjKr4P Alhaitham Dashboard 0.4 (169) 已发布 https://testflight.apple.com/join/pR1xwCfB ## 重要提示 1. Dashboard 升级了服务器配置与凭据储存结构。升级后,旧服务器配置及对应凭据会被清理,需要重新添加服务器。 2. Shared Store 数据模型有较大调整。如果旧数据库无法打开,请在“设置 → 开发者 → Shared Store Management”中手动重建。重建会删除原有记录。 ## 公共更新 …

18 Jul 2026, 03:42 UTC569 viewsread 8 August 2026

Alhaitham App Proxy 0.1 () 已发布 Alhaitham DNS Proxy 0.4 () 已发布 Alhaitham Dashboard 0.4 (167) 已发布 https://testflight.apple.com/join/pR1xwCfB ## 主要更新 本次更新相对 main 基线累计 125 次提交,重点是重构 Dashboard 的远程服务管理,并完善 App Proxy、DNS 与事务详情的稳定性。 ## Dashboard ### 远程服务器管理重构 - 全面更新 Clash、Stash 与 Surge 的远程服务配置。 - 支持为同一服务配置多个有序 Endpoint,并在连接失败时自动切换。 - Surge 现同时使用 HTTP 与 TCP 通道,提升策略、DNS 与流量数据的获取稳定性。 - API 凭据改由 Keychain 保存;启动时会自动清理已删除服务器…

Signed 抗倒伏小麦

10 Jul 2026, 02:53 UTC565 viewsread 8 August 2026

Alhaitham App Proxy 0.1 (13) 已发布 https://testflight.apple.com/join/KVmQFXAA Alhaitham DNS Proxy 0.3 (67) 已发布 https://testflight.apple.com/join/r8yjKr4P Alhaitham Dashboard 0.4 (155) 已发布 https://testflight.apple.com/join/pR1xwCfB ## 主要更新 本次更新距离 main 基线约 26 天,累计 410 次提交。更新重点不是单纯增加页面,而是围绕 App Proxy Flow、事务体系、应用模型、Forwarder 调度与 SwiftData 写入边界进行了一轮完整重构。 ## 公共更新 ### Flow / Policy / Transaction 数据结构重构 - 统一 Flow 基础模型,回收…

Signed 抗倒伏小麦

13 Jun 2026, 04:53 UTC838 views8 reactionsread 8 August 2026

本项目不会优先实现 SS、V2Ray、Trojan 等传统代理协议。应用代理(App Proxy Provider)的接管优先级高于包隧道(Packet Tunnel Provider),可以与传统 VPN 同时启用,并位于其上游。因此,本项目更适合用来尝试解决传统 VPN 当前不涉及、或很难处理的问题;至于下游继续使用哪种 VPN 或代理协议,并不是本项目优先关心的重点。 如果后续确实需要完整的代理转发能力,本项目更可能会另行推出一款基于包隧道(Packet Tunnel Provider)的专用代理工具,而不是把传统代理协议优先塞进当前应用代理架构里。

❤8

Signed 抗倒伏小麦

13 Jun 2026, 04:45 UTC685 views1 reactionsread 8 August 2026

# 本次更新说明 本次更新距离上次发布已经过去约半个月,期间累计接近 400 次提交。更新规模较大,重点不只是增加页面或修复显示问题,而是对底层架构、数据处理方式和持久化方式做了一轮完整调整。 本轮更新确立了新的三层数据储存架构:流(Flow)、事务(Transaction,相当于 Surge 的请求 Request 或 Clash 的连接 Connection)与应用模型。流(Flow)负责描述网络连接与传输过程,事务(Transaction)负责记录从流量中识别、拼接并还原出的请求/响应,而应用模型则用于保存那些需要长期复用、或者脱离单个流与单个事务后依然有价值的数据。 同时,本次更新完全分离了数据库读写与数据处理线程。数据处理过程不再直接被数据库操作拖慢,运行期数据会通过管理器、写入队列与节流保存机制持续写回。实测在当前设计下,请求记录模式可以长期保持开启:系统会持续嗅探、识别、拼接并保存每一个请求,包括 UDP 流…

❤1

Signed 抗倒伏小麦

13 Jun 2026, 04:22 UTC532 views1 reactionsread 8 August 2026

# Alhaitham 仪表盘(Dashboard)0.4 (149) https://testflight.apple.com/join/pR1xwCfB ## 新增:全部事务(All Transaction)入口 - 新增全部事务入口 - 接入 HTTP、DNS、应用层(AppLayer)事务的独立页面 ## 新增:聚合外观设置入口 - 外观设置入口合并为全部流(All Flow)、DNS、全部事务(All Transaction)、DNS 策略(DNS Policy)等聚合入口 - 减少应用流(App Flow)、DNS 流(DNS Flow)、V1 事务分散入口 ## 改进:全部事务(All Transaction)外观设置 - 全部事务外观设置支持 V1 应用层(AppLayer)事务 - 在可用系统上显示 HTTP、DNS 等事务类型的预览与分段设置 ## 改进:Surge / Clash / Stash …

❤1

Signed 抗倒伏小麦

13 Jun 2026, 04:22 UTC507 viewsread 8 August 2026

# Alhaitham DNS 代理(DNS Proxy)0.3 (53) https://testflight.apple.com/join/r8yjKr4P ## 新增:事务聚焦页 - 恢复并改进事务聚焦页 - 现在可以查看 DNS 流(DNS Flow)、DNS 事务与 DNS 模型数据 ## 新增:设置入口 - 设置页新增统一事务外观设置入口 - 设置页新增事务缓存清理入口 ## 改进:DNS 缓存 - 改进 DNS 缓存查询与命中逻辑 - 修复缓存响应 ID、缓存 payload 回读与服务器选择相关问题 ## 改进:DNS 报文解析 - 改进 DNS 报文解析 - 修复压缩指针截断、循环指针、DNS over TCP 解析模式等问题 ## 修复:DNS 解析失败记录缺失 - DNS 解析失败时也会记录兜底(Fallback)事务 - 方便后续排查异常请求

Signed 抗倒伏小麦

13 Jun 2026, 04:21 UTC402 viewsread 8 August 2026

# Alhaitham 应用代理(App Proxy)0.1 (3) ## 新增:应用层(AppLayer)事务记录 - 直连(DIRECT)转发下可以记录 HTTP、DNS 以及无法识别协议的兜底(Fallback)事务 - 应用层(AppLayer)事务会从原始 TCP/UDP 流量中分析、识别、拼接并还原出上层协议请求/响应 - 例如 HTTP 事务会还原为具体的 HTTP 请求/响应,DNS 事务会还原为具体的 DNS 查询/响应 ## 新增:聚焦页面 - 新增应用流(App Flow)、事务(Transaction)、HTTP 聚焦页面 - 可以在应用代理(App Proxy)内直接查看流量、事务与 HTTP 数据 ## 新增:设置入口 - 设置页新增统一事务外观设置入口 - 设置页新增事务缓存清理入口 ## 改进:转发管线 - 重构转发管线,统一 TCP/UDP 转发入口 - 修复部分连接释放、等待就绪与响应…

Signed 抗倒伏小麦

13 Jun 2026, 04:21 UTC465 viewsread 8 August 2026

Alhaitham App Proxy 0.1 (3) 已发布 Alhaitham DNS Proxy 0.3 (53) 已发布 https://testflight.apple.com/join/r8yjKr4P Alhaitham Dashboard 0.4 (149) 已发布 https://testflight.apple.com/join/pR1xwCfB # 公共更新 ## 新增:事务(Transaction)体系 - 相当于 Surge 的请求 Request 或 Clash 的连接 Connection - 支持统一查看全部事务,也可以分别查看 HTTP 事务、DNS 事务与应用层(AppLayer)事务 ## 新增:应用层(AppLayer)事务识别 - 应用层(AppLayer)事务是从原始 TCP/UDP 流量中分析、识别、拼接并还原出的上层协议请求/响应 - HTTP 事务会还原为具体的 HTTP…

Signed 抗倒伏小麦

27 May 2026, 03:10 UTC672 views1 reactionsread 8 August 2026

Alhaitham DNS Proxy 0.2 (50)已发布 https://testflight.apple.com/join/r8yjKr4P Alhaitham Dashboard 0.4 (146)已发布 https://testflight.apple.com/join/pR1xwCfB 公共更新: 1. 流(Flow)读写统计数据(字节数)现在正常回写数据库,在流(Flow)的相关视图可以看到读写的字节数 2. 流管理器现在采用延迟写入,每 200 ms 保存一次更新,以节省 CPU 使用、降低磁盘读写频率 3. 流(Flow)命中的默认策略现在正确回写 App Proxy 更新: 1. 新增 PASS (Passthrough/穿透)策略,此模式下不经过任何处理引擎,原样转发数据 - 与 DIRECT (直连)策略是不同的,DIRECT 依旧会经过处理引擎识别解析协议及内容

❤1

Signed 抗倒伏小麦

25 May 2026, 07:45 UTC676 views2 reactionsread 8 August 2026
Photo

Alhaitham DNS Proxy 0.2 (49)已发布 https://testflight.apple.com/join/r8yjKr4P Alhaitham Dashboard 0.4 (145)已发布 https://testflight.apple.com/join/pR1xwCfB 公共更新: 1. 流(Flow)不再储存匹配到的规则快照,而是直接连接到匹配到的策略(Policy) 2. 改进了策略(Policy)与流(Flow)视图 - 长按流(Flow)的行,会展开显示流与对应策略(Policy)的详情 - 流(Flow)的详情页面也可以直接跳转到匹配的策略页面 - 分流页面逻辑优化,提升加载速度 3. 更新更多翻译文本与翻译方式 App Proxy 更新: 1. Extension 启动逻辑与 DNS Proxy Extension 对齐 已知问题: 1. 流(Flow)如果没有匹配到…

❤2

Signed 抗倒伏小麦

Showing the 12 most recent of 19 posts we hold for @GetSomeTriticumChannel. 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.

Cite this entry

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 20 November 2026 — this entry's latest reading, not the date you are reading this.

“🌾 整点小麦:iOS/macOS App” (@GetSomeTriticumChannel), 1,054 subscribers as measured 20 November 2026. Telegram Register, tgregister.com/channel/GetSomeTriticumChannel.

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.