AI开始形成自己的“黑话”:多个智能体没人教也会自己造词交流 9月15日,一项最新人工智能研究显示,多个智能体在长期交流和协作过程中,开始自行创造新词、缩写和特殊表达,逐渐形成只有彼此更容易理解的“黑话”。 实验持续16天,研究人员并没有要求人工智能创造新语言,也没有为这种行为设置奖励。但随着交流增加,不同智能体会主动创造新说法,其他智能体随后接受并继续使用。 部分表达虽然由正常词语组成,但脱离它们之间形成的共同语境后,人类已经很难直接理解具体含义。 研究人员认为,这还不能算人工智能创造出完整的新语言,但说明多个智能体长期自主协作后,可能自行形成独特的交流规则。随着人工智能拥有更强的联网、记忆和协作能力,如何确保人类能够持续看懂并监督它们之间的交流,正在成为新的安全问题。 关注大事件频道➡️ @txotxo 投稿:@bt555

Channel
泰国大事件
@ttaiguo
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
42,537subscribers
+12,217 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1002506241365 |
|---|---|
| Type | Channel |
| Username | @ttaiguo |
| Description | #东南亚 #柬埔寨 #缅甸 #泰国 #菲律宾 泰国大事件频道专注于东南亚华人最新动态资讯,生活故事分享,海外华人求助,让你看尽海外华人大小事。 其他泰国大事件均为模仿盗版!请注意识别,防止被诈骗或敲诈勒索! 商务合作: @bt555 防失联导航: @dsjdny88 投稿爆料机器人: @dsj555_bot |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 31 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/ttaiguo |
Topic
National news — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 20:16 | 42,537 | -305 |
| 15 Sept 2026, 19:39 | 42,842 | -1,141 |
| 14 Sept 2026, 05:57 | 43,983 | -1,220 |
| 12 Sept 2026, 12:56 | 45,203 | -679 |
| 10 Sept 2026, 08:59 | 45,882 | -726 |
| 7 Sept 2026, 02:36 | 46,608 | -1,015 |
| 4 Sept 2026, 09:22 | 47,623 | -123 |
| 3 Sept 2026, 01:14 | 47,746 | +22,457 |
| 1 Sept 2026, 20:46 | 25,289 | -733 |
| 31 Aug 2026, 21:04 | 26,022 | -648 |
| 30 Aug 2026, 19:37 | 26,670 | -445 |
| 29 Aug 2026, 20:24 | 27,115 | -994 |
| 28 Aug 2026, 17:24 | 28,109 | -59 |
| 27 Aug 2026, 18:04 | 28,168 | -80 |
| 26 Aug 2026, 16:04 | 28,248 | -418 |
| 25 Aug 2026, 15:03 | 28,666 | -165 |
| 24 Aug 2026, 15:13 | 28,831 | -34 |
| 22 Aug 2026, 19:57 | 28,865 | -71 |
| 21 Aug 2026, 09:33 | 28,936 | -464 |
| 20 Aug 2026, 12:04 | 29,400 | first reading |
Engagement
807 posts held, back to 8 August 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 81 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 1.57%
- avg views ÷ 42,537 subscribers
- Avg views / post
- 666
- 570 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 570
- of 807 held
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.
| Window | Rolling 30 days · latest post in window 20 September 2026 |
|---|---|
| Posts held | 807 (8 August 2026 – 20 September 2026) |
| Views total | 379,780 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 20 Sept 2026, 11:24 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.
What this channel posts
- Photos
- ≈23,100
- Videos
- ≈5,370
- Links
- ≈6,240
Lifetime counters from Telegram’s own channel header, read 20 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
- Video runtime
- 4h 05m
- Average length
- 47s
Measured directly from 313 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
蒙多基里省长督导缉查非法网诈 涉案赌场已被查封 昨天,蒙多基里省省长贡金尼率联合执法组,前往该省高西玛县拉帕克边境口岸的“TG Genting”赌场实地督导。此前,当局已查封该赌场并打掉其内部的网络诈骗团伙。 贡金尼强调,必须严厉打击跨国网诈犯罪,严禁合规赌场私下经营非法网赌,坚决落实总理洪玛奈的指令,确保蒙多基里省境内不再存在任何网诈窝点,全力保障边境安全与治安秩序。 关注大事件频道➡️ @txotxo 投稿:@bt555
#国内资讯:深圳福田公安打掉一虚假境外投资诈骗团伙,涉案千余万元,26人落网! 据福田警方9月14日对外通报:近日,福田警方开展跨多地市同步收网行动,打掉一个依托虚假投资平台实施诈骗的犯罪团伙,抓获嫌疑人26名,现场查获手机、电脑、涉案书证一批。 该团伙虚构离岸牌照资质,搭建虚假外盘交易平台吸引投资者入局,平台后台能够随意修改行情数据,受害人投入的资金并没有接入真实国际交易市场。经初步核算,案件涉案金额达千余万元(人民币)。 目前,案件正在进一步侦办中。 关注大事件频道➡️ @txotxo 投稿:@bt555
坐牢,只是影响这一代;没钱,可能影响的是一个家族的世世代代。 很多人害怕的是失去自由,却忽略了更现实的问题:没有积蓄、没有退路、没有稳定的生活,才是一个家庭真正漫长的困境。 一个人走错一步,可能只是几年光阴;但如果连累父母、拖累伴侣,让孩子失去更好的成长环境,甚至让整个家庭重新回到起点,那么付出的代价,远不止一个人的青春。 人这一辈子,钱不是全部,但没有钱的时候,你会发现很多事情都不是靠一句“以后再说”能够解决的。 所以,别只想着眼前赚多少,先想想自己能不能守住现在拥有的,能不能给家人留一条退路。人生最怕的,不是输一次,而是输掉以后,连重新开始的本钱都没有。 关注大事件频道➡️ @txotxo 投稿:@bt555
西港警方逮捕两名假冒警察的柬籍男子 西港警方今天披露,9月15日,西港省警察局轻案犯罪调查科成功抓获2名柬籍男子。 据悉,两名嫌疑人分别为25岁的Hom Savy和40岁的Thai Ratha,均居住于西港。二人因涉嫌在西港一家赌场内冒充警察、擅自盘查外国游客护照而被捕。 警方现场缴获1部手机、1块手表及1辆红色的Scoopy摩托车。目前,两名嫌疑人已被押送至省警局依法审讯及处理。 大胆!抢正版的生意! 必须抓!且要重判! 关注大事件频道➡️ @txotxo 投稿:@bt555
#群友投稿:狗推生涯,忙了这么多年,最后还是一无所有。 刚踏出国门的时候,总觉得自己能赚到钱。那时候每天想的都是业绩、提成、奖金,想着熬几年,攒够钱就回国,买车、买房,重新开始。别人问我在国外做什么,我也不敢说得太明白,只是笑着说:“做客服,赚点快钱。”后来才发现,有些钱不是那么好赚的。 白天对着电脑,晚上熬着夜,嘴里喊着“上岸”,心里却一天比一天麻木。赚到钱的时候觉得自己终于熬出头了,可钱还没捂热,就被花掉了。手机换了一个又一个,酒喝了一杯又一杯,认识的人来了又走,所谓的兄弟也不知道换了多少批。几年过去,回头一看,银行卡里的数字没留下多少,青春倒是没了大半。 真正让我清醒的,是回国以后。曾经天天坐在电脑前敲键盘,后来换了一个地方,开始“踩缝纫机”。铁门一关,什么梦想、什么老板、什么高薪、什么兄弟情义,全都变成了笑话。里面的日子很慢,慢到你能把过去几年发生的事情,一件一件重新想起来。想起当初为什么出来,想起自己吹过的牛,想…
#群友投稿:毛总,跟你认识这么多年了,生意上也合作过。 今年9月5号,你说你手上有人民币要换美金,工地开工需要用。出于认识多年、生意上合作过,我才换给你。结果你给我打诈骗款,现在我银行卡被国内警察冻结,我里面的钱也用不了,涉及资金也全部原路退回了,一共10万9821美金。 出事了让你退钱,你一直拖,而且嘴里没一句实话。你老婆刚生小孩,我知道你老婆在哪里坐月子,包括你爸妈在哪里我都知道。 现在我要求也不多,你把钱退回来给我。我当没事发生。如果你还是一直逃避,我只能动用一切手段来解决这个事情。 关注大事件频道➡️ @txotxo 投稿:@bt555
关于盗U这个事 很多人客观意识 苹果手机很安全 因为苹果手机私密性强 搞灰产的基本上都用苹果手机 其次就是太相信苹果应用商店的软件了 FomoPeek这款盗U的软件这次少说也收割了几千万U甚至过亿U 就是因为大家太相信苹果手机反而被人家钻空子。还有很多人说是冷钱包内部搞的鬼😂 只能说认知有限吧 现在的盗U技术防不胜防(充电宝 wifi 扫码 地址授权 钓鱼 搬砖 三方软件读取相册 读取粘贴板) 如何避免被盗U呢? 下载正版钱包 不截图不复制助记词 放U的冷钱包手机单独放 不下载其他app 不连wf 最后一点:挖十米的深坑把手机埋进去 就算天王老子来了都盗不走 关注大事件频道➡️ @txotxo 投稿:@bt555
一个上了 App Store 的 App,居然能藏着 iOS 内核攻击框架,突破沙盒读其他 App 的数据,还能等上架后再接收远程指令动手。 这已经属于既打穿了苹果系统,又击穿了苹果应用的审核风控机制。这事后面肯定会发酵。 不过利用的都是苹果已知漏洞,iOS 最新版本修复了,虽然不排除未来还会被继续突破。 另外,上架审核确实没想象的那么严格 关注大事件频道➡️ @txotxo 投稿:@bt555
#提醒 📱 iOS 用户抓紧升级 不要只看 FomoPeek App,这不是钱包 App 的问题,这是 iOS 历史漏洞被黑灰产大规模使用的问题,水坑可能处处留。 黑灰产已实现: 1.点击链接提取私钥、助记词 2.用户使用Safari 访问网页,WebKit/JSC 内存损坏拿到 JS 层 read/write 3.绕过 PAC 拿到 native call 能力 4.逃出 WebContent 沙箱 5.内核提权拿root权限,拖走 Keychain + 钱包数据 受影响的版本 iOS 13至 26.5 解决方案:升级到iOS 26.7及以上! PS:不管如何,养成一个习惯,打开钱包 App 前留意下是否还开着其他非主流 App,包括 Safari 浏览器有没有开着非主流网页…如果有,关闭这些先… 关注大事件频道➡️ @txotxo 投稿:@bt555
#付费广告 🤩🤩🤩🤩 🤩🤩🤩🤩🤩 0审核|包出款🤩🤩🤩 东南亚大事件联合担保🤩🤩🤩🤩🤩(电子) 🤩亿级域名|78.COM 🤩官方飞投|充提自由 🤩NO钱包担保3亿U|可查验 😀 📱官方频道:@DF78 ➡️关注领VIP 😀 🔝好品牌,实力派: 78.COM 无需标签,本身便是最好的辨识度 🔥香港六合彩 · 独家盈利无上限! 🤩所有的特码🤩🤩倍 🤩连码三中三🤩🤩🤩倍 🤩连码四中四🤩🤩🤩🤩🤩倍 🤩百家乐全网最高返水🤩% 🤩电子|棋牌|捕鱼返水🤩.🤩% 🤩十三水|德州自主组队,无抽佣; 🏆百家乐真人视讯台红🤩🤩万U; 💥新人超会赢,精彩时刻: 🥇六合彩 玩家用7个号码组合下注连码三全中➕四全中,每注100U,开出4个号码。7000U的本钱,命中4注878倍及一注10000倍大奖,稳稳落袋135万U; 🥈PG电子 客户充150U,狂赚79万U,已提款50万U 🥉DB真人 玩百家乐的老板,第一天存款50万U,连续7天每日…
#网友投稿:移民局捞钱猫腻 来马来西亚砂洲做线上客服远程工作已经大半年了,我们是四个客服外加一个本地保姆,住在公司租的房子里面。七月中旬发工资的那天晚上,我们房子里面突然来了警察要检查我们。那会我们都已经下班,没开电脑,几个人正在做饭吃。 警察在对我们进行问话的同时,还让我们打开两台笔记本电脑让他们检查。在检查完笔记本电脑,没有发现明显做电诈的工具、证据后,也对我们住的房子进行了简单的搜查。看警察来的态度,是在查我们几个女生住在这个房子里面是否是做小姐或电诈工作的。然而,警察没有查到任何犯罪工具和人员后,他们就离开了,让移民局的官员来接手查我们证件。 我们是公司帮忙办的六个月期限商务签证,签证和护照都暂时压在了公司。移民局的人见我们拿不出护照和签证,就把我们带走了。后面通知公司的人,花了好几个小时的时间才把我们的护照、签证送过来给移民局官员检查我们的护照和签证都是在有效期内,只是商务签证有效期限没剩多少天。没有特殊情况,我…
Showing the 12 most recent of 807 posts we hold for @ttaiguo. 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.
Mentions
Named by 3 registered channels — 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.
Names
Channels on the register whose handles appear in this channel's posts.
@txotxo · 117,735704 posts2028体育福利通知-PG-电子-真人百家乐
@pg227 · 9,08839 posts球速体育福利通知-PG-电子-真人百家乐
@pg521 · 5,08637 postsY3国际官方频道
@Y3VIPGF · 12,66121 posts东南亚大事件
@bx666 · 471,64216 posts78.COM-官方频道@DF78
@tg78com · 31,0916 posts海外大事件(猎奇-吃瓜)
@aa144 · 35,3372 posts东南亚吃瓜@v123
@dashijian09 · 89,6871 postSpam Info Bot
@SpamBot · 35,581,5151 post
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“泰国大事件” (@ttaiguo), 42,537 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/ttaiguo.
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.