赶紧414

Channel
是达达利亚的🐶
@Genshin_Impact0016
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
7subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001697012816 |
|---|---|
| Type | Channel |
| Username | @Genshin_Impact0016 |
| Created | Between 1 December 2021 and 31 March 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Genshin_Impact0016 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 17:01 | 7 | no change |
| 7 Aug 2026, 06:10 | 7 | first reading |
Engagement
19 posts held, back to 31 March 2022 — 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 22 April 2023. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 5
- Videos
- 3
- Links
- 14
Lifetime counters from Telegram’s own channel header, read 12 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.
- Video runtime
- 1m 47s
- Average length
- 54s
Measured directly from 2 videos 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.
Recent posts
⬆️surge、shdowrocket 模块: https://github.com/NobyDa/Script/raw/master/Surge/Module/TestFlightAccount.sgmodule
新增: TestFlight账户管理脚本 主要功能: 1. 自动存储多个TestFlight账户,并自动合并APP列表,避免切换账户。 2. 账户内单个测试版APP允许多方共享: - 导出:点击测试版APP -> 底部开发者许可协议 -> 复制密钥并分享给对方 - 导入:TestFlight 右上角"兑换" -> 粘贴密钥 -> 弹出保存成功通知后刷新APP列表 - 多方共享为实验性功能,双方都需要使用该脚本; 该功能主要解决某些APP的TF名额稀缺的问题 请注意,该脚本已经与"TF区域限制解除脚本"合并,如需使用该脚本请务必禁用它,否则可能出现APP安装异常
https://c1n.cn/pKTvc ⬅️机场我推荐这家专线套餐
🎉【v0.9.3 发布】Hi, Gridea 的朋友们,久等了~ 增加 HTTP 代理、Netlify 部署支持、Gitee 部署支持等。 # ⚠️ 重要更新 调整 output 文件夹目录位置到 ~/.gridea/output 文件夹,与站点源文件夹分离,站点源文件夹中的 output 文件夹可自行删除。`v0.9.3` 及后续版本将不再使用。 额外带来的变更为 Git 提交记录仅保留最新同步的一条。(如果对提交记录有需求的用户请谨慎升级。) 为什么要变更 output 目录? 目的是为了和博客源文件夹分离开,避免使用 OneDrive 等同步工具同步时,把 output 文件夹以及里面的 .git 文件夹一并同步,从而导致遇到同步问题或大量文件变更情况。 # 新增 - 🌟 Github Pages 远程同步支持配置本地网络代理。感谢 @wherelse - 支持部署到 Netlify。 - 支持部署到 Git…
#BoxJs v0.12.0 【版本升级】 当发现有新版本时,更新提示页面顶部会显示“立即更新”按钮 1. 该按钮会跳转至 App 并触发资源更新 2. 更新完成后,回到 BoxJs 按提示刷新页面即可完成更新 注意:需要更新至 TF (TestFlight) 版本 注意:需要更新至 TF (TestFlight) 版本 注意:需要更新至 TF (TestFlight) 版本 【安装&升级】 全新的安装&升级方式: Quantumult X TF: v1.0.29 (670)+: 一键安装BoxJs & 一键升级BoxJs Loon TF: v2.1.19 (385)+: 一键安装BoxJs & 一键升级BoxJs Shadowrocket TF: v2.2.8 (1658)+: 一键安装BoxJs & 一键升级BoxJs 如果没有 TF 可以查看:B…
https://chavyleung.gitbook.io/boxjs/
可能是交互做得最好的终端 https://www.warp.dev/
tf build 1634 之后可用
#QX #Surge #Loon #Clash #Stash #ShadowRocket 【Sub-Store x ShadowRocket】 Sub-Store 现已完整支持 ShadowRocket,请使用模块。 🌟 GitHub
https://futuristic-starflower-868.notion.site/Shadowrocket-0bd927fbf26b442e96c2ab53ec180d17
https://mp.weixin.qq.com/s/yEL6PGNkWqtJGTkstlce9Q
Showing the 12 most recent of 19 posts we hold for @Genshin_Impact0016. 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.
Forward network
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.
Mentions
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@Genshin_Impact0016 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 13 August 2026 – 13 August 2026
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“是达达利亚的🐶” (@Genshin_Impact0016), 7 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Genshin_Impact0016.
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.