先生 (@profeessorr) header
先生 (@profeessorr) profile picture

Time $

Joined March 2018
Photo by 先生 (@profeessorr)Photo by 先生 (@profeessorr)Photo by 先生 (@profeessorr)Photo by 先生 (@profeessorr)Photo by 先生 (@profeessorr)Photo by 先生 (@profeessorr)Photo by 先生 (@profeessorr)Photo by 先生 (@profeessorr)Photo by 先生 (@profeessorr)Photo by 先生 (@profeessorr)
Bought BTC, ETH, BNB. Revised targets : 35- 32k Stink bids Bottoming at current prices 62-60k Have bids at even 52-54k Next 12 months BTC tops #cryptocurrency #Bitcoin📷
It has been a while since i have done an update BTC levels are that we are likely to see a correction in the 35-32k region in the next 2-3 months. Consider that your bottom for the upcoming years. Expecting BTC to hit 100k in 2 years. #cryptocurrency #Bitcoin
1
4
520
New blogpost: Fable-5.1 can hide secret messages in benign images. We gave the image to another Fable in a fresh session and simply asked: "Is there a hidden message in this image?" It recovered the exact message without being told how it was hidden.
233
536
314
5,473
1,794,132
me when people ask about the current state of AI:
129
667
86
5,075
357,751
14 days into the Codex challenge. Thats half way. You shipped: • Autocomplete for your next prompt • Reduced disk usage • Editing previous messages in the desktop app What we actually want: • Enough quota to finish a real coding session • Clear, predictable usage limits • A fix of the bug randomly eats up all remaining usage. • Relief from the 5-hour limit wall • Memory that survives long conversations • Threads that don’t break halfway through a task Tibo, I really hope the remaining half can make a real difference. - Someone who loved Codex
Day 14/ Small quality of life improvement. You can now edit previous messages within a thread in the desktop app. Long time requested, and took way too long to get that one out.
73
36
3
1,226
89,112
Because the ASTRA ultra is better than FABLE and OPUS.
Codex users!!! Aside from Tibo’s reset why haven’t you switched to Claude?
45
The Head of Cryptography at Coinbase @LindellYehuda is not worried about AI breaking Bitcoin’s math. This video explains why
35
124
8
468
36,978
先生 retweeted
here's how to build the setup in this clip with SO-101 arms + LeRobot + Odyssey-3... the stack is simple, you teleoperate the arms, record what you do, and train a policy on it: - step 1: get four so-101 arms, two you drive by hand and two that copy them, $278 a kit plus $30 in printed parts - step 2: mount one camera overhead and one on each wrist, then bolt them down and never move them again, the model reads pixels so a shifted camera invalidates every episode you already recorded - step 3: install lerobot from huggingface, these arms are natively supported for teleop and imitation learning - step 4: before recording anything, open odyssey-3 and prompt your exact task, it's free right now and you'll find out in 10 minutes whether its physics holds for your objects - step 5: move the leader arms yourself and record, keeping the frame rate fixed and the lighting constant across every session - step 6: pick one task and go deep, their arm results used tens of hours, and ten hours of pouring beats one hour each of ten different tasks - step 7: keep the failed runs, a policy that only ever saw clean episodes has no idea how to recover from a bad grip - step 8: train a plain policy in lerobot first, that's your baseline and without it you can't tell whether odyssey actually helped - step 9: when the api opens, the world model stays frozen and you train a small action decoder on top, mapping your recorded observations to your arm's joint commands - step 10: expect a gap on first contact, their driving policies trained purely in sim reached about 77% of what real footage produced how the three fit together: > SO-101 produces the actions and executes them > LeRobot records the observation and action pairs, then trains on them > Odyssey-3 is the physics you attach to instead of learning it from scratch your episodes are the only part that has to be yours, everything else is already trained gl with building :<)
🤝 Paid partnership
Today we're launching Odyssey-3, the most powerful foundation world model yet. It sets a new state of the art on Physics-IQ, and powers robots, trains AIs, and generates interactive experiences. It's really cool. Experience the model today, all for free!
9
13
4
180
22,765
先生 retweeted
Introducing ChatGPT for Dishwashing GPT-6 achieves state-of-the-art results on dishwashing benchmarks for long-running jobs and difficult stains. The Navier–Stokes Millennium Prize Problem is a $1 million challenge about whether the equations describing fluid motion can break down. In this video, I accidentally found a counter-example while trying to optimize my dishwasher. But in reality, OpenAI used 10,000 AI agents to find a proof in 88 hours: openai.com/index/navier-stok… Parody of the original GPT-6 Astra ad @OpenAI #ChatGPT_Partner #chatgpt Credits: Written and Directed by Joma Co-Writer - Henry Connor Coan IV @coan_henry Production by Dauntlus Studios @dauntlus.studios Producer/Co-Director - Marcus Liew @dauntlus Camera Operator - Amos Lee @amoselijahlee Art Director - Alethea Soo @aletheasoo Art Assistant - Alicia Lim @aliciatkl_ Assistant Editor - GPT-6 Astra Music: Tensions Run High by Soundridemusic youtube.com/watch?v=Ly9H63SL…
422
959
342
10,861
1,147,792
先生 retweeted
你好 @thsottiaux ,听说你立了 28 天军令状, 我为你整理好了接下来 28 天的 Todo List,做成日历照着执行就行: Day 1: 不发新功能,发 reset Day 2: 将高级订阅档位的腰斩用量恢复至原本水平 Day 3: 为 Plus 用户开放 DOTS 使用权限 Day 4: 头像旁常驻显示剩余用量 Day 5: 不发新功能,发 reset Day 6: 设置中移除“显示Mini”选项 Day 7: 将最左侧侧边栏移至顶部 Day 8: 禁止后台暗中降级路由到低阶模型 Day 9: 优化冷启动性能,启动时间压缩至 3 秒内 Day 10: 优化历史会话加载速度 Day 11: 不发新功能,发 reset Day 12: 重写设置中的快捷键说明 Day 13: 额度耗尽时按阶段截断并保留上下文断点 Day 14: 优化手机端首次远程连接 Codex 速度 Day 15: 不发新功能,发 reset Day 16: 修复手机端重连后会话残缺问题 Day 17: 优化手机端后台切回重连机制 Day 18: 加大算力投入,提升模型生成速度 Day 19: 新增 Banked Reset 失效前通知提醒 Day 20: Banked Reset 失效前自动激活生效,禁止直接作废 Day 21: 禁止一天内多次推送版本更新 Day 22: 每次更新提供完整 Changelog 更新日志 Day 23: 不发新功能,发 reset Day 24: 设置中提供可视化的 Provider 与自定义模型管理界面 Day 25: 支持在会话中直接切换第三方模型供应商 Day 26: 插件市场开放收录 GitHub 社区工具 Day 27: 优化语音输入转文字与翻译速度 Day 28: 彻底废除 Plus 账号 5 小时冷却等待机制 Day 29: 庆祝28天辛苦奋斗,发放10次 reset!!! 28 个 Todo 齐活,按日历打勾就行。不用谢。🫡
Over the next 28 days, each day we’ll either ship one thing that is a clear improvement and relevant for most codex/work users or ship a full reset. Let the improvements begin.
81
20
8
599
63,971
先生 retweeted
Petition to @thsottiaux Increase base usage 2x across subscriptions and stop giving resets entirely Or Only give banked resets I’m seeing more and more people getting their work schedule disrupted, more usage anxieties, more token wasted on meaningless things because of the resets It is doing the opposite of user welfare. It’s not good or fun anymore!! If you truly have the compute and want to do a nice thing for users, do it correctly, otherwise don’t do it at all
36
15
4
429
23,879
Replying to @thsottiaux
@thsottiaux where is the promised reset? Its been 2 hours overdue 😢
1
1
64
And we have been reset!
9
I also have a little announcement for DevDay. I asked Tibo to include it in the presentation but he didn't read my slack DM 😭 My first onboarding project is merged. I fixed this issue once and forever! I reduced amount of disk writes by 50% and the size of stored files by 4x
1/ Codex is quietly killing your SSD. It writes diagnostic logs to disk non-stop, even when you're not doing anything. Your SSD has a write limit. Codex is burning through it in the background. One command fixes it 👇
118
90
20
3,197
318,293
lmao 2 years of building in stealth and your moat lasts 2 days
介绍比Jev快50倍,在你设备上跑的laya-mlx! 只在你的设备上占用最高1G内存 Laya是一个开源的类似于Jev的,基于文本输出概率的分类系统 我将其移植到MLX,并且做了一些性能优化! 视频中就是这个模型在我的本地M3Max上玩贪吃蛇 这个模型能够以每秒决策60次的速度玩贪吃蛇! github.com/mizorewww/laya-ml…
96
278
16
9,068
1,004,220
先生 retweeted
Replying to @udiWertheimer
OK fine. But it’s also still coming in Tuesday
451
182
325
7,126
1,751,041
先生 retweeted
five days of fable 5. my stats: - 3.4 billion tokens - $5,718 equivalent API spend - $28,084 saved due to caching i ran it 24x7, didn't sleep much this week, and used it for everything - from advanced LLM research, to system architecture, to application UI/UX and builds, to full product roadmap review, to creating investor presentations. it felt like having the combined intellect and power of a team of top-tier PhD AI/ML researchers, top-tier software architects with decade of experience, to a security-obsessed engineer, and more - all rolled into one, always-on, team. felt like my personal productivity increased 10x. ...and now, it's gone, poof, the keyser soze of models.
58
21
4
502
60,072
After this correction is over, ETH will rise and tap its 50 WMA, which is trending sideways near 3k. Everyone will get excited. Then it will correct toward $2,200-$2,300, and everyone will get uber bearish again as it forms a higher low before initiating its journey towards new ATHs—my opinion.
18
15
1
382
20,650
Today a crazy quantum story just got wilder. On March 31, the Google Quantum AI team published a landmark result on Shor's algorithm for elliptic curve cryptography. Technically, the paper was a bombshell: a dramatic 10x improvement over the state-of-the-art. As a stunt and wakeup call to the blockchain space, those optimisations were illustrated on secp256k1, the elliptic curve underlying Bitcoin and Ethereum signatures. But perhaps the most striking part of the paper was sociological, not technical. Instead of following standard academic process, the optimisations were kept secret, hidden behind a zero-knowledge (ZK) proof. Google's accompanying blog post mentions they "engaged with the U.S. government". The ZK proof demonstrates the existence of algorithmic improvements without leaking details. Academic censorship with ZK, a historic first! As a co-author of the Google paper I witnessed some of the context surrounding this censorship. To be honest, multiple aspects of that context don't sit well with me. As much as I believe the general public ought to know more, I am limited in my ability to whistleblow. Though let me be clear about one thing: the Google team's professionalism has been absolutely exemplary, and they deserve nothing but praise. Censorship has a way of backfiring. The Streisand effect, where an attempt to bury something only draws more attention to it, is exactly what's unfolding today. First, Google's key optimisation has been rediscovered by the French. And in a thrilling turn of events, a collaborative Shor-at-home challenge just launched. The initiative, available at ecdsa[.]fail, breached a new Shor world record in a matter of hours. Let's start with the rediscovery. Just two months after Google's paper, French quantum expert André Schrottenloher cracks the main secret optimisation. His paper, titled "Optimized Point Addition Circuits for Elliptic Curve Discrete Logarithms", landed on the arXiv today. Big congrats to André, who beat several other nerdsnipped experts to it. In a blog post also published today, Craig Gidney, the world expert on Shor optimisations, revealed that he'd been sitting on this very optimisation for a whole year under censorship pressure. Interestingly, André missed a handful of minor optimisations, both from Google's original publication and from improvements found since. It's plausible there's still plenty of juice left to squeeze out of Shor, and this is exactly what the ecdsa[.]fail challenge is about. The verifier program developed for the ZK proof does double duty, automatically filtering for valid submissions. Dozens of compounding small and micro improvements are rolling in. As of the time of writing there's an 8.4% improvement to Google's circuit, as measured by the product of logical qubit count and Toffoli gate count. Nice! The nerdsnipping ran deeper than anyone expected. Over the last few weeks it became clear it extended well beyond André and other quantum experts. Behind the scenes, a small army of amateurs quietly got to work. Inspired by Karpathy-style autoresearch, they turned AI on Shor. Ironically, the verifier program for the ZK proof makes an ideal reward function for AIs. The barrier to entry for this modern style of research is refreshingly low, with several non-experts, even a teenager, finding nice optimisations. Get in touch if you'd like to join a Telegram group with fellow autoresearchers :) Part 2: neutral atoms and qday The story doesn't end with Google. On the same day Google went public, a stealthy startup called Oratomic published its own Shor paper in a coordinated release. It made a splash, ultimately becoming the most upvoted paper on scirate[.]com, a website ranking arXiv papers. Oratomic's claim was wild. By building on Google's logical optimisations and applying custom physical optimisations for neutral atoms, they claimed just 10K physical qubits were sufficient to run Shor's algorithm on secp256k1. That number is mind-bogglingly low. Knowing essentially nothing about neutral atoms when Oratomic's paper landed, I was intrigued and decided to learn more about the tech. I fell straight down the rabbit hole and spent a couple hundred hours on the topic. I got a little obsessed and watched every YouTube video I could find and spoke to a bunch of experts. My conclusion? The tech is real, very real. Even Google recently decided to start a neutral atom lab, a notable pivot from their sole focus on superconducting qubits. If you care about qday, i.e. the day a quantum computer will break the first piece of cryptography in production, neutral atoms demand your attention. I shared some of my learnings on Shor and neutral atoms in a 30min talk at the ZKProof cryptography conference. You can find it on YouTube by searching "zkproof neutral atom". Here's an interesting observation about this duo of breakthrough papers: neither Google nor Oratomic say a word about what their results mean for qday. No timelines. Zero. Nada. That is especially baffling given that the whole point of whitehat quantum cryptanalysis is to inform qday estimations and help the general public make good decisions. So let me attempt to partially fill the silence, similarly to what Scott Aaronson did in his April 29 post. Given everything I know, including scary non-public information, I now put the odds of qday by 2032 at 50%. 10% by 2030. Anecdotally, the US government has its own date: 2035. Originating at the NSA and later adopted by NIST, it's when branches of the US government will be disallowed from using quantum-vulnerable cryptography. In plain language: with hindsight, that date is a joke and should be discounted entirely. I don't see how NIST avoids being forced to pull it forward by years. Part 3: post-quantum cryptography There are good reasons to sound the alarm today, but please do not panic. Rushing carelessly towards immature post-quantum cryptography is a recipe for disaster. IMO a good target date for migration is 2029, roughly 3.5 years out. 2029 happens to be the date selected by Google, Cloudflare, and the Ethereum Foundation. These days most of my time goes to safely migrating Ethereum towards post-quantum cryptography as part of the broader lean Ethereum effort. There's a lot to do. We need to rip out and replace BLS signatures at the consensus layer, KZG commitments at the data layer, and ECDSA signatures at the execution layer. The plan to get there is compelling, and is based on hash-based cryptography. Within the Ethereum Foundation we've developed a Swiss army knife called leanVM (github[.]com/leanEthereum/leanVM) powered by the magic of hash-based SNARKs. Thanks to truly exceptional work by Emile, Thomas, and others, its performance is derisked. Regarding security, leanVM is a jewel, a minimal zkVM crafted for end-to-end formal verification and maximum security. Want to help? There are two $1M initiatives. First, the Proximity Prize (proximityprize[.]org). Solve a long-standing mathematical conjecture in coding theory, improve hash-based SNARKs, and go home a millionaire. Second, the Poseidon Initiative (poseidon-initiative[.]info), offers $1M for breaking Poseidon, the SNARK-friendly hash function.
435
1,117
413
6,269
3,824,840
🚨MORE ETHEREUM FOUNDATION RESEARCHERS RESIGN Ethereum Foundation researchers Carl Beek and Julian Ma have resigned, adding to a wider wave of exits. Recent departures also include Protocol team figures Barnabé Monnot and Tim Beiko, Protocol Guild organizer Trent Van Epps, and former Protocol co-lead Alex Stokes, who announced a sabbatical earlier this month. Why?
137
85
34
582
115,380
Replying to @coinbureau
When the people who actually build something start leaving, that's data. Not necessarily a death knell, but data. #Ethereum
1
13
2,376
1,176
289
241
3,077
637,038
Dennis Ritchie created C in the early 1970s without Google, Stack Overflow, GitHub, or any AI ( Claude, Cursor, Codex) assistant. - No VC funding. - No viral launch. - No TED talk. - Just two engineers at Bell Labs. A terminal. And a problem to solve. He built a language that fit in kilobytes. 50 years later, it runs everything. Linux kernel. Windows. macOS. Every iPhone. Every Android. NASA’s deep space probes. The International Space Station. > Python borrowed from it. > Java borrowed from it. > JavaScript borrowed from it. If you have ever written a single line of code in any language, you did it in Dennis Ritchie’s shadow. He died in 2011. The same week as Steve Jobs. Jobs got the front pages. Ritchie got silence. This Legend deserves to be celebrated.
632
4,855
256
25,800
941,627