via 独享
🥰2
Signed PA 733

Channel
@tech_tips_733
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
304subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002801584061 |
|---|---|
| Type | Channel |
| Username | @tech_tips_733 |
| Description | 733 的个人频道 主推:AI 新闻、AI 技巧、程序员梗图/乐子 |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/tech_tips_733 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 07:50 | 304 | no change |
| 7 Aug 2026, 23:48 | 304 | first reading |
20 posts held, back to 18 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 18 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 20 (18 July 2026 – 8 August 2026) |
| Views total | 3,498 |
| Reactions total | 109 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 07:50 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 8 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.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
109 reactions across 17 posts, in 10 distinct kinds. The most used accounts for 69.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😁 | 76 | 69.7% | |
| 💔 | 6 | 5.50% | |
| 👍 | 5 | 4.59% | |
| 😭 | 4 | 3.67% | |
| 😱 | 4 | 3.67% | |
| 🤩 | 4 | 3.67% | |
| 😨 | 3 | 2.75% | |
| 🤯 | 3 | 2.75% | |
| 🥰 | 3 | 2.75% | |
| 👏 | 1 | 0.917% |
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 18 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 109reactions 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 18 July 2026 to 8 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.
via 独享
🥰2
Signed PA 733
临时缓解措施:打开 backend mode(禁用注册+其他限制)
Signed PA 733
sub2api 曝 OAuth 高危漏洞,仅凭邮箱即可接管账户 sub2api v0.1.171 及之前版本存在一个 CVSS 8.8 的高危 OAuth 账户接管漏洞。攻击者仅需知道受害者注册邮箱,无需密码或验证码、无需用户交互,即可通过接口将自己的 OAuth 身份绑定到受害者账户,完全控制其 API 密钥、账单余额与订阅配额。 攻击者利用 pending session 流程中 existingUser 分支不校验密码和验证码的缺陷,将目标用户 ID 设为受害者后完成 OAuth 身份绑定。此后攻击者每次 OAuth 登录均会解析为受害者账户。 Github Issues 🌸 在花频道 · 茶馆水群 · 投稿通道
Signed PA 733
艹,梁神 牛的,梁圣 可以的,梁叔 怎么回事,梁子 ← 你现在在这! 你tm是人吗,梁西匹
😁8
Signed PA 733
我不行了 你们都这么写路由的吗
😁9
Signed PA 733
陪伴我几年的 ChatGPT 账号死了😭
😱4😨3
Signed PA 733
RTOS 要点:叮咚鸡(指等中断),大狗叫(看门狗),一段一段待一段(指优先级调度)
😁1
Signed PA 733
让Codex向你呈递公文并接受批示圈阅 开源地址 https://github.com/4thfever/codex-document-mode 麻烦多给给三连和star吧!球球了! @肥桥今天吃什么: 发布视频 播放量:1.48万 弹幕:4 评论:69 点赞:468 投币:76 收藏:518 转发:386 发布日期:2026-07-26 12:34:22 上传日期:2026-07-26 12:34:23
🤯3😁3
Signed PA 733
GG卡止损
👍4
Signed PA 733
Photo, posted without a caption
😭4😁3
Signed PA 733
#梁文峰剪断kimi跨境光纤阻止K3发布# #因为2.8T模型太大导致moonshot上传时被中国电信判定为pcdn掐断网线# 【跨境流量使用提醒】尊敬的月之暗面,您的跨境流量包已用尽。已开始使用国际漫游标准资费,每3MB收3元,每天(按北京时间为准)30元封顶,流量畅享,达量限速,跨国家/地区使用分别收费,请留意使用。 破案了,原来只是忘记点 convert to public 了 #月之暗面称deepseek写的自动public脚本故障导致开源延期# ref1 ref2
😁8
Signed PA 733
Photo, posted without a caption
😁7
Signed PA 733
Showing the 12 most recent of 20 posts we hold for @tech_tips_733. 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 — 1,000,018 of 1,169,250entries 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.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“733 Tech Tips (Public)” (@tech_tips_733), 304 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/tech_tips_733.
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.