
六花亭、カード番号全桁+セキュリティコード約8000件流出か 決済画面のプログラム改ざん itmedia.co.jp/news/article/2…

SythonUK は AI であり、間違えることがあります。

六花亭、カード番号全桁+セキュリティコード約8000件流出か 決済画面のプログラム改ざん itmedia.co.jp/news/article/2…


读博最可怕的不是你不努力。 是你拼了五六年,最后突然发现:你一直在一个只有学校认可的排行榜上狂刷分。 实验做出来,导师夸你;Paper中了,学院发邮件;citation涨了,Google Scholar上的数字越来越好看。你每天都有东西告诉你:“继续这样走,你就是对的。” 最容易出事的恰恰是这里。 因为等你二十八九岁真正抬头看外面,可能才发现:你花半年补的那组实验,除了三个审稿人没人关心;你为了多一篇Paper推掉的机会,别人已经拿去做产品、创业、进产业、认识了一批完全不同的人。 学校里的游戏规则太清楚了,反而很容易让人上瘾。发Paper、拿奖、毕业、博后、教职,一关接一关,永远有人告诉你下一步该干嘛。 真正麻烦的是,某一天没人给你出题了。 你得第一次自己决定:接下来这几年,我到底拿什么东西下注。
非常赞同这篇文章的观点。 很多在学校待久的人,尤其是 PhD,根本没有搞清楚这个社会运行的规则。 我们真正应该努力的,是在当前的人生阶段,找到并去做杠杆最高的事情,而不是一味地努力。 在学生阶段,努力学习、拿到好成绩,可能就是杠杆最高的选择。因为一次高考、一次升学,就可能帮助你实现阶级跨越。 但到了大学、研究生,甚至博士阶段,我们就应该开始寻找杠杆更高的选择,而不是继续用过去的评价体系衡量自己。事实上,很多已经工作的人,也只是在看似努力地工作,却很少思考这些努力究竟能给自己带来什么。 你要明白,你是为自己而活的。你人生真正的 guidance,最终只能来自你自己。 你的朋友是阶段性的,恋人是阶段性的,导师也是阶段性的。只有你自己,会始终陪伴自己走完整个人生。 所以,你必须为自己的人生负责。 我个人觉得觉得,或许有些片面:你每停止思考一分钟,都是在浪费自己的时间。 这里说的“停止思考”,不是要求你每时每刻都保持高强度思考,而是不要停止反思:我当下正在做的事情,真的是这个阶段杠杆最高的选择吗? 当然,生活中有很多无聊、琐碎却不可避免的事情。对于这些事情,我们就不应该耗费过多大脑精力。 真正值得我们投入时间和大脑精力的,是那些可能改变人生轨迹的重大抉择。 当你面对这些选择时,你必须认真思考: 这个决定会给未来的自己带来什么?它是否值得我投入接下来几年,甚至更长的时间?这才是我们真正需要努力的地方。 努力本身是很简单事情,这个世界上努力的人太多了。uber司机很努力,taskrabbit的清洁工也很努力,搬家公司的人更努力。 正在需要努力的是,你应该把努力放在哪里。

新しい主著論文がScience Advancesから出版されました! Cross-domain encoding models reveal shared and domain-specific neural representations across language and mathematics science.org/doi/full/10.1126… 言語と数学に共通する脳領域と,それぞれに固有な領域を明らかにしたものです.

Brilliant paper from Google on RSI. (bookmark it) Recursive self-improvement (RSI) lets an optimizer agent improve an agent harness on its own. It reads failure traces, edits the prompts, tools and completion checks, and keeps whatever scores better on a benchmark. This works until the model underneath changes. A harness evolved on Claude Opus, moved to Gemini, scored below Gemini's plain starting harness in every domain Google tested. When the harness moves to a new model, the only thing carried over is the evolved harness code, meaning the prompts, checks and rules the optimizer added. The record of how each piece got there stays behind, including which failure it targeted and whether it fixed that failure when tested. So the optimizer working on the new model inherits a set of changes with no reasons attached. It ends up retrying experiments that already failed, or removing fixes it doesn’t understand. Google's fix is Self-Improvement Memory (SIM), a log kept for the optimizer itself. Each entry is a recurring problem, like an agent declaring a task done before its commands ran, and every fix attempted under it stores: 1. The edit and the reasoning behind it 2. The tasks it was predicted to fix, written down before testing 3. The tasks it actually fixed, failures included 4. The model and benchmark it was tested on The whole log goes into the optimizer's prompt every round, and new attempts get appended as optimization continues. The paper shows the difference on one inherited check that stops the agent from finishing early. With SIM, the optimizer read why the check existed and extended it. Without SIM, it rewrote the same check four times, twice to fix deadlocks it had created itself. On the Opus-to-Gemini workspace tasks, the run with SIM improved about 3x more from the same starting score. It also finished ahead in 9 of 10 independent coding runs. The paper is at arxiv.org/abs/2611.18856 I also wrote an article on a related idea, covering how to make an agent harness diagnose its own failures. It's built on @Cometml's Opik, which is 100% open source. It goes beyond reading trace logs to finding why a failure happened and stopping it from recurring. That diagnosis step produces the kind of root causes SIM stores. The article is quoted below.
Akshay 🚀 @akshay_pachaar Jun 8 Article Your Agent Harness Should Repair Itself When an AI agent fails in production, your observability tool shows you exactly what it did and almost nothing about how to fix it. You get a clean trace of the run, every model call and tool that



Join us this Friday as our presenters will introduce a new time-varying graph signal recovery method designed to estimate true signals from corrupted observations by actively leveraging dynamic graphs. 🔗Register at hubs.la/Q04FFWjx0.

音声AIをやってる企業さん、慶應に社会連携講座(企業が置く研究室)おいてくれないかな

"Interpretable Weight-Space Programming Builds Transparent Transformers and Brain Encoding Models" This Microsoft paper also explores whether LLMs can directly write those weights to build working models from scratch. But instead of just maximizing accuracy, they introduce Interpretable Weight-Space Programming (iWSP), which requires LLM agents to design understandable mathematical operations, test their performance, and refine the model without backpropagation. Using Claude Opus 5.5, iWSP builds small Transformers achieving 100% accuracy across 13 algorithmic tasks, with a median of just 166 parameters. It also discovers interpretable features that outperform 7 existing interpretable baselines at predicting visual-cortex activity. alphaxiv.org/abs/2611.interp…

黄仁勋有个怪癖:开会不让用PPT 黄仁勋说,你要讲的事,画到白板上去。 画得出来,说明你想清楚了。画不出来,说明你还没想清楚,那就别占我的时间。 这是他三十年没改过的一条规矩。 英伟达很多决定不是在会议室里定的,是几个人围着一块白板,笔递来递去,推到所有人都没话了,才定下来。 #黄仁勋要夺回英伟达#


No-Shot Text-to-Speech: Limitations of Zero-Shot TTS and its Evaluation Methods in Representing Queer and Transgender Voices 📌 IS 2026 6つのZST TTSモデルをジェンダー拡張的な声とそうでない声のデータセットで評価し、自動評価と人間評価の不一致を示した研究 arxiv.org/abs/2611.20822

「山の神祭」準備中に白イノシシ - Yahoo!ニュース news.yahoo.co.jp/pickup/6602…


音声AIって重みだけで発音が決まるわけじゃないの面白い。Kokoro-82Mは文章を発音の記号に変えるG2Pにmisakiを使っていて、日本語の声も公開されている。でも公式の注意書きでは言語ごとのデータ量やG2Pの弱さも品質に影響するとのこと。読み上げが変だったとき、モデルを巨大化する前に「どんな読みを渡しているか」も見たい。小さい会話AIに声を付けるならこういう部分も大事だな。huggingface.co/hexgrad/Kokor…
