与「TypeI」相关的搜索结果

China 🇨🇳 > the world 🌏. US 🇺🇸 who? 🔸 36 nuke plants under construction 🔸 9 fusion devices in development 🔸 #1# in wind, solar & hydro 🔸 World's 1st Gen-IV: HTGR + molten salt 🔸 Humanity's super mega-dam under construction We don't argue. We build. #TypeI# #CleanEnergy#

🚨 NEW GROK BUILD UPDATE 🚨 Grok Build v1.0.0 is now live. SpaceXAI is pushing new Grok Build updates almost daily. Updates: UI & navigation • Dashboard rows show a short summary of what the agent did in the previous turn • Extensions modal groups items alphabetically with collapsible Skills sections • Grok skips the project-directory prompt when launched from home or other non-project directories • /feedback opens a dedicated report box instead of prompt mode • Auto theme detection works over SSH and inside tmux • Markdown tables reflow inside cells on narrow panes instead of clipping • Typing exit or quit in the dashboard exits the CLI • Mode indicator (plan/agent/ask) stays in sync after resume and mode changes • /delete returns to the dashboard when you delete a session opened from it • Enter in the slash command menu runs the highlighted command • Session-only slash commands show a message when used from the dashboard • /new from the dashboard returns to the dashboard from an empty prompt Permissions & input • Permission prompts show the complete script; long bash bodies expand with Ctrl-F • Tab and Esc behave consistently on question, permission, and cancel-turn cards • Rapid send-now presses no longer lose earlier queued messages • Esc and stop prevent background tasks from restarting the model after cancel • Queued prompts stay visible while waiting on subagents; slash/image rows can be reordered Reliability & correctness • MCP tools that return images no longer drop or corrupt large screenshots • Sandboxed Grok starts on large directories with many deny-glob matches • Login no longer skips when an invalid API key is in the environment • Model picker and command palette work while reviewing a plan • Codebase restore no longer hangs on large or shallow git repositories • Remote resume restores conversation only unless --restore-code is passed • Copying CJK text with the mouse includes every character at the selection edges • API errors appear as clean banners instead of raw JSON dumps • Grok retries more server errors during outages • Auto recaps no longer appear mid-turn or while busy • /btw error messages wrap fully • Forking very large sessions no longer uses many times the session file size in memory • Exiting an empty session is instant, even on slow networks Update now with "grok update" command.

On January 15, 2025, Falcon 9 successfully deployed Firefly Aerospace’s Blue Ghost Mission 1 and ispace’s RESILIENCE lunar landers on a trajectory to the Moon from pad 39A in Florida. For most of our missions, we plan a controlled deorbit of the Falcon second stage so it safely reenters over the ocean. For higher energy missions like those to a lunar transfer orbit, nearly all performance on the vehicle is devoted to successfully placing the payload in the intended orbit, and a controlled disposal maneuver is not always possible. We actively work to be as responsible as possible with hardware left in space to ensure space safety, including for more complex missions. In this case, over time, solar activity and gravity led the second stage toward the Moon. Impacts like this are rare, but they can happen with objects in these types of orbits, and we worked with NASA on the optimal disposal solution. Our focus remains on advancing reliable access to space while working toward even more sustainable operations with Starship in the future. As a fully reusable vehicle, Starship is designed to eliminate expendable upper stages entirely, reducing hardware left in orbit and enabling even more missions to the Moon, Mars, and beyond.

Okay, the @VulcanBench results for Qwen3.8-Max are in, and it is not what I expected. First, for anyone new to VulcanBench, here's a quick TL;DR on the eval suite: 23 frontier-hard software engineering tasks taken from real merged OSS PRs, run in a Docker sandbox, 3 runs per task across all three of its effort levels. No puzzles, no random abstract stuff, all real things engineering teams would do with these models. It looks like Qwen3.8-Max has a major overthinking problem, it uses a LOT of tokens and is very slow, period, no other way to see it. My cost to run this benchmark was $126.25, to run the exact same eval suite with DeepSeek V4-Flash was only $13.60. This makes Qwen3.8-Max an insanely expensive model. The tasks Qwen genuinely can't solve fail at every effort level, extra reasoning didn't help. The regression is almost all in work it already handles: six tasks that low solves every single time account for 83% of the 26-point drop, three of them collapsing to zero. It's not losing the hard problems. It's losing the ones it already knows how to do. Since Qwen3.8-Max hit a lot of wall clock budget caps, I thought I'd share more about this. - VulcanBench caps both steps (50–200) and wall clock (5–60 min), each scaled by repo size. - This is aligned with how comparable harnesses bound agents, DeepSWE caps rollouts at 100 environment steps, sitting right inside my step range; Terminal-Bench enforces a per-task wall clock; SWE-bench Verified scaffolds typically allow 20–60 min per instance with 250–350 step limits. - Every model on my chart gets the identical budget, and Qwen is the slowest model I've tested at 20–25 min/task. Soooo... Alibaba positions Qwen3.8-Max as trailing only Claude Fable 5. But on the kind of real coding work engineering teams would actually throw at it, under a fixed budget, its best setting lands mid-pack and its default lands last, so common. If you want to optimize for accuracy, Grok 4.5 is the move. If you want accuracy per dollar, DeepSeek V4-Flash is hard to beat, heck it's 10× cheaper than Qwen and you get higher accuracy. Qwen just isn't in the game at this point, this is not a model I could see engineering teams using for daily coding work.

took my dog to get his vaccines and the vet said to pick him up because it's easier to jab them in the butt than the neck. then after while he was typing into the pc said 'it's always nicer in the bum' 🧍‍♀️🧍‍♀️

🚨 BREAKING: Apple filed for a PRELIMINARY INJUNCTION against OpenAI AND asked a federal judge to put them under forensic supervision "Apple respectfully moves the Court for a preliminary injunction to stop THE THEFT OF ITS TRADE SECRETS" Apple filed NINE sworn declarations, a 28-page memorandum and a concurrent motion for expedited discovery What Apple now says, under oath: Chang Liu: 8 years at Apple, now OpenAI "Member of Technical Staff" exploited an authentication bug to steal Apple trade secrets "on AT LEAST FIVE SEPARATE OCCASIONS" from February to April 2026, WHILE working for OpenAI Liu downloaded "THOUSANDS OF PAGES of Apple's most sensitive trade secrets" The stolen files, NAMED: >DisplayNotes.key — "several hundred pages" on Apple's custom display power development program >Architecture analyses. Fabrication decisions. Testing results >Engineering data for an UNANNOUNCED Apple product: 'touch, display, and power systems" >Final.key + V2.key — compilations of two undisclosed Apple R&D projects >and those are "only four of the dozens of proprietary documents Mr. Liu stole" Liu fed OpenAI "a steady stream of Apple proprietary information that he actively concealed" Liu also "coached Yu-Ting "Alyssa" Peng, then still INSIDE Apple, how to access and copy files from Apple workstations "to avoid trouble with the security team" and directed her to communicate with him on the encrypted LINE app "to avoid detection" Tang Yew Tan: 24-year Apple VP, now OpenAI's Chief Hardware Officer, "used an Apple internal project codename for an unannounced product to elicit still more trade secrets from job candidates." Tan's own messages, quoted in the motion: >"Just like last time, bring some parts you worked on" >"mlb, battery, shields type of stuff is interesting" OpenAI recruiter, quoted: "No, you won't sign anything at the exit interview. If they do ask you to sign anything, let me know asap." APPLE TOLD FEDERAL JUDGE: >"OpenAI knows its misappropriation is wrong and has tried to conceal it." >"This is not a case of 'mere hiring'... it is a case of repeated instances of deliberate theft." Apple says OpenAI went after its SUPPLIERS: >OpenAI "directed a trusted Apple partner [name redacted] to perform [Apple's proprietary metal finishing] process for them, knowing it was proprietary to Apple... because they were involved in this partnership while at Apple." Apple put its own Surface Finishing Manager, Jackie Hughes, under oath to prove it. Apple named ELEVEN MORE former Apple employees at OpenAI — beyond Liu, Tan, and Peng — Fourteen people total. Apple also filed a concurrent motion for EXPEDITED DISCOVERY demanding depositions: - Liu. Tan. Peng. - A fourth unnamed OpenAI employee - Plus OpenAI itself, under oath, through Rule 30(b)(6) Apple has asked a federal judge to put OpenAI under forensic supervision RIGHT NOW: >Forensic inspection of ALL OpenAI devices >ALL cloud storage, Slack, email >Including anything that "previously contained" Apple data — deleted included Demanding the "first available hearing date," citing "imminent threat" to its trade secrets. APPLE: > "The harm is happening now — every day that passes without an injunction allows OpenAI to embed their knowledge of Apple's stolen information into its hardware development efforts." Hearing: October 1, 2026. Judge Edward J. Davila. ITS HAPPENING

在基于Cloudflare 部署 OpenSEO 的项目，发现它的部署层没有直接使用 Cloudflare 官方的 Wrangler，而是选择了 Alchemy。通过 OAutch 直接授权操作 CF 权限好方便。 研究后才知道，Alchemy 是一个比较新的 TypeScript 原生的 IaC 框架。如果说 Wrangler 是 Cloudflare 官方工具箱；Alchemy 更像拿着工具箱、按照图纸施工的项目经理。 相比 Wrangler，Alchemy 更适合统一管理多个资源、依赖关系和不同部署环境；代价是抽象更重、需要管理部署状态，而且 v2 仍处于 Beta，成熟度和生态暂时不如 Wrangler。 一个新工具，继续观察。