🔴版本 v1.4.6已经发了,建议所有人立即升级!
🤡11

Channel
@dujiaoshuka
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
10,185subscribers
+1,056 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001326502387 |
|---|---|
| Type | Channel |
| Username | @dujiaoshuka |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/dujiaoshuka |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 55% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 16:00 | 10,185 | +59 |
| 16 Sept 2026, 11:37 | 10,126 | +72 |
| 14 Sept 2026, 12:36 | 10,054 | +22 |
| 13 Sept 2026, 01:58 | 10,032 | +80 |
| 9 Sept 2026, 00:56 | 9,952 | +134 |
| 3 Sept 2026, 20:55 | 9,818 | +103 |
| 31 Aug 2026, 08:23 | 9,715 | +59 |
| 28 Aug 2026, 08:15 | 9,656 | +65 |
| 25 Aug 2026, 17:05 | 9,591 | +70 |
| 22 Aug 2026, 06:34 | 9,521 | +74 |
| 18 Aug 2026, 18:34 | 9,447 | +94 |
| 15 Aug 2026, 09:59 | 9,353 | +93 |
| 11 Aug 2026, 17:22 | 9,260 | +112 |
| 8 Aug 2026, 08:18 | 9,148 | +19 |
| 7 Aug 2026, 09:15 | 9,129 | first reading |
14 posts held, back to 23 June 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 33 pages of 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 2 of 3 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 27 August 2026 |
|---|---|
| Posts held | 14 (23 June 2026 – 27 August 2026) |
| Views total | 4,980 |
| Reactions total | 15 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Aug 2026, 05:39 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.
296 reactions across 12 posts, in 12 distinct kinds. The most used accounts for 28.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 85 | 28.7% | |
| 👍 | 62 | 20.9% | |
| 🔥 | 35 | 11.8% | |
| 🤡 | 32 | 10.8% | |
| 🎉 | 31 | 10.5% | |
| 😁 | 26 | 8.78% | |
| 😍 | 6 | 2.03% | |
| 🥰 | 6 | 2.03% | |
| 💋 | 4 | 1.35% | |
| 🏆 | 3 | 1.01% | |
| 👎 | 3 | 1.01% | |
| 🤩 | 3 | 1.01% |
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 13 of the 14 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 296 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 23 June 2026 to 27 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.
🔴版本 v1.4.6已经发了,建议所有人立即升级!
🤡11
刚刚更新v1.4.5的重新再更新一下,修复了一个问题~ 下午的v1.4.5已经撤回并重新打包了📦,建议所有人都升级
#版本发布 🎉Dujiao-Next v1.4.5 正式发布 ━━━━━━━━━━━━━━ 更新日志: https://github.com/dujiao-next/dujiao-next/releases/tag/v1.4.5 ━━━━━━━━━━━━━━ ✅顶级供应商|官方合作品牌 vmrack.net - 全球自动化云基础设施服务商 提供先进的云服务器、裸金属、CDN、媒体处理、对象存储和网络解决方案,助力企业轻松上云 🏆铂金赞助商鸣谢: ---------------------------- - [汇沣支付- 实时结算] - [Feepay - 稳定支付接口] - [AcPay - 稳定D0支付] - [牛牛支付 - 超级无敌牛逼代收] - [赛博支付-发卡收款好帮手] - [CEOACC.COM | 源头海外社交账号批发] - [NiuProxy | 全球动态住宅源头厂商 0.3$/GB] - [高质量…
❤2👍2
#版本发布 🎉Dujiao-Next v1.4.3 正式发布 ━━━━━━━━━━━━━━ 更新日志: 1. 增强订单风控策略,灵活调整策略防止“占库存攻击” 2. 优化修复支付功能和页面相关问题 3. 去除订单取消邮件通知,减少用户打扰 4. 修复部分已知的bug ━━━━━━━━━━━━━━ ✅顶级供应商|官方合作品牌 vmrack.net - 全球自动化云基础设施服务商 提供先进的云服务器、裸金属、CDN、媒体处理、对象存储和网络解决方案,助力企业轻松上云 🏆铂金赞助商鸣谢: ---------------------------- - [汇沣支付- 实时结算] - [Feepay - 稳定支付接口] - [AcPay - 稳定D0支付] - [牛牛支付 - 超级无敌牛逼代收] - [赛博支付-发卡收款好帮手] - [CEOACC.COM | 源头海外社交账号批发] - [NiuProxy | 全球动态住宅源头厂…
🎉3🥰3😍3🔥2😁1
#恰饭通知 📣dujiao-next 作者开店了! 写了这么久的 dujiao-next,这次终于轮到我自己用它做生意了。 以前一直在为dujiao-next做功能更新,但是从头到位都没有认真去使用过它, 说来好笑,自己是作者,却从来没运营过自己的系统。 有时候一些新功能和想法都是靠自己灵感突然涌动而去实现的, 但是自己不深度使用也无法完全知晓系统有哪些缺陷,功能或体验上还有哪些地方值得打磨。 老早就计划自己运营一个站点,但是激情总是容易被拖延症打败~😂 所以~ 这次想真真正正自己独立运营一个品牌站,所有商品从进货到上架流程完全由自己亲身实践和把控。 一来可以更好的打磨Dujiao-Next,二来也可以恰点小饭,一举两得!win win! 再说了,一些人天天吆喝怕Dujiao-Next有漏洞被0元购, 现在作者跟你用一样的系统/一样的代码,就算出漏洞也是作者先损失,你还怕什么?🙂 ————————— 下面介…
👍6😍3❤2😁2🏆1
#合作伙伴推送 ✅️老朋友VMrack经过漫长的硬件升级和架构扩容,终于又回来了~ 这次依旧跟独角达成了合作款机型,配置如下: 区域:洛杉矶 配置:1vCPU|1GB内存|20GB系统盘 带宽类型:三网优化 基础IPv4数量:1 价格:76美元/年 闪购链接:👉点我购买 由于AI泡沫和全球硬件暴涨的原因,这个价格的确相较于之前涨幅了一些, 我认为优势主要还是在线路上,价格大家就见仁见智了。 我个人就这个定价跟VMrack官方激烈的battle了几轮, 但这已经是目前争取到最优的价格了。 如果大家以后有建站/云服务器方面的需求,也可以考虑一下VMrack。
🤡7❤3🔥3🏆2👍2
#瞎哔哔 #安全预警 跟一位群友聊到了一个关于 Bepusdt/Epusdt/Tokenpay等虚拟币支付网关的一种“中间人攻击缺陷”, 这里把攻击原理和预防手段给大家分享一下。 攻击原理: 第一个人A开入金100的充值单, 第二个人B同时开100的充值单, 由于市面上所有开源虚拟币支付的区分订单手段都是通过金额差异区分法, 所以第一个人A的支付金额是100,第二个人B的支付金额为100.01, 然后第二个人B他故意只支付100,然后会入到第一个人A的入金订单, 这时候第二个人B来找管理员说充值没到账,会提供入金截图,哈希等凭证, 让管理员手动入金补单, 然后等管理员给B加进去余额,发现第一个人A已经用完了刚才白得的100。 这时候管理员又没100%的证据确定这两个人是同一个人,只能吃哑巴亏,这就是利用了社会工程学加中间人攻击。 预防手段: 1. 再有人要求补单之前,拿着他的hash和链上记录去后台扫一眼有没有临近金…
😁3🎉2💋2🤩2❤1
🎉 Dujiao-Next v1.4.0 正式发布 本次是架构级更新:两个前端内嵌进后端二进制,从「三端分离」变成单进程、单端口、单域名交付。同时对支付链路做了一轮完整的安全加固。 ━━━━━━━━━━━━━━ 📦 单二进制交付 • 用户前台 + 管理后台 + API 打进一个二进制,只需一个进程、一个端口、一个域名 • 容器数从 4~5 个降到 2~3 个,不再需要独立前端容器与 nginx • 后台入口改为自定义路径 web.admin_path,无需再单独解析一个域名 • 镜像更名为 dujiaonext/dujiao-next(旧名 dujiaonext/api 仍作过渡别名同步推送) • 发布产物精简为单个 dujiao-next_*.tar.gz 🔐 支付安全加固 • 支付回调强制校验金额、币种、订单号、渠道与签名,缺失不再默认可信 • 回调入账全程行锁 + 事务,重复、乱序或并发回调不会重复扣库存、重复充值…
👍13❤6💋2👎1🤩1
https://t.me/simonxbb 🙂开了一个个人频道, “爷们娘们,能不能走个面儿。独角群这么多人,您受累,把第一波关注点起来,咱就有了!”
#开发动向 😂由于前期next快速迭代和功能更新,代码质量和结构早已混乱和臃肿不堪, 目前正在做新一轮重构,将代码和结构目录以及功能重新进行梳理和划分, 这是一个比较重大的改动,所以目前暂时不会接受Github仓库PR和新功能开发。 下个版本开始,前后台不再需要独立部署,思来想去现在的部署方式的确过于麻烦和不友好, 以后前端静态文件也将统一使用golang的embed进行打包构建。 🙂简而言之: 以后,你只需要一个二进制文件即可运行整个服务,不用再去分别部署api/admin/user, 不排除后续会支持在后台“在线更新”的方式, 当然为了安全起见, 更新方式采用自动下载github的release方式,不会由独角这边控制下载源~
❤38🔥30🎉26👍23😁20
#小提示 ⚠️ Telegram短链域名 t.me 在没有任何预兆的情况下被突然暂停解析,原因未知! t.me 域名外链在外部浏览器已经无法正常打开,客户端内深链不受影响。 请各位暂时使用 telegram.me 域名替换 t.me 以保障部分业务正常运行!
🥰3👍2👎1
剧终 请各位站长安心使用,顺便提醒一下做好安全防范,不然就算Next后台做了许多的安全设计也防不住呆! 还有当事人已经向我道歉了而且也不是当事人出口成脏,所以这件事就过去了!
🤡11❤3👍2
Showing the 12 most recent of 14 posts we hold for @dujiaoshuka. 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.
@dujiaoshuka edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“独角Next <Dujiao-Next>” (@dujiaoshuka), 10,185 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/dujiaoshuka.
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.