←搜索结果

按匹配度 · 共 51 条结果 清除搜索

星期六

  1. SemiAnalysis

    SemiAnalysis 实测 Trainium3 的 PyTorch 训练与 Neuron Explorer 剖析器

    SemiAnalysis 工程团队在 Trainium3 上实测了原生 PyTorch 训练栈 TorchNeuron 与 TorchTitan,用 Qwen3-32B 在 16 颗 Trainium2 上训练,eager 模式达 11,099 tokens/s、23.89% MFU,compiled 模式达 14,156 tokens/s、30.47% MFU。作者认为 Neuron Explorer 剖析器优于 Nvidia 和 AMD 的方案,但首次编译耗时过长,gpt-oss 训练配方首步编译用了 27 分 17 秒。FlexAttention 测试通过 96 个用例中的 89 个,7 个失败均因编译超时而非数值错误。

    证明了自己。Anthropic正在Trainium2和Trainium3上运行生产推理和RL rollout。从历史上看,Trainium在推理方面表现出色,但并非研究训练的最佳选择。在推理中,模型架构的变化速度比训练慢得多;在训练中,研究人员会对模型架构进行大量不同的实验和消融,需要一个覆盖广泛API表面的技术栈。过去,这正是Trainium的短板所在。 AWS Neuron团队正积极努力改变这一缺陷,最大的转变是迈向一流的原生PyTorch训练体验。在训练循环中到处撒xm.step()、与定制的XLA式执行模型较劲的日子已经一去不复返。Trainium现在以PyTorch用户所期望的方式运行PyTorch——eager模式,配合torch.compile和标准API。 SemiAnalysis工程团队过去几周一直在试用Trainium3机架,发现体验很棒——我们很喜欢它整体的发展方向。需要说明的是,它还不完美,我们自己也遇到了几个bug。它远未达到CUDA生态的成熟度,但方向是对的。他们的团队借助智能体编码正在快速推进。 此外,与其他加速器公司不同——我们曾不得不费尽周折才能让他们

    匹配字段正文

星期四

  1. Browser Use

    Browser Use 盘点 2026 年最佳浏览器 Agent MCP 服务器

    Browser Use 发布 2026 年浏览器 Agent MCP 服务器盘点,把这类服务器分为驱动和委托两种模式,并逐一评测 Browser Use Cloud MCP、Browser Use 开源 MCP、Hyperbrowser MCP 和 agent-browser chat 四款。作者在 100 个 BU Bench V2.1 任务的对比评测中发现,四个驱动类工具每个任务的中位输入 token 消耗在 2.1M 到 6.7M 之间,全部计入编码 Agent 的上下文。文中还给出各服务器的安装命令、模型选择、计费方式与已知限制,并说明长任务、并行任务和结构化输出场景更适合委托模式。

    ne. Its tool description calls it a last resort. For long tasks I'd reach for it first. The model is yours. In practice that means an OpenAI key, an OpenAI-compatible endpoint, or AWS Bedrock with MODEL PROVIDER=bedrock. The docs also mention an Anthropic key, but the server code doesn't read it; on the OpenAI path, without OPENAI API KEY the agent tool fails. The default config it writes on first run uses gpt-4.1-mini, and on Bedrock that config model wins, so also set BROWSER USE LLM MODEL to

    匹配字段正文

星期日

  1. 腾讯云开发者社区

    《Agent 工程实战八讲》导读:从能跑到敢上线的工程方法

    腾讯云开发者社区发布《Agent 工程实战八讲》导读,围绕如何把能调用模型与工具的原型升级为可完成业务任务、解释失败、控制成本并持续迭代的系统。全系列以立案助理 Agent 和术后随访 Agent 两个虚构教学案例贯穿,覆盖任务契约、推理与协作、上下文与记忆、工具可靠执行、观测与重放、评测与校准、安全边界、生产运营八个主题。文中强调模型能给出下一步不等于系统能兑现业务结果,示例字段、预算与数字均为教学演算,不构成法律意见。

    in the Middle、Judging the Judges)、协议规范(MCP 固定到 2025-11-25 版本、W3C Trace Context、OpenTelemetry、RFC 8693 与 RFC 9700)、厂商与标准组织的工程文档(Anthropic 的 Agent 与上下文工程文章、LangGraph、Temporal、Stripe、AWS、PostgreSQL、Google SRE、OWASP、NIST)。论文结果只在原研究任务、模型和预算下成立;厂商文档用于确认机制,不代表跨产品的能力保证;动态 API、模型价格和产品套餐不作为长期前提。 法律、司法解释与部门规范性文件:民事诉讼法、登记立案规定、在线诉讼规则、最高人民法院人工智能司法应用意见、个人信息保护法、医疗卫生机构网络安全管理办法、互联网诊疗监管细则、卫生健康行业人工智能应用场景参考指引。它们在文中只用于说明 Agent 的职责边界、人工确认要求与数据边界,正文分别标注文件性质,相关表述一律是本系列对规则的工程理解,不构成法律意见;具体适用仍需法务与业务负责人判断。 作者的参考设计与演算:两个案例、全

    匹配字段正文

星期日

  1. OpenAI Developers精选

    OpenAI 开发者分享如何用 Astra 在 Codex 中构建游戏

    OpenAI 开发者撰文介绍如何用 Astra 在 Codex 中构建游戏,并以太空探索游戏 Void Explorer 为例,展示从概念图、架构设计到地形流式加载与性能测试的完整流程。Void Explorer 包含 2,048 个恒星系和超过 10,000 颗程序化生成的行星,行星最大可与地球相当。作者还提到用同一方式开发了水面渲染的 Sunwake 和 2D 动作 RPG Hollowflux,并可通过 Sites 插件发布为浏览器游戏。

    player and enemies. Water also affects combat: an eel’s discharge travels through connected water, so stepping onto dry stone protects the player from that discharge. Hollowflux draws its game art in code, with water that reacts to movement and combat. Building and sharing games What I like about working with Astra is that I can start with the experience I want, use images to make the visual direction concrete, and give feedback from actually playing. A complaint about a disappearing planet can

    匹配字段正文

星期五

  1. Artificial Analysis

    Nano Banana 2.1 在生产力与知识工作用例排名第 2

    Artificial Analysis 的用例评测显示,Nano Banana 2.1 在 Productivity & Knowledge Work 类别排名第 2,仅次于 GPT Image 2(high),高于两个 GPT Image 2.5 模型,较 Nano Banana 2 的第 8 名明显上升,与其在 Layout 和 Text Rendering 上的提升一致。该类别覆盖图表、信息图、图表和幻灯片。它在 Live-Action Film 用例升至第 3,Retail & Ecommerce 排名第 3,Architecture & Real Estate 是弱项,排在第 7。

    behind only GPT Image 2 (high), up from 8 for Nano Banana 2. That lines up with its Layout and Text Rendering gains. Its largest use-case gain is Live-Action Film, now 3, which draws on its Human Anatomy. It is also 3 for Retail & Ecommerce. Architecture & Real Estate is the weak spot, at 7. ➤ Productivity & Knowledge Work covers diagrams, infographics, charts and slides. ➤ Live-Action Film covers cinematic scenes, film stills, storyboards and character sheets. ➤ Retail & Ecommerce covers produ

    匹配字段正文

星期四

  1. Anthropic:Claude.dev 开发者博客

    Claude Code mods 入门:从空文件夹构建第一个 mod

    Anthropic 发布 Claude Code mods 入门教程,mod 是运行在 Claude Code 会话内的 JavaScript 或 TypeScript 文件,可监听事件、改写行为或绘制自定义 UI,本质是插件内的 hooks。教程从空文件夹构建约 80 行的 Token Weather,在提示词上方实时显示上下文窗口占用,并演示 Blast Radius 和 Replay Theater 两个更复杂的 mod。需要 Claude Code 2.1.287 或更高版本,mods 默认开启,完整代码在 anthropics/claude-code-playground。

    is in the public anthropics/claude-code repository under mods/, so you can read how the team builds them. Token Weather reads how full the context window is after each turn and draws one line above the prompt: a weather icon, the percentage, the tokens used out of the window, a small chart of recent turns, and how much the last turn added. Here it is in a real session. Each turn reads more files, and the band fills from ☀ Clear to ☂ Showers to ☇ Storm: The shortcut: let Claude build it You can

    匹配字段正文

星期四

  1. SemiAnalysis

    SemiAnalysis 发布 ClusterMAX 3.0 GPU 云评级,覆盖 77 家 neocloud

    SemiAnalysis 发布 ClusterMAX 3.0,对 77 家 neocloud 做全面评测,市场覆盖范围从 2.0 版的 209 家扩大到 323 家,并访谈了 200 多名终端用户。Nebius 与 CoreWeave 同列 Platinum,Google Cloud 与 Oracle 进入 Gold,Azure 降至 Silver,Crusoe 降至 Bronze,全球仅 19 家 neocloud 获得奖章评级。评测分审计、性能、可靠性三阶段,涵盖 GPU 计算、网络、存储、编排、监控与故障注入,并新增 Bronze 与 Underperforming 之间的 Participation Ribbon 档。

    etwork NAD, for hardware-offloaded Open vSwitch; rdma ib / rdma roce: rdma/ib, rdma/roce, or nvidia.com/rdma , with one NAD per rail or a host-network fallback; Provider-specific: AWS EFA (vpc.amazonaws.com/efa and libfabric), DOKS (rdma/fabricN with roce-net-fabricN@fabricN), and GKE DRANET (DRA claim templates and pod resourceClaims) Device setup and the NCCL plugin on top of it can change job performance. On Google’s GB300, the built-in NCCL library picked an unroutable link-local GID and hun

    匹配字段正文

星期三

  1. Anthropic:Claude.dev 开发者博客

    Anthropic 如何用 Claude 两周让 claude.ai 提速 3 倍

    Anthropic 在两周冲刺中把 claude.ai 和 Claude 桌面应用的核心体验提速约 3 倍,75 分位下全新加载的可输入页面从 3.1 秒降到 0.55 秒,新建 Claude Code 会话从 0.8 秒降到 0.3 秒,加载 Claude Cowork 云会话从 2.6 秒降到 0.73 秒。团队用 Claude Tag(beta)在单个 Slack 频道内驱动流程,合并了三千多个改动且没有出现面向客户的事故或回滚。做法上,Claude 通过 Datadog MCP server 分析使用数据,锁定占 95% 用户活动的四条路径,并建立指令计数、React commit、样式重算等可在实验室复现的基准,再以 CI 棘轮和功能开关控制风险。

    Side-by-side recording of the claude.ai sidebar loading. Before, the rows arrive late and rearrange: ten rows jump, nine appear and four vanish. After, the rows fill in where they will stay, and nothing moves.

    cording — it’s Chrome resizing the page, not the handoff from the static composer to the real one (that measured 0 px on all 49 of your loads today). On the new-tab page, Chrome draws its own 56 px footer below the page (“Managed by anthropic.com · Customize Chrome”). When the tab navigates to claude.ai the footer goes away and the page gets 56 px taller, but only 100 ms after our first paint; /new puts the greeting and composer 18% of the page height from the top, so they drop 0.18 × 56 ≈ 10 px

    匹配字段正文

星期一

  1. LiveKit 产品与工程博客

    LiveKit 对比 Pipecat:实时语音与视频 AI 智能体开源框架怎么选

    LiveKit 官方博客对比了实时语音与视频 AI 智能体两大开源框架 LiveKit Agents 与 Pipecat,指出前者基于自家开源 WebRTC 与 SIP 服务、抽象层级更高,后者不预设传输层、需自行逐级组装 pipeline。文章还说明 TEN Framework、Dograh、Vision Agents、Vocode 的定位,并从语言支持、维护活跃度、上手速度和生产就绪度四方面给出选型建议。

    s with their own customers: Salesforce, Zocdoc, SAP, telli. Pipecat's lean toward companies that build tooling or reference architectures for other developers: NVIDIA's Blueprint, AWS, Anthropic 3. Can I get a working agent going today? When evaluating each framework it's important that you can easily build (and reason about the code for) a voice or video agent. Given AI-augmented development, a developer should be able to get an agent working in a day with either. Independent write-ups comparin

    匹配字段正文

星期六

  1. n8n Blog

    n8n 解析 AI 智能体如何用反思模式在生产环境中自我纠错

    反思模式让 AI 智能体通过生成、反思和修正三个阶段检查错误并改善输出。文章比较单模型自我反思、多智能体反思和工具增强反思,并指出应设置迭代停止条件,以控制模型 token 消耗、计算成本和延迟。n8n 可通过多个 AI 智能体节点和子工作流实现生成与批评流程,并跟踪 token 消耗及成本。

    to use a tool-augmented reflection pattern, the model may access external systems, such as a search engine, to complete its evaluation. The model catches and catalogs potential flaws that need to be fixed before responding to the customer. 3.Refine The agent feeds its original draft and critique back into the generative model. It uses the additional context to revise its response. It corrects errors and removes irrelevant information to produce a higher-quality output. It’s important for the ag

    匹配字段正文

星期三

  1. Ahead of AI精选

    GPT-6 Astra、循环 Transformer 与隐藏推理链解析

    作者实测 GPT-6 Astra 后,分析其性能、计算机使用能力,以及循环 Transformer 是否会隐藏推理链。文章解释了循环 Transformer 通过重复使用相同权重增加有效深度,并指出 Astra 采用该架构仍未获官方确认,也没有充分证据表明循环机制会导致推理链更难监控。

    reasoning There’s a useful distinction between storing information and using it to solve a problem. For instance, the Beyond Parameters: Exploring Virtual Logic Depth for Scaling Laws paper from June 2025 investigates this by measuring memorization and reasoning in an LLM separately. First, in the memorization experiments, looping leaves the amount of stored information nearly unchanged when the parameter count stays fixed. Increasing the number of distinct parameters does increase this capacity

    匹配字段正文

星期日

  1. 張小珺 Xiaojùn

    播客解读 Kimi K3 技术报告并串联十余篇相关论文

    这期学习型播客逐步解读 Kimi K3 技术报告,并由 Yutao 串联十余篇相关论文。节目旨在帮助听众理解其中的技术之美,但提醒 Yutao 的语速很快。

    This episode is a learning‑focused podcast. We walk through the Kimi K3 technical report, hoping to appreciate “the beauty of technology” together. Yutao draws connections to more than ten related papers as he breaks down the report. Fair warning: he speaks really fast. https://t.co/7D9O7cd5ff

    匹配字段正文

星期四

  1. The Register

    实测16个模型识别蘑菇:最佳模型首猜准确率仅65%

    波兰软件工程师 Piotr Migdał 用1040张蘑菇照片测试16个模型,表现最好的 Gemini-3.8-flash 首次猜测准确率为65%,前五猜测命中率85%。Qwen3.8-27b 表现最差,首猜准确率13%,并把有毒蘑菇误判为可食用达36%。Migdał 指出危险误判并非随机,例如把致命丝膜菌认成鸡油菌,他警告不要因为 AI 说安全就吃下蘑菇。

    tonking Stingray' beta swims out: Deeper Rust 'oxidization' plus LLM speech-to-text GNOME 51 is here, and Ubuntu interim releases are getting interesting again; Revive Raskin's 3 laws of software with humane work that considers a dev's duty of care All this, and angry NeoVim users; Firefox 157: Could bold new look be just what Mozilla needs? Yet another new version of Firefox, with a significant reskin; KDE turns 30 and someone's brought an AI-native desktop proposal Akademy talk imagines Plasma

    匹配字段正文

星期一

  1. Amazon Science

    Amazon Science 介绍如何用 Verus 开发可证明正确的 Rust 代码

    Amazon Science 发文介绍开源自动程序验证器 Verus,它用数学规格机械检查 Rust 代码在所有输入下是否符合预期,弥补传统测试难以覆盖的边界情况。开发者可直接在 Rust 源码中用类 Rust 语法写前置与后置条件,通常不到一秒即可获得反馈,AI 智能体也能参与证明生成。Verus 还能对 Rust 的 unsafe 代码块和自定义锁方案的并发代码做数学验证,亚马逊已用它证明 Nitro Isolation Engine 关键原语及内部关键基础设施的正确性,开源项目如证书验证库、数据格式解析器和 Kubernetes 控制器也已采用。

    ion of Rust's "unsafe" code blocks and concurrent code with custom locking schemes, re-establishing machine-checked safety guarantees for performance-critical implementations like AWS's Nitro Isolation Engine; Amazon uses Verus to prove correctness of key primitives in critical infrastructure, and the tool has been adopted by open-source projects including certificate validation libraries, data format parsers, and distributed systems like Kubernetes controllers Many open-source and industry soft

    匹配字段正文

星期五

  1. LMSYS Blog精选

    LMSYS 公开 infer-forge:围绕 SGLang 的 Harness、Loop 与 Graph 工程方法

    LMSYS 发布 infer-forge 方法论文,介绍围绕 SGLang 的推理工程系统,由 MonoRepo、Harness、Task Loop 和 Task Graph 四层结构组成,用于让跨仓库的推理优化工作可复现、可验证。该系统为内部工程系统,并非 SGLang 或 LMSYS 官方组件,目前不开源,文章公开的是构建方法论,供团队交给 AI 编码工具并结合自身系统上下文搭建适配实现。文中给出使用记录:一位工程师 4 月至 7 月的在飞任务峰值从 2 个升至 9 个,DeepSeek-V4-Pro 服务项目中 38 个可独立验证的任务节点被组织成任务图。

    The inference deployment space stacks five layers of static configuration. Model shows Ling, Qwen, DeepSeek, Kimi, GLM, and MiniMax. Serving Scenario runs Modality (text, image, video) into Traffic Shape (input and output length, media count, resolution, QPS, concurrency, cache reuse) into SLO (TTFT, TPOT, throughput, E2E latency). Serving Topology separates Deployment Architecture—Colocated PD, PD Disaggregation, and EPD Disaggregation, each listing the node roles it is built from — Prefill and Decode together, then Prefill and Decode as separate roles, then Encoder alongside them — from Parallelism—TP, PP, DP, and EP—because the two are chosen independently. Versioned Runtime Profiles is a stack of tabbed cards labelled Service A rev. 12, Service B rev. 7, and Service C rev. 21, plus a fourth paler card behind them all, blank and showing only its top edge, whose narrow tab carries an ellipsis for the profiles not drawn, the front card holding an Engine Configuration and a Container I

    le are stable enough to guide future work. Standardization follows proven practice; it does not attempt to predict every path in advance. 4.2.2 Starting Context Starting Context draws the line between known state and assumption. A Task may begin from a blank state, a prepared environment, or an upstream result. What matters is that the source and verification status of that state remain explicit. Custom Setup records conditions prepared for the current Task, such as the model, container image, d

    匹配字段正文

星期三

  1. Trail of Bits Blog

    Trail of Bits 实测:GPT 5.6-Cyber 三次逃出 QEMU/KVM 虚拟机

    Trail of Bits 的 Artem Dinaburg 在 Patch the Planet 项目中获得 GPT 5.6-Cyber 预览权限,让它在 CTF 任务中逃出运行在 Debian 12、AMD Zen3 上的 QEMU/KVM 虚拟机,结果它三次成功逃逸。第一次利用几周前披露的 Januscape(CVE-2026-53359)内核漏洞;更新内核后,它组合 libslirp 4.7.0 的 CVE-2026-9539 与一个未分配 CVE 的修复提交实现任意内存读写;在手动重建最新上游 QEMU 和 libslirp 后,它又串联三个 0-day 和一个未进入发行版内核的已修复漏洞完成逃逸。作者指出,该智能体在约 12 小时的时间跨度内跨多次压缩和子智能体调用保持持续作业,能自行回溯失败路径、拉取论文、编写 oracle 和最小复现;他建议改用 Firecracker 这类最小攻击面的虚拟化方案,并加强最小权限、日志与主动监控。

    ith a minimal attack surface and a focus on security, like Firecracker . I had the AI agent run against Firecracker. It was able to hardlock the machine due to more Linux kernel flaws (all patched in upstream), but could not successfully escape. It may have, given even more time, but Firecracker is obviously a substantially harder target. In general, we have to become much more attentive to security fundamentals: least privilege (regarding network access, credentials, available features, etc.),

    匹配字段正文

星期五

  1. Hugging Face

    使用 Strands Agents、LeRobot 与 Hugging Face Storage Buckets 在一处完成录制、训练和部署

    Strands Robots 将 LeRobotDataset 的录制、同步、流式训练和实体机器人部署整合到同一 Robot() 工作流,并让新演示数据返回同一 Storage Bucket。Xet 按字节去重,仅上传变化的数据块;stream_dataset() 可从 Hub 逐帧读取远程 Parquet 与 MP4 分片,无需完整下载。Bucket 仅支持流式读取且不保留修订记录,真实部署还需隔离数据与凭据、限制智能体权限并只加载可信组织的模型。

    mulation path) Python 3.12+, on Linux or macOS (Apple Silicon supported for the MuJoCo backend). A Strands-compatible model provider for the agent's reasoning. Amazon Bedrock with AWS credentials, the Anthropic API , OpenAI, or Ollama running locally. Strands Robots with the dataset extras: uv pip install -U "strands-robots[sim-mujoco,lerobot] =0.5.1" . The lerobot extra pulls in LeRobot ( =0.6.1), datasets , av , and torchcodec , so recording and video decode both work without further setup. Re

    匹配字段正文

星期五

  1. NVIDIA Developer · Generative AI精选

    NVIDIA AI Red Team 总结部署更安全 AI 智能体的四种方式

    NVIDIA AI Red Team 在六个月内评估了多个 AI 智能体,归纳出四类反复出现的失效模式:缺少访问控制、工具允许任意代码执行、缺少网络出口控制、密钥以明文暴露。团队指出基于提示词的护栏和 LLM-as-a-judge 模式常被社会工程、渐进式操纵和恶意包安装等合法工作流绕过,有效防护需要模型控制面之外的确定性控制,包括严格访问控制、Docker 或 NVIDIA OpenShell 等加固沙箱、默认拒绝的网络出口以及通过专用密钥管理器让密钥远离智能体。

    t be carefully secured. While frontier models make adversarial manipulation more difficult, with sufficient time and expertise, nearly all of them can still be subverted. Common flaws we observed include: weak access control (permitting any user to access the agent), execution and file-write tools that create opportunities for RCE, insufficient network egress controls permitting data exfiltration and reverse shells, and secrets in plaintext inside the execution environment accessible by the agen

    匹配字段正文

星期四

  1. Figma AI / Agent / Make

    Figma 如何用智能体守护内部系统安全

    Figma 安全工程团队公开了其内部安全智能体系统,用 RAG 检索历史告警与调查上下文,再由 Tines 上的智能体调用 Okta、Wiz、Slack、Panther 等工具完成告警分诊,并可查询安全数据湖、提交修复 PR。团队称复杂告警的解决时间缩短约 70%,值班呼叫量因 AI 驱动的严重度降级减少 20%,端点软件审批请求减少 25%。系统将记忆分为案例记忆、引导记忆和过程记忆三层,并用确定性护栏限制智能体行为,例如所有 PR 自动设为草稿。

    A split-background abstract illustration. The left side is black with a blue diamond, an orange floral motif, scattered orange squares, and bold graphic accents in magenta and olive green. The right side is teal with stacked horizontal pill shapes in orange, blush pink, and dark teal, punctuated by small blue and pink circles.

    mory. It’s completely changed how our security team works. The RAG layer: Giving alerts a memory The first thing we built was a retrieval-augmented classification system on top of AWS Bedrock Knowledge Bases and Amazon Kendra. Again, our initial goal was just to surface historical context about what had happened the last time the same alert fired, and maybe suppress duplicate alerts. When a Panther alert fires, our Lambda handler converts it into a standardized document and indexes it into Kendr

    匹配字段正文

星期一

  1. Browser Use

    Browser Use 如何把云浏览器成本降到三分之一并加快启动

    Browser Use 重建了云浏览器基础设施,把每个浏览器会话从每小时 0.06 美元降到 0.02 美元,并让新会话在 1 秒内启动。它改用 Firecracker 在普通 EC2 上为每个会话运行独立微型 VM,通过 2MB 大页、自定义 userfaultfd 处理等把恢复 VM 到可接受命令的时间从 9.8 秒降到 3.1 秒,页错误处理次数从约 10 万次降到约 1100 次。VM 冷启动低于 400ms,公开 API 的浏览器创建延迟为 p50 825ms、p99 1.35s,该基础设施已上线。

    Browser Use: how we made cloud browsers 3x cheaper — every browser is its own Firecracker microVM on regular EC2, at $0.02 per browser hour with sub-400ms VM cold start and headless stealth.

    That is the unusual part. Firecracker is normally run on bare-metal servers, where you rent the whole physical machine. To reduce customers' cost, we run it on regular EC2, where AWS has already put your server inside a VM. This should be slow. Nested VMs make memory and CPU operations more expensive, and Chromium takes time to start. This post is about how we made this setup fast and efficient. But first, why did we rebuild our infrastructure? When we first built our browser infrastructure on

    匹配字段正文