Channel
@dogki
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
27subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001633917596 |
|---|---|
| Type | Channel |
| Username | @dogki |
| Description | 嘘🧐频道主不对本频道的言论负责！内容皆来自网络。 |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/dogki |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 07:46 | 27 | no change |
| 7 Aug 2026, 20:55 | 27 | first reading |
18 posts held, back to 22 August 2023 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 16 January 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 11 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.
uTLS 新发现漏洞可被GFW利用高效识别代理流量 继指纹泄露漏洞之后，用于模拟真实浏览器指纹的 uTLS 库被发现还存在另外一个严重漏洞。来自 acgdaily 的研究人员发现 uTLS 在模拟 Chrome/Edge 浏览器时 TLS 握手包长度填充（Padding）缺失。 当一个真实浏览器发送的 ClientHello 数据包长度小于 512 字节，浏览器会添加一段“填充（Padding）”数据，将包的大小强行撑到至少 512 字节，这样做的目的是防止部分防火墙和服务器拒绝数据包导致僵化。但 uTLS 在模拟时遗漏了“填充”这一步骤，因此会发送一个在真实 Chrome 环境下“不可能存在”的小包。这让 GFW 仅需根据数据包的大小，就能断定该数据包是伪造的。此 BUG 会导致 uTLS Chrome 120 指纹纯被动识别。uTLS 官方已在最新的 v1.8.2 版本中修复了此漏洞。 影响范围 (Chrome 120…
很多时候问题的根源，不在于立场，而在于态度。 态度相同，可能演化出完全不同的观点和立场，这并不奇怪，可以讨论，可以辩论，可以互相批评，无非是观点不同，方法论不同，优先级不同。甚至有的时候言辞激烈些，也不甚要紧。兴许偶尔还会被错误的信息蒙蔽了双眼，被利用了愤怒与关切，在这个时代，也很普遍，甚至不在少数。 但总归，大家是朴素的，希望你的人类同胞们好的，希望他们过得安全、幸福、自在。 但有另一小撮人，早已没有朴素的是非观了。他们除了一张嘴外，别无长处，兴许在经济上发达些，搬弄是非的能力上出色些，却对辛苦努力工作，追求美好生活的普通人们有着极大的恶意。时常说些恶劣的话出来，咒人发狠，那就是极其坏的事情了。 于是便见得群情澎湃，许多的街谈巷议，竟将这些人打了下去，搅动了另一些人的美梦。这群人自然是要大哗的，普通人们竟能让他们的威风扫光，不仅是在言论上打倒在地，还要再踏上几只脚，世间竟有如此反常之事？ 非也。这一小撮人兴许借着早几…
https://www.quji.org/archives/8654
不知道真假呢🤮
https://www.v2ex.com/t/1134428
https://t.me/xhqcankao/20201
笑死😂
中文太难了
李克强的去世好突然，这么高的领导为什么医疗保障这么差劲？难过😢
刚才才看到除夕不放假的消息，作为低端人口，我绷不住了，除夕都不放假了，任何的解释都是无力和苍白的，只想说一句，草泥马！
有没有勇士冲一下😂
HeyGen AI视频翻译效果惊艳全场 口型完美，卡点和嘴型都对的上。声音克隆稍有缺陷但也很好了，毕竟HeyGen只通过40秒的视频来克隆音频。如果刻意对比原视频，情感还原度稍有欠缺。 ⚜️ 付费方案：HeyGen视频翻译功能全套解决 地址： labs.heygen.com/video-translate ⚜️ 开源方案： - 语音转文字：whisper - 文字翻译：GPT - 声音克隆+生成音频：so-vits-svc - 生成符合音频的嘴型视频：GeneFace++ 🖥 github.com/svc-develop-team/so-vits-svc 🖥 github.com/yerfor/GeneFace 期待各种应用场景的出现，YouTube视频分分钟转成全球各种语言，受众立马翻几倍。有朝一日，语言成为人们沟通障碍的情况终会消失。 -- 更多详情
Showing the 12 most recent of 18 posts we hold for @dogki. 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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“小声说话😷” (@dogki), 27 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/dogki.
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.