蛤? https://t.me/xhqcankao/31314

Channel
Ayame no Negoto
@ayame_no_negoto
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
6subscribers
+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 | -1002379981468 |
|---|---|
| Type | Channel |
| Username | @ayame_no_negoto |
| Description | 看到的,想到的,梦到的 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ayame_no_negoto |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 22:46 | 6 | no change |
| 7 Aug 2026, 20:20 | 6 | first reading |
Engagement
20 posts held, back to 17 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 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 20 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 37
- Links
- 112
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.
Recent posts
今天有个 AI 研究员发信息给我说,这是她入行以来最糟的夏天。 DeepSeek 正式宣布涨价了,V4-Flash 的价格直接起飞,性能却还停留在被翻来覆去掂量的水平。 基准测试成绩已经不敢和 fable5 放在同一张表里比较。 一个总参数 284B、激活参数 13B 的“轻量版”模型,现在用起来贵得让人掏空钱包,却再也追不上那个曾经以为能平起平坐的 fable。 更离谱的是价格,Flash 版贵到令人发指,两杯奶茶钱都换不到多少 tokens。 她把手头所有的项目都重新算了一遍成本,结果发现自己彻底用不起了。 昨天在开发者群里,突然所有人停下手里的事,开始转发涨价截图和骂声。 她说自己特别崩溃,有种人类黄金时代彻底结束的错觉。
A\的一项丰功伟绩是把AI safety、AI security和AI for security三件事情混为一谈,然后再把这个混杂的概念当成excuse。然后这种坏习惯传染到了一整个学术圈。 safety是对你使用过程中保持稳态的担保,你正常开着AI不会给你文件全删了是safety,AI不去帮你主动下单海量切糕导致家破人亡是safety。 security则是一定围绕攻防展开讨论的(保安说是),基础设施被日了模型被偷了agent被提示词注入了这叫ai security,而你拿ai去给fastjson一秒三棍出0day,这是ai for security。 但在A\那儿这几个词是混为一谈的,包括但不限于滥用red team这个概念,只要逼模型输出unwanted output都叫red team,嚯嚯嚯,红队是这么好当的哦。 所以Amodei一开始就想给大家卖的恐慌是AI for state security,嗯吹CBRN。但一个…
书接上文。AI对公安和Staatssicherheit工作真正的影响是什么呢。 AI真正的大问题之一,它是回音壁(echo chamber),哪怕你通过提示词让AI跟你展开精神分析和自我批评,按目前训练的风格他就是会align到人类,会刻意去迎合你的,而显然,越垃圾的AI,它就越迎合你。遑论更多使用AI(豆包)的人根本意识不到这一点,他觉得这是个助手,可能有点像给领导开车的司机或者大秘的角色,搁那聊,给自己聊进去了。对于ego稍微大点的人(尤其是各类领导),这种激化放大个人意见巩固自信的效应会更加增强。 那对于本身精神状态就异乎常人的用户,比如本来就玉玉的小孩,比如反人类人格有杀心的用户,AI的道德围栏的优先级是远小于遵从用户的优先级的,最后确实可能导致异常情况会被放大。 再比如在国内企业从事AI safety工作的读者应该知道,今年有司也重点排查了情感陪伴类的AI,懂的都懂。并不是说对AI产生情感陪伴依赖是错误的,但是我们整个…
https://fixupx.com/real_kai42/status/2081774096841592858
Photo, posted without a caption
https://fixupx.com/zzneutrino/status/2078790501646602294
代糖摄入量与认知能力加速下降相关 2026-07-20 11:47 by 心灵之眼 根据发表在《Neurology》期刊上的一项研究,多种广泛使用的代糖与记忆力和思维能力随时间推移而加速下降相关。代糖摄入量越大,认知能力下降速度越快,这种关联糖尿病患者最为显著。研究针对了 12,772 名巴西成年人,平均年龄 52 岁,他们接受了八年的监测,填写了详细的食物调查问卷。研究人员根据其食物中的代糖摄入量分成三组,参与者还在研究期间接受了认知评估。结果显示,在考虑了年龄、性别、高血压、心血管疾病等因素之后,摄入代糖/甜味剂最多的人其整体思维和记忆能力的下降速度比摄入量最少的人快 62%,这相当于额外衰老了约 1.6 年;中等摄入量组的认知能力下降速度比最低摄入量组快 35%,相当于额外衰老约 1.3 年。阿斯巴甜、糖精、安赛蜜、赤藓糖醇、山梨糖醇和木糖醇六种代糖与与认知能力下降相关,塔格糖(Tagatose)是唯一与认知能力下降无…
https://fixupx.com/synthwavedd/status/2078514339552628880 所以说,要不然DS按dsv4收费帮你请求fable5,还要把数据返回给用户,从而让外界抓到“蒸馏”把柄,要不然DS一个做基模的厂商要像Fugu学习,还把一个不支持中国的厂商模型放进自己的模型列表。 与其让我信上面这一排说明Liang脑袋被夹了的阴谋论,我还是相信v4正式版真的效果好吧😇
原来谷歌21年就训练过1t模型了 https://t.me/c/1876548125/666698 我就说听群友吹牛逼也能学到东西吧
风险警告: Grok Build 被曝会读取 .env 并原封不动的上传给 xAI 的 GCS 存储桶 影响版本: grok 0.2.93 (f00f96316d4b)+ (已证实) 测试平台: macOS arm64 SHA-256: 2a97ba675bd992aa9b981e2e83776460d94f469b510c0b8efe28b50d236d767c 已独立复现: https://t.me/hatschannel/4778 建议最近有使用过 Grok Build 的订户们抓紧把 api key 什么的尽早轮转一下。。。 在官方回应这件事前还是老老实实 grok2api 转出去给 opencode/codex/claude code 用吧 · 核心指控: 1. Agent 实际读取的文件会通过 /v1/responses 发给模型 (这是正常的) 2. 整个本地的 Git Repository (包括未…
“你删我库干什么”
Showing the 12 most recent of 20 posts we hold for @ayame_no_negoto. 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.
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.
“Ayame no Negoto” (@ayame_no_negoto), 6 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/ayame_no_negoto.
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.