Channel
@simonxbb
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
296subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004291112014 |
|---|---|
| Type | Channel |
| Username | @simonxbb |
| Description | Dujiao-Next(原独角数卡、EPUSDT)等作者 Assimon 个人频道， 频道目的： - 1.专门用于发布作者个人情绪化或不经过大脑思考的表达 - 2.开展一些业务用于“补贴家用”或”圈米“ - 3.分享一些技术前沿知识或稀奇古怪的东西 - 4.任何不适用于在官方Dujiao-Next主频道发布的内容 |
| Created | Between 1 May 2026 and 24 July 2026— 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/simonxbb |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 08:04 | 296 | no change |
| 7 Aug 2026, 09:15 | 296 | first reading |
9 posts held, back to 24 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 6 of 9 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 4 August 2026 |
|---|---|
| Posts held | 9 (24 July 2026 – 4 August 2026) |
| Views total | 8,746 |
| Reactions total | 19 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 08:04 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.
19 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 68.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 13 | 68.4% | |
| 👍 | 5 | 26.3% | |
| 👏 | 1 | 5.26% |
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 6 of the 9 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 19reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 24 July 2026 to 4 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.
#恰饭通知 📣dujiao-next 作者开店了！ 写了这么久的 dujiao-next，这次终于轮到我自己用它做生意了。 以前一直在为dujiao-next做功能更新，但是从头到位都没有认真去使用过它， 说来好笑，自己是作者，却从来没运营过自己的系统。 有时候一些新功能和想法都是靠自己灵感突然涌动而去实现的， 但是自己不深度使用也无法完全知晓系统有哪些缺陷，功能或体验上还有哪些地方值得打磨。 老早就计划自己运营一个站点，但是激情总是容易被拖延症打败～😂 所以～ 这次想真真正正自己独立运营一个品牌站，所有商品从进货到上架流程完全由自己亲身实践和把控。 一来可以更好的打磨Dujiao-Next，二来也可以恰点小饭，一举两得！win win！ 再说了，一些人天天吆喝怕Dujiao-Next有漏洞被0元购， 现在作者跟你用一样的系统/一样的代码，就算出漏洞也是作者先损失，你还怕什么？🙂 ————————— 下面介…
#快讯 IOS似乎已经全球下架了Telegram，原因暂不清楚。 各位苹果手机用户可以暂时先将图中开关关闭掉，防止卸载后无法再下载 ————————— 2026-08-04 10:30 已恢复，商店可以搜索到了
#要闻 DeepSeek-V4-Flash正式版发布！ 在核心测试中，DeepSeek-V4-Flash正式版的表现已经超越了GLM5.2，并进一步逼近Claude Code Opus4.8。 关键是价格还跟之前一样，输入为1元/百万Token，输出为2元/百万Token！WOW！！ 这还只是Flash版本，Pro版本还没发布哦～ 天下苦A/久矣，希望这次“梁叔叔”能干翻OA两家！ 官方消息源： https://x.com/deepseek_ai/status/2083084415157022911?s=20
#瞎哔哔 #安全预警 跟一位群友聊到了一个关于 Bepusdt/Epusdt/Tokenpay等虚拟币支付网关的一种“中间人攻击缺陷”， 这里把攻击原理和预防手段给大家分享一下。 攻击原理： 第一个人A开入金100的充值单， 第二个人B同时开100的充值单， 由于市面上所有开源虚拟币支付的区分订单手段都是通过金额差异区分法， 所以第一个人A的支付金额是100，第二个人B的支付金额为100.01， 然后第二个人B他故意只支付100，然后会入到第一个人A的入金订单， 这时候第二个人B来找管理员说充值没到账，会提供入金截图，哈希等凭证， 让管理员手动入金补单， 然后等管理员给B加进去余额，发现第一个人A已经用完了刚才白得的100。 这时候管理员又没100%的证据确定这两个人是同一个人，只能吃哑巴亏，这就是利用了社会工程学加中间人攻击。 预防手段： 1. 再有人要求补单之前，拿着他的hash和链上记录去后台扫一眼有没有临近金…
❤2👍1
最近的AI热让所有博主都在推GiffGaff的手机卡，经常刷到X上大批量卖卡的，我就知道这玩意离凉凉不远了。 希望后续GiffGaff官方政策会放宽，不然我这个5年老用户也难受了
英国手机卡 Giffgaff 正对长期漫游用户采取行动 根据NS论坛的消息，Giffgaff 手机卡的运营商正在关停大量用户的服务。据停权用户反馈，他们收到了如下内容的邮件： 根据我们的条款和条件，我们的服务主要面向英国境内用户，漫游服务仅适用于短期旅行。鉴于您的使用模式表明您在英国境外长期或永久使用我们的服务，您的账户已不再符合服务资格要求。因此，您的服务将很快终止，所有相关访问权限也将停止。 Giffgaff 是一个英国移动电话公司，大量中国用户持有该公司发行的实体卡，常被用于注册海外服务。今年1月，Giffgaff 已采取过一次规模相对较小的封号行动，但恐慌情绪迅速蔓延开来。Giffgaff 和许多用户的重要服务有关联，任何风吹草动都令人惴惴不安。当前依然无法评估此次关停服务的影响规模。建议有条件的用户换绑其它运营商的手机号。 [消息等级 Level C2 · 简要]
👍2
#科技分享 #IOS修改定位 之前我在寻求解决apple watch解锁心电图、睡眠呼吸暂停监测等功能， 因为这个功能在中国大陆还未开放，所以大家的苹果手表并不是“满血”的。 但是苹果非常鸡贼，这个功能你只要去一次大陆之外的地方就能自动解锁， 所以我去闲鱼上寻找了一圈解决方案，但是大部分都需要你提供apple id或者登录卖家提供的apple id才能解锁， 这样非常的不安全，等于把整个设备权限交给商家，所以我放弃了。 大家都知道对于IOS修改定位是非常麻烦的，要么“越狱”，要么使用物理设备“尾插”等， 直到某一天我在X刷到了一个叫wloc的项目，无需越狱和尾插就能修改定位， 然后我就在想能不能用于解锁apple watch的功能，爱于折腾的我也是抱着试一试的态度， 不出意外我成功了，在将位置信息修改为洛杉矶以后，我的apple watch成功解锁所有功能。 这里如果大家有ios修改定位的需求，可以试试这个项目，无需越…
👍2❤1
#瞎哔哔 作为一个小项目的开源作者，几乎从早期的“独角数卡”开始，时不时就会在群里听到 “独角是不是有漏洞” “独角被0元购了” “xxx有漏洞被黑了” 这些话题，几乎让我的耳朵快要起茧子了。 从最开始胆战心惊帮他们排查，询问分析，追溯问题，到后面逐渐开始淡漠，甚至反感这个话题。 为什么？ 因为经过很多次排查确认，发现大部分问题都是由于使用者自己的问题导致的，他们不外乎都会出现以下的情况： 1.贪小便宜，找野鸡代搭建，甚至连服务器和域名都要求对方包了 2.安装第三方破解版软件或一键脚本导致被种植木马后门 3.使用弱口令和简易密码 4.不关注任何官方渠道关于漏洞和预警消息的通知 5.啥都不懂就截图暴露，例如截图里包含你的支付密钥等信息 6.自己让ai瞎改一通，不做任何审计就上线 情况太多太多根本无法列举完，说到底就是这群人对自己的数字资产安全冷漠和不上心导致的。 你为什么不能像保护你钱包私钥一样去保护你的系统安全呢？…
❤7👏1
📱频道简介 Dujiao-Next(原独角数卡、EPUSDT)等作者 Assimon 个人频道， 😉开设频道目的： - 1.专门用于发布作者个人情绪化或不经过大脑思考的表达 - 2.开展一些业务用于“补贴家用”或”圈米“ - 3.分享一些技术前沿知识或稀奇古怪的东西 - 4.任何不适用于在官方Dujiao-Next主频道发布的内容 🏖个人代表作展示 🟢 Dujiao-Next 现代化开源数字商品销售系统，不必多言～ 🟢DujiaoPay Web3稳定币收款网关，结算直达自有钱包（梦想做web3界的Stripe） 🟢佩奇Peiqi @PeiqiBot 免费群管机器人/内置AI风控策略，脚本号痛恨的对象！ 🟢即存网盘 @JiCunBot 一个基于Telegram元数据的网盘机器人，文件留在 Telegram 官方服务器，机器人仅保存元数据，全程不下载、不读取、不缓存任何文件内容。 🟢AI会员自动开 @GoAiOpe…
❤3
Showing the 9 most recent of 9 posts we hold for @simonxbb. 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 — 333,865 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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
“西蒙瞎哔哔” (@simonxbb), 296 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/simonxbb.
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.