乐于分享
好东西不私藏

在哒AI日报 | 第20期:Google Gemini个性化AI图像生成向美国免费用户开放

在哒AI日报 | 第20期:Google Gemini个性化AI图像生成向美国免费用户开放
2026年6月30日AI日报
📋 今日新闻索引
1. Google Gemini个性化AI图像生成向美国免费用户开放
2. Anthropic与加州政府达成Claude半价合作协议
3. 韩国科技巨头承诺投入超5500亿美元缓解"内存末日"
4. AI排行榜平台Arena年化营收突破1亿美元
5. Cursor推出移动端App,AI编程进入手机时代
6. TIDAL打击AI生成音乐,切断变现渠道
7. Ford在AI质检失败后重新雇佣资深工程师
8. OpenAI展示Codex专用硬件设备
9. 美国议员拟立法禁止AI公司出售用户健康数据
10. 中国智谱AI发布GLM-5.2,网络安全能力逼近Mythos
────────────────────

1. Google Gemini个性化AI图像生成向美国免费用户开放🔥🔥🔥🔥🔥 

热度指数:★★★★★

【摘要】Google宣布将Gemini的个性化AI图像生成功能向美国所有免费用户开放,此前该功能仅限付费订阅用户使用。
【核心事件】Google于6月29日宣布,Gemini应用的"Personal Intelligence"图像生成功能(基于Nano Banana模型)现向美国所有符合条件的用户免费提供,无需Plus/Pro/Ultra订阅。
【关键细节】• 该功能利用用户Google账户数据(Gmail、Google Photos、YouTube、搜索等)生成个性化图像• 用户无需详细描述偏好,Gemini可自动理解兴趣• 可从Google Photos中拉取用户真实照片• 该功能为可选项,用户可选择允许Gemini访问哪些应用• Gemini月活跃用户已超7.5亿
【深度分析】市场化分析:Google此举旨在通过免费策略扩大用户基数,与ChatGPT和Claude争夺消费者市场。将高级AI功能从付费墙后释放,反映了AI图像生成领域的激烈竞争。7.5亿月活用户的规模优势使其在数据飞轮效应上具备独特竞争力,但也引发了隐私方面的讨论——用户需要授权多个Google应用的数据访问权限。

【原文内容】

Google announced on Monday that the Gemini app is now offering its personalized Nano Banana-powered image generation feature to a broader audience. Starting today, all eligible users in the U.S. can access the feature for free, a service that was previously only available to Plus, Pro, and Ultra subscribers.

Google initially announced that Gemini's Personal Intelligence feature would get Nano Banana-powered image generation back in April, allowing users to create images that reflect their unique interests. This means that images can be generated based on Gemini's understanding of your likes and preferences without you having to specify them in your prompt. Gemini utilizes data from your Google account connections — such as Gmail, Google Photos, YouTube, and Search — to achieve this.

For example, instead of saying, "Create an illustration of me and my favorite things, such as coffee and baking," you can simply request, "Create an illustration of me and my favorite things."

Gemini can also pull actual images of you from Google Photos, so you don't need to manually upload photos.

Google initially rolled out the Personal Intelligence feature earlier this year, making it widely available to all U.S. users in March. The company recently expanded this functionality to users in India and Japan.

Personal Intelligence is an opt-in feature, allowing you to decide which apps Gemini can access. Once enabled, it is set as the default for every prompt, but you can disable it using a new toggle in the Tools menu.

Additionally, last month, Google announced several upcoming updates for the Gemini app, including a new "Daily Brief" feature, a revamped interface, access to AI video model Gemini Omni, and a personal AI agent named Gemini Spark.

Notably, Google's AI chatbot Gemini surpassed 750 million monthly active users (MAUs) earlier this year, reinforcing its position as a major player in the AI space.

【中文翻译】

Google于周一宣布,Gemini应用现向更广泛的用户群体提供基于Nano Banana模型的个性化AI图像生成功能。从今天起,美国所有符合条件的用户均可免费使用此功能,此前该服务仅面向Plus、Pro和Ultra订阅用户开放。
Google早在今年4月就宣布Gemini的"Personal Intelligence"功能将获得Nano Banana驱动的图像生成能力,允许用户创建反映其独特兴趣的图像。这意味着Gemini可以根据对用户喜好和偏好的理解来生成图像,无需用户在提示词中明确说明。Gemini通过连接用户的Google账户数据——如Gmail、Google Photos、YouTube和搜索记录——来实现这一功能。
例如,用户无需说"创建一幅包含我和我最喜欢的东西的插画,比如咖啡和烘焙",只需简单地说"创建一幅包含我和我最喜欢的东西的插画"即可。
Gemini还可以从Google Photos中提取用户的真实照片,因此无需手动上传。
Google在今年早些时候推出了Personal Intelligence功能,3月份向所有美国用户广泛开放。该公司最近将这一功能扩展到了印度和日本用户。
Personal Intelligence是一个可选功能,用户可以决定允许Gemini访问哪些应用。启用后,它将成为每个提示的默认设置,但用户可以通过工具菜单中的新开关来禁用它。
此外,上个月Google宣布了Gemini应用的几项更新,包括全新的"每日简报"功能、 revamped界面、AI视频模型Gemini Omni的访问权限,以及名为Gemini Spark的个人AI助手。
值得注意的是,Google的AI聊天机器人Gemini在今年早些时候月活跃用户突破了7.5亿,巩固了其作为AI领域主要参与者的地位。

【参考链接】

• https://techcrunch.com/2026/06/29/geminis-personalized-ai-image-generation-is-now-free-for-u-s-users/

────────────────────

2. Anthropic与加州政府达成Claude半价合作协议🔥🔥🔥🔥🔥 

热度指数:★★★★★

【摘要】加州州长与Anthropic达成"首创性"合作协议,全州政府机构可以半价使用Claude AI工具,同时获得培训和技术支持。
【核心事件】加州州长Gavin Newsom与Anthropic签署协议,允许加州所有州政府机构和地方政府以50%折扣使用Claude AI聊天机器人,用于文档起草、信息分析等日常工作。
【关键细节】• 这是"首创性"的政府-AI合作模式• 包含免费劳动力培训、技术援助和Anthropic开发者的工作流指导• Newsom此前在3月签署行政令,推动AI在政府中的负责任使用• 与此同时,Anthropic与联邦政府关系紧张——此前因拒绝允许将Claude用于监控和自主武器,被相关部门标记为"供应链风险"• 该协议体现了州级政府与联邦政府在AI政策上的分歧
【深度分析】世界化分析:这一合作标志着AI在公共服务领域应用的重大突破。加州作为美国最大经济体,其AI政府采购模式可能成为其他州乃至其他国家政府的参考模板。值得注意的是,Anthropic在联邦层面遭遇挫折后转向州级合作,显示了AI公司在政府市场策略上的灵活调整。这也反映出全球范围内,政府层面对AI工具的采纳正在加速。

【原文内容】

Governor Gavin Newsom (D-CA) and Anthropic have made a deal that allows California government agencies to use Claude at a discounted price. This agreement comes at a time when businesses are struggling to manage the hefty costs of enterprise subscriptions to AI tools.

Under the deal, all state agencies and local governments will have access to Claude, Anthropic's AI chatbot, as well as training and support from Anthropic. A press release from the Governor's office says that Claude will help state employees draft documents and analyze information.

"AI should not replace the human work of government; it should help our workers move faster, solve problems more effectively, and deliver better results for Californians," Governor Newsom said in a statement.

This deal follows Newsom's March executive order that intends to accelerate the use of AI "to make government more efficient" while also maintaining stronger safety standards.

"While others in Washington are designing policy and creating contracts in the shadow of misuse, we're focused on doing this the right way," Newsom said at the time.

As Anthropic forges a closer relationship with the state of California, the federal government has made an enemy out of the OpenAI rival. Earlier this year, Anthropic and the U.S. Department of Defense clashed over a contract that would give the government agency permission to deploy Claude for any lawful use. Anthropic sought to explicitly carve out protections that prevent the government from using its technology to surveil Americans or deploy autonomous weapons without human oversight. But Defense Secretary Pete Hegseth refused, and the agency signed a deal with OpenAI instead. The government went as far as to declare Anthropic a "supply-chain risk," preventing the company from working with any other Pentagon contractors.

【中文翻译】

加州州长Gavin Newsom与Anthropic达成了一项协议,允许加州政府机构以折扣价使用Claude。该协议签署之际,各企业正努力应对AI工具企业订阅的高昂成本。
根据协议,所有州政府机构和地方政府都将获得Claude——Anthropic的AI聊天机器人的访问权限,同时还将获得Anthropic的培训和支持。州长办公室的新闻稿表示,Claude将帮助州政府雇员起草文件和分析信息。
Newsom州长在声明中表示:"AI不应取代政府的人工工作;它应该帮助我们的工作人员更快地行动、更有效地解决问题,并为加州人提供更好的服务。"
该协议是Newsom在3月签署的行政令的后续,该行政令旨在加速AI的使用"以提高政府效率",同时维持更严格的安全标准。
Newsom当时表示:"当华盛顿的其他人在滥用的阴影下设计政策和制定合同时,我们专注于以正确的方式做事。"
在Anthropic与加州建立更紧密关系的同时,联邦政府却将这家OpenAI的竞争对手视为对手。今年早些时候,Anthropic与国防部就一份允许该机构将Claude用于任何合法用途的合同产生分歧。Anthropic试图明确设定保护措施,防止政府利用其技术监控美国公民或在没有人类监督的情况下部署自主武器。但国防部长拒绝了这一要求,转而与OpenAI签署了协议。政府甚至将Anthropic列为"供应链风险",阻止该公司与任何其他国防部承包商合作。

【参考链接】

• https://techcrunch.com/2026/06/29/anthropic-and-gov-newsom-forge-deal-allowing-california-government-to-use-claude-at-half-price/

────────────────────

3. 韩国科技巨头承诺投入超5500亿美元缓解"内存末日"🔥🔥🔥🔥🔥 

热度指数:★★★★★

【摘要】三星和SK海力士计划投资5180亿美元在韩国西南部建设四座新内存芯片工厂,韩国企业AI相关总投资承诺超过9000亿美元。
【核心事件】韩国两大内存芯片巨头三星和SK海力士宣布大规模投资计划,以应对全球AI建设带来的"内存末日"(RAMageddon)——即全球内存芯片短缺。
【关键细节】• 5180亿美元用于建设4座新内存工厂 + 520亿美元用于HBM封装中心• 3560亿美元用于AI数据中心建设(到2035年)• 韩国企业AI相关总投资承诺超9000亿美元• 三星另宣布未来十年投资约1.7万亿韩元(2655万亿韩元)• 韩国总统李在明称2026年是韩国成为"不可替代"产业强国的关键之年• 现有龙仁和平泽芯片设施"已达到极限"
【深度分析】经济化分析:这一投资规模史无前例,反映了AI基础设施建设对上游芯片供应链的巨大拉动效应。美国四大科技巨头今年AI基础设施投资合计将达6500亿美元,而韩国仅内存芯片就投入5180亿美元,可见AI算力需求的爆发式增长。韩国正试图通过"全栈"布局(从内存到数据中心)巩固其在全球AI供应链中的核心地位。对全球半导体产业格局而言,这将加剧先进制程和封装技术的竞争。

【原文内容】

The world's two largest memory chip companies plan to invest $518 billion (~800 trillion won) to build four new memory fabs in southwestern South Korea, a region that has historically attracted little semiconductor investment.

The announcement is part of the country's sweeping national investment plan spanning semiconductors, AI data centers, and physical AI, which was unveiled at a presidential briefing on Monday, with the chairmen of Samsung and SK Hynix in attendance. The plan breaks down into three buckets. In the memory chip bucket is $518 billion for four new memory fabs in the southwest, plus $52 billion for an HBM (high bandwidth memory) packaging hub in the central region. Then there's another $356 billion (550 trillion won) for AI data centers to be built by Korean tech and energy behemoths such as SK, GS, and Naver through 2035.

All told, South Korean tech companies have committed to spend over $900 billion on AI and the demands for chips it is creating. With this, the nation hopes to catapult itself into becoming more of an AI power player than it already is. Currently, Samsung and SK Hynix (along with U.S. memory chip maker Micron) are all enjoying record demand from what's been called RAMageddon, a worldwide shortage of memory chips caused by the AI buildout.

"Semiconductors, physical AI, and AI data centers are the triple axis for South Korea's next industrial era," President Jae Myung Lee said in a televised address Monday, calling 2026 the year South Korea must establish itself as an "irreplaceable" industrial power.

Lee said existing chip facilities in Yongin and Pyeongtaek, the heart of South Korea's semiconductor belt just south of Seoul, have "already reached their limits," and urged companies to accelerate investment in the southwest, hoping to spread the AI wealth beyond the nation's capital. "We must secure overwhelming production capacity in advance," he said.

Yet, Lee pushed back against media reports that the government had pressured companies into the investments, reportedly saying the decisions reflected the companies' own judgment. "The government's role is to invest its capabilities so that companies can invest without losses and with better prospects," he was quoted as saying.

Samsung separately published a press release Monday, announcing plans to invest 2,655 trillion won (~$1.7 trillion) over the next decade, with 425 trillion won earmarked for the Honam region, the southwestern corner of the Korean peninsula.

【中文翻译】

全球两大内存芯片公司计划在韩国西南部投资5180亿美元(约800万亿韩元)建设四座新的内存芯片工厂,该地区历史上很少吸引半导体投资。
这一公告是该国涵盖半导体、AI数据中心和物理AI的全面国家投资计划的一部分,该计划于周一在总统简报会上公布,三星和SK海力士的董事长均出席。该计划分为三个部分:内存芯片方面,5180亿美元用于西南部四座新内存工厂,加上520亿美元用于中部地区的HBM(高带宽内存)封装中心;另外还有3560亿美元(550万亿韩元)用于韩国SK、GS和Naver等科技和能源巨头到2035年建设的AI数据中心。
总计,韩国科技企业已承诺在AI及其带来的芯片需求上投入超过9000亿美元。韩国希望借此将自己提升为更具影响力的AI强国。目前,三星和SK海力士(以及美国内存芯片制造商美光)都在享受创纪录的需求,这被称为"内存末日"(RAMageddon)——由AI建设引发的全球内存芯片短缺。
韩国总统李在明周一在全国电视讲话中表示:"半导体、物理AI和AI数据中心是韩国下一个工业时代的三轴",并称2026年是韩国必须确立自己"不可替代"产业强国地位的一年。
李在明表示,位于首尔以南的韩国半导体带核心——龙仁和平泽的现有芯片设施"已达到极限",敦促企业加速在西南部的投资,希望将AI财富扩展到首都以外。"我们必须提前确保压倒性的产能,"他说。
不过,李在明反驳了媒体报道中关于政府向企业施压要求投资的说法,据报表示这些决定反映了企业自身的判断。"政府的角色是投入其能力,使企业能够无损失、以更美好的前景进行投资,"他说道。
三星周一另外发布新闻稿,宣布计划在未来十年投资2655万亿韩元(约1.7万亿美元),其中425万亿韩元专门用于韩国西南角的湖南地区。

【参考链接】

• https://techcrunch.com/2026/06/29/south-korean-tech-giants-commit-over-550b-to-ease-ramageddon/

────────────────────

4. AI排行榜平台Arena年化营收突破1亿美元🔥🔥🔥🔥 

热度指数:★★★★

【摘要】源自UC Berkeley的AI模型评测平台Arena,在推出商业服务仅8个月后就达到1亿美元年化营收。
【核心事件】AI排行榜提供商Arena(前身为LMSYS Chatbot Arena)宣布其年化营收达到1亿美元,距离去年9月推出商业服务仅8个月。
【关键细节】• Arena源自2023年UC Berkeley的研究项目• 基于超1000万次用户评估的众包AI模型排行榜• 商业模式:为企业提供深度模型性能分析服务• 今年1月以17亿美元估值融资1.5亿美元A轮• 竞争对手Yupp已于3月倒闭• 与Mercor、Surge、Scale AI等竞争同一预算• 累计融资2.5亿美元,投资方包括a16z、Kleiner Perkins等
【深度分析】市场化分析:Arena的快速商业化证明了"AI评测"这一赛道的巨大价值。在模型能力趋同的当下,独立第三方评测成为企业选型的关键参考。Arena从开源学术项目到1亿美元营收的蜕变,也揭示了AI产业链中"评测基础设施"的商业潜力。值得注意的是,其营收来自"消费"而非"订阅",反映了AI服务定价模式的多样化趋势。

【原文内容】

Just eight months after launching its commercial service, AI leaderboard provider Arena, which originated as a research project at UC Berkeley in 2023, has reached $100 million in annualized run-rate revenue.

Arena is best known for its popular crowdsourced AI model performance leaderboard, generated from over 10 million user evaluations. Its consumer website lets a user type a prompt it sends to two models; afterward, the user chooses which model did a better job.

While Arena's popular AI model leaderboard is free for public use, the company began generating revenue from its platform in September when it introduced AI Evaluations, a service that provides model labs and enterprises with deep-dive performance analytics gathered from its community.

Arena's rapid revenue growth shows that its commercial offerings are as popular with customers as they are with its community of evaluators, who are frequently drawn to the platform for early access to the latest, often unreleased, AI models.

"A lot of people don't even understand that our business is making any money at all; people still see us as an open source project," Anastasios Angelopoulos, Arena's co-founder and CEO, told TechCrunch.

While Arena calls its revenue milestone ARR, a term that traditionally stood for annualized recurring revenue, Angelopoulos clarified that the company charges customers for "consumption," which means that its revenue is not recurring.

While Arena doesn't have direct competitors — Yupp, another crowdsourced AI model-picking startup, shut down in March— Angelopoulos said the company competes "for the same dollar" with human labeling startups like Mercor, Surge, and Scale AI, all of which assist model makers in refining their AI during post-training.

As AI providers strive to maximize model performance, their appetite for post-training optimization services continues to surge. When Arena announced in January that it raised a $150 million Series A at a post-money valuation of $1.7 billion, its annualized revenue was $30 million.

Arena has raised a total of $250 million from investors, including Felicis, Andreessen Horowitz, The House Fund, LDVP, Kleiner Perkins, Lightspeed Venture Partners, Laude Ventures, and UC Investments.

【中文翻译】

AI排行榜提供商Arena在推出商业服务仅8个月后就达到了1亿美元的年化营收。该平台源自2023年加州大学伯克利分校的一个研究项目。
Arena最著名的是其广受欢迎的众包AI模型性能排行榜,该排行榜基于超过1000万次用户评估生成。其消费者网站让用户输入一个提示词,发送给两个模型;然后用户选择哪个模型表现更好。
虽然Arena的AI模型排行榜免费向公众开放,但该公司从去年9月开始通过其平台产生收入,当时它推出了AI Evaluations服务,为模型实验室和企业提供从其社区收集的深度性能分析。
Arena的快速营收增长表明,其商业产品与客户一样受评测社区的欢迎。评测者经常被该平台吸引,因为他们可以提前体验最新的、通常尚未发布的AI模型。
Arena联合创始人兼CEO Anastasios Angelopoulos告诉TechCrunch:"很多人甚至不知道我们的业务在赚钱;人们仍然把我们看作一个开源项目。"
虽然Arena将其营收里程碑称为ARR(年化经常性收入的传统术语),但Angelopoulos澄清说,公司按"消费"向客户收费,这意味着其收入并非经常性收入。
Arena没有直接竞争对手——另一家众包AI模型选择初创公司Yupp已于3月关闭——但Angelopoulos表示,公司与Mercor、Surge和Scale AI等人工标注初创公司"争夺同一笔预算",这些公司都协助模型制造商在后训练阶段优化AI。
随着AI提供商努力最大化模型性能,他们对后训练优化服务的需求持续激增。今年1月Arena宣布以17亿美元投后估值融资1.5亿美元A轮时,其年化营收为3000万美元。
Arena已从投资者处累计融资2.5亿美元,投资方包括Felicis、Andreessen Horowitz、The House Fund、LDVP、Kleiner Perkins、Lightspeed Venture Partners、Laude Ventures和UC Investments。

【参考链接】

• https://techcrunch.com/2026/06/29/arena-the-ai-leaderboard-everyone-uses-is-now-a-100m-business/

────────────────────

5. Cursor推出移动端App,AI编程进入手机时代🔥🔥🔥🔥 热度指数:★★★★

【摘要】AI编程工具Cursor推出移动端应用,用户可通过手机启动和监控AI编程Agent,标志着AI编程从桌面走向移动。
【核心事件】Cursor宣布推出Cursor Mobile应用,允许用户直接从手机提示编程Agent、启动新的编程任务或与管理桌面客户端发起的Agent交互。
【关键细节】• Cursor此前被SpaceX以600亿美元收购• 该应用与Cursor 2.0的独立编程Agent架构深度整合• 支持iPhone Live Activities功能实时显示Agent进度• Anthropic Claude Code负责人Boris Cherny表示已几乎完全转向手机AI编程• 开发者正从多显示器桌面设置转向手机,用于与远程Agent持续对话
【深度分析】社会化分析:AI编程工具向移动端迁移是一个标志性趋势。当编程工作从"写代码"转变为"监督AI写代码"时,工作场景自然从桌面解放到移动设备。这不仅改变了开发者的工作方式,也重新定义了"编程"的含义——从键盘敲击转向对话式管理。这可能引发软件工程教育和团队协作模式的深层变革。

【原文内容】

Cursor isn't letting the $60 billion SpaceX acquisition slow it down.

On Monday, the company announced a new app called Cursor Mobile, designed for users who want to prompt coding agents directly from their phone. The app ties into the Cursor 2.0 changes unveiled in October, which shifted the service toward independent coding agents. With the mobile app, users can spin up new coding agents or interact with agents that were initiated from the desktop client.

Cursor's move to mobile follows similar apps from Anthropic and OpenAI, which both offer ways to interact with their coding tools on mobile.

It's part of a broader shift in AI-based coding tools, which are increasingly abstracting away from written code and toward oversight of code-writing agents. With no need to access large code bases, many developers are switching away from multi-monitor desktop setups in favor of phones, which allow continuous conversations with remote agents.

In a recent talk, Anthropic's head of Claude Code Boris Cherny said he had almost entirely switched to mobile AI coding as a result. "Most of my coding now is on my phone," Cherny said in the talk. "I would have said 'you're crazy' if you told me that six months ago, but yeah, here we are."

The Cursor app is available in beta on the App Store.

【中文翻译】

Cursor并没有让600亿美元的SpaceX收购案放慢脚步。
周一,该公司宣布推出一款名为Cursor Mobile的新应用,专为希望直接从手机提示编程Agent的用户设计。该应用与10月发布的Cursor 2.0变更深度整合,后者将服务转向独立编程Agent。通过移动应用,用户可以启动新的编程Agent,或与从桌面客户端发起的Agent进行交互。
Cursor向移动端迈进是继Anthropic和OpenAI之后推出类似移动应用,这两家公司都提供了在移动端与其编程工具交互的方式。
这是AI编程工具更广泛转变的一部分,这些工具正越来越多地从编写代码抽象为监督代码编写Agent。由于无需访问大型代码库,许多开发者正从多显示器桌面设置转向手机,以便与远程Agent进行持续对话。
Anthropic的Claude Code负责人Boris Cherny在最近的一次演讲中表示,他因此已几乎完全转向移动AI编程。"我现在大部分编程都在手机上完成,"Cherny在演讲中说。"如果六个月前你告诉我这些,我会说你'疯了',但是的,我们现在就是这样。"
Cursor应用已在App Store提供测试版。

【参考链接】

• https://techcrunch.com/2026/06/29/cursor-now-has-a-mobile-app-for-guiding-your-coding-agent-on-the-go/

────────────────────

6. TIDAL打击AI生成音乐,切断变现渠道🔥🔥🔥🔥 

热度指数:★★★★

【摘要】音乐流媒体平台TIDAL宣布将不再为AI生成的音乐支付版税,同时将在7月开始对100%AI生成的曲目进行标签标注。
【核心事件】音乐流媒体平台TIDAL宣布从今天起停止对AI生成音乐的版税支付(demonetize),并在7月对100%AI生成的曲目进行标签标注,但并未完全禁止AI音乐。
【关键细节】• TIDAL不直接禁止AI音乐,而是切断其变现能力• 7月起将标注100%AI生成的曲目• 此举反映了音乐行业对AI生成内容的态度分化• Suno同期推出Spark孵化器项目,招募独立艺术家为AI训练提供素材
【深度分析】市场化分析:音乐行业正面临AI生成的深刻冲击。TIDAL选择"不禁止但不变现"的中间路线,既避免了与AI技术发展的正面冲突,又保护了人类创作者的利益。与此同时,Suno的孵化器项目则代表了另一条路径——直接与AI融合。这两种策略的对比,折射出音乐行业在AI时代的路线之争:是抵抗还是拥抱?最终可能走向某种共存模式。

【原文内容】

Tidal won't pay royalties on AI-generated music but isn't banning it outright.

In July the platform will label tracks that are 100 percent AI-generated, but it's demonetizing them starting today.

The music streaming service is the latest to grapple with how to handle the flood of AI-generated content hitting platforms. The move follows similar actions by other streaming services and comes amid ongoing tension between the music industry and AI companies.

Tidal's approach represents a middle ground: rather than removing AI-generated content entirely, the platform is removing the financial incentive for creating and uploading such content. The company will also begin detecting and labeling AI-generated tracks, giving listeners more transparency about what they're hearing.

The decision has been welcomed by artist advocacy groups, who have been pushing for stronger protections against AI-generated content that can mimic established artists' voices and styles.

【中文翻译】

TIDAL将不再为AI生成的音乐支付版税,但并未完全禁止。
7月,该平台将对100%AI生成的曲目进行标签标注,但从今天起就已开始切断其变现能力。
这家音乐流媒体服务是最新一家应对AI生成内容涌入平台的平台。此举跟随了其他流媒体服务的类似行动,也是在音乐行业与AI公司之间持续紧张的背景下进行的。
TIDAL的做法代表了一种中间立场:不是完全移除AI生成的内容,而是消除创建和上传此类内容的经济激励。该公司还将开始检测和标注AI生成的曲目,为听众提供更高的透明度。
这一决定受到了艺术家权益团体的欢迎,他们一直在推动更强有力的保护措施,防止AI生成内容模仿知名艺术家的声音和风格。

【参考链接】

• https://techcrunch.com/2026/06/29/tidal-cracks-down-on-ai-music-by-cutting-off-monetization/

────────────────────

7. Ford在AI质检失败后重新雇佣资深工程师🔥🔥🔥🔥🔥 

热度指数:★★★★★

【摘要】Ford承认AI和自动化质检系统未能达到预期质量水平,已重新雇佣350名资深工程师来培训年轻员工并重新编程AI工具。
【核心事件】美国汽车巨头Ford宣布重新雇佣350名资深工程师(被称为"灰胡子"工程师),此前其依赖AI和自动化系统进行质量检测的尝试未能达到预期效果。
【关键细节】• Ford首席运营官Kumar Galhotra承认"越来越依赖自动化质检系统"但结果令人失望• 车辆硬件工程VP Charles Poon:"我们错误地以为仅通过引入AI并输入设计要求就能产出高质量产品"• 重新雇佣的工程师用于培训年轻员工和重新编程AI工具• 该举措已见成效:保修和召回成本降低,为Ford带来"数亿美元"的成本顺风• Ford在JD Power初始质量调查中位列主流品牌第一
【深度分析】社会化分析:这个案例是"AI不是万能药"的生动证明。Ford的经历揭示了一个重要教训:AI工具需要人类专业知识的有效引导才能真正发挥作用。"灰胡子"工程师的回归不是对AI的否定,而是对"人机协作"模式的重新认识。这也反映了当前AI应用中普遍存在的"过度期望"问题——许多企业以为部署AI就能自动获得质量提升,忽视了领域专业知识的不可替代性。

【原文内容】

Ford executives said they have hired 350 veteran engineers — some of them were former employees, while others had been working at suppliers — after artificial intelligence and automated systems failed to deliver the desired quality level.

Bloomberg reports the company's chief operating officer Kumar Galhotra told journalists that Ford had been "relying more and more on automated quality systems" with disappointing results. So the company "brought back technical specialists," and those specialists "hunt for failure points before a part ever reaches the plant floor."

Charles Poon, Ford's vice president of vehicle hardware engineering, added, "Mistakenly we thought that by just introducing artificial intelligence and ingesting the design requirements that we had, that that would produce a high-quality product."

To be clear, this doesn't mean Ford is abandoning its AI plans entirely. Instead, it's using the rehired employees — referred to as "gray beard" engineers — to train younger staff and reprogram AI tools.

This rehiring seems to be paying off, resulting in what Ford CEO Jim Farley said are things like lowered warranty and recall costs, "contributing to literally hundreds and hundreds of millions of dollars of a tailwind for Ford on cost." The automaker also claimed the top spot among mainstream brands in the JD Power Initial Quality Survey released this week.

【中文翻译】

Ford高管表示,在人工智能和自动化系统未能达到预期质量水平后,公司已雇佣了350名资深工程师——其中一些是前员工,另一些此前在供应商处工作。
据彭博社报道,公司首席运营官Kumar Galhotra告诉记者,Ford一直"越来越依赖自动化质检系统",但结果令人失望。因此公司"重新引入了技术专家",这些专家"在零件到达生产线之前就能发现故障点"。
Ford车辆硬件工程副总裁Charles Poon补充道:"我们错误地以为,仅仅通过引入人工智能并输入我们拥有的设计要求,就能产出高质量的产品。"
需要澄清的是,这并不意味着Ford完全放弃了AI计划。相反,它正在利用重新雇佣的员工——被称为"灰胡子"工程师——来培训年轻员工并重新编程AI工具。
这种重新雇佣似乎正在收到回报,Ford CEO Jim Farley表示,这带来了保修和召回成本的降低等成果,"为Ford在成本方面带来了数亿美元的实际收益"。这家汽车制造商还在本周发布的JD Power初始质量调查中位列主流品牌榜首。

【参考链接】

• https://techcrunch.com/2026/06/28/ford-rehires-gray-beard-engineers-after-ai-falls-short/

────────────────────

8. OpenAI展示Codex专用硬件设备🔥🔥🔥🔥 

热度指数:★★★★

【摘要】OpenAI与配件公司Work Louder合作推出Codex Micro硬件设备,一款专为Codex编程体验设计的键盘。
【核心事件】OpenAI在AI Engineer World Fair上展示了名为"Codex Micro"的硬件设备,这是一款与配件公司Work Louder合作开发的键盘,旨在"增强人们的Codex使用体验"。
【关键细节】• 设备名为Codex Micro,是一款专为Codex设计的键盘• 与配件公司Work Louder合作开发• 在AI Engineer World Fair上展示• OpenAI发言人Dominik Kundel介绍该设备• 这标志着OpenAI从纯软件向硬件延伸的趋势
【深度分析】市场化分析:OpenAI推出专用硬件设备,反映了AI公司从纯模型/软件向"全栈体验"扩展的趋势。类似于Anthropic和Google都在探索AI专用硬件,OpenAI此举旨在为Codex编程工具创造差异化的用户体验。与Work Louder的合作也表明,AI硬件生态正在形成新的产业链分工。

【原文内容】

Here's a photo of OpenAI's Codex hardware.

The gadget is called the Codex Micro, and it's being shown at the AI Engineer World Fair, where it's being described as a keyboard that's "designed to supercharge people's Codex usage," according to OpenAI spokesperson Dominik Kundel.

The hardware, a partnership between OpenAI and accessories company Work Louder, was teased earlier on Monday. A new video showed a Codex-focused device built in collaboration with Work Louder.

This represents OpenAI's continued expansion beyond pure software into dedicated hardware experiences for its AI tools.

【中文翻译】

这是OpenAI的Codex硬件设备照片。
该设备名为Codex Micro,正在AI Engineer World Fair上展示。据OpenAI发言人Dominik Kundel介绍,这是一款"旨在大幅提升人们Codex使用体验"的键盘。
这款硬件是OpenAI与配件公司Work Louder合作开发的,于周一早些时候首次预告。一段新视频展示了与Work Louder合作构建的Codex专用设备。
这标志着OpenAI从纯软件继续扩展到为其AI工具提供专用硬件体验。

【参考链接】

• https://www.theverge.com/ai-artificial-intelligence/959269/heres-a-photo-of-openais-codex-hardware

────────────────────

9. 美国议员拟立法禁止AI公司出售用户健康数据🔥🔥🔥🔥 

热度指数:★★★★

【摘要】美国参议员Elizabeth Warren等人计划推出新版《健康和位置数据保护法案》,明确禁止AI公司出售用户向聊天机器人提供的健康和位置数据。
【核心事件】美国参议员Elizabeth Warren和众议员Mary Gay Scanlon计划在未来几周推出新版《健康和位置数据保护法案》,将禁止范围扩大到AI系统,明确覆盖用户输入AI聊天机器人的数据。
【关键细节】• 该法案最初于2022年6月提出,现针对AI时代进行升级• 明确覆盖用户向ChatGPT、Claude等AI系统输入的健康数据• 要求FTC在180天内制定规则• 拨款10亿美元给FTC用于执法• 背景:OpenAI推出ChatGPT Health、Anthropic推出Claude for Healthcare• Elon Musk曾公开呼吁用户上传医疗记录到Grok• 美国缺乏联邦层面的全面数据隐私框架
【深度分析】社会化分析:随着AI公司纷纷进军医疗健康领域,用户隐私保护问题日益紧迫。当用户将MRI扫描、病历等敏感信息上传到AI聊天机器人时,现有的隐私保护框架显得捉襟见肘。该法案的推出反映了立法者对AI时代数据隐私风险的快速响应。值得注意的是,该法案同时获得民主党的Warren和Sanders支持,显示两党在AI数据隐私问题上存在共识基础。

【原文内容】

A new proposal would ban the sale of Americans' health and location information to data brokers — including information people reveal to an AI chatbot like ChatGPT or Claude.

In the coming weeks, Senator Elizabeth Warren (D-MA) and Representative Mary Gay Scanlon (D-PA) are planning to debut a new version of the Health and Location Data Protection Act that's better suited to the AI era. The former version of the bill, first introduced in June 2022, prohibited data brokers from collecting and selling health and location data. Four years later, it's expanded to ban other companies from selling such data to brokers, and to specifically cover data entered into AI systems.

AI labs have set their sights on building health and medical products. In January, Elon Musk publicly called for people to upload their medical records, like MRI scans, to Grok, xAI's chatbot. That same month, OpenAI introduced ChatGPT Health, a sandboxed tab within ChatGPT that it deemed more secure, and encouraged users to upload their medical records and other sensitive information. It also introduced ChatGPT for Healthcare, aimed at medical providers. A few days after that, Anthropic quickly followed up with Claude for Healthcare, a "HIPAA-ready" tool for individuals, health providers, and hospitals.

But when battling data breaches or unauthorized access to data, users are largely at the AI companies' mercy. The data protection for tools like OpenAI's and Anthropic's "largely depends on what companies promise in their privacy policies and terms of use," Sara Gerke, a law professor at the University of Illinois Urbana-Champaign, told The Verge in January. The US lacks an overall federal framework for data privacy, despite years of attempts.

This bill — which is also sponsored by Senators Ron Wyden (D-OR) and Bernie Sanders (I-VT) — would require the Federal Trade Commission to enact the rules within 180 days and will allow the FTC, state attorneys general, and affected individuals to sue to enforce it. It would also earmark $1 billion to the FTC over the next 10 years for enforcement.

"It's more important than ever that we crack down on data brokers that are raking in giant profits from selling Americans' most sensitive information," said Senator Warren in a statement. "Especially as more people enter their private health data into AI, we need to make sure that information isn't exploited by the highest bidder."

【中文翻译】

一项新提案将禁止向数据经纪人出售美国人的健康和位置信息——包括人们向ChatGPT或Claude等AI聊天机器人透露的信息。
在未来几周,参议员Elizabeth Warren(民主党-马萨诸塞州)和众议员Mary Gay Scanlon(民主党-宾夕法尼亚州)计划推出新版《健康和位置数据保护法案》,使其更适应AI时代。该法案最初于2022年6月提出,禁止数据经纪人收集和出售健康与位置数据。四年后,该法案扩大范围,禁止其他公司向经纪人出售此类数据,并明确覆盖输入AI系统的数据。
AI实验室已将目光投向构建健康和医疗产品。1月,Elon Musk公开呼吁人们将医疗记录(如MRI扫描)上传到xAI的聊天机器人Grok。同月,OpenAI推出了ChatGPT Health——ChatGPT中一个被认为更安全的沙盒标签页,并鼓励用户上传医疗记录和其他敏感信息。它还推出了面向医疗服务提供者的ChatGPT for Healthcare。几天后,Anthropic迅速跟进推出了Claude for Healthcare——一个面向个人、医疗服务提供者和医院的"HIPAA就绪"工具。
但在应对数据泄露或未经授权的访问时,用户基本上只能依靠AI公司的自觉。伊利诺伊大学厄巴纳-香槟分校法学教授Sara Gerke今年1月告诉The Verge,OpenAI和Anthropic等工具的数据保护"在很大程度上取决于公司隐私政策和使用条款中的承诺"。尽管多年来多次尝试,美国仍缺乏全面的数据隐私联邦框架。
该法案由参议员Ron Wyden(民主党-俄勒冈州)和Bernie Sanders(独立派-佛蒙特州)联合赞助,将要求联邦贸易委员会在180天内制定规则,并允许FTC、州总检察长和受影响的个人提起诉讼执行。它还将在未来10年向FTC拨款10亿美元用于执法。
Warren参议员在声明中表示:"打击那些通过出售美国人最敏感信息获取巨额利润的数据经纪人,比以往任何时候都更加重要。特别是随着越来越多的人将私人健康数据输入AI,我们需要确保这些信息不被出价最高的人利用。"

【参考链接】

• https://www.theverge.com/ai-artificial-intelligence/959033/health-location-data-protection-act-ai-warren-scanlon

────────────────────

10. 中国智谱AI发布GLM-5.2,网络安全能力逼近Mythos🔥🔥🔥🔥 

热度指数:★★★★

【摘要】中国智谱AI发布开源模型GLM-5.2,在网络安全和漏洞发现领域达到与美国顶级模型相当的水平。
【核心事件】中国AI公司智谱AI(Z.ai)发布了开源权重模型GLM-5.2,研究人员声称该模型在某些漏洞发现和网络安全场景中可匹配Anthropic的Mythos模型。
【关键细节】• GLM-5.2是开源权重模型,任何人都可在现有硬件上下载运行• 在网络安全/漏洞发现方面接近Mythos水平• 在通用任务上仍落后于Anthropic和OpenAI的模型• 开源特性使其灵活性高但也存在被滥用的风险• 美国政府一直试图限制中国获取先进AI模型和硬件• 该进展凸显了中美AI能力差距正在缩小
【深度分析】世界化分析:GLM-5.2的发布是中美AI竞争格局的一个重要信号。在通用能力仍有差距的情况下,中国AI公司在特定垂直领域(如网络安全)已接近甚至达到美国顶级模型水平。开源权重的发布方式更加速了技术扩散。这对出口管制政策构成挑战——当一个开源模型可以在任何硬件上运行时,传统的出口控制手段面临根本性挑战。这也可能促使各方重新思考AI安全治理的思路。

【原文内容】

China's Zhipu AI (Z.ai) released its open-weight GLM-5.2, and some researchers have claimed that it matches Mythos in certain bug-finding and cybersecurity scenarios. While GLM lags behind models from Anthropic and OpenAI in other, more general tasks, it seems that China has dramatically reduced the gap in the capabilities between its models and those of the US.

This level of advancement is particularly concerning to the U.S. government, which has worked to restrict China's access to powerful models like Anthropic's Mythos and Fable, as well as the hardware necessary to train and run them. The Trump administration views Mythos and other advanced AI models capable of identifying vulnerabilities as serious national security threats. Recently, OpenAI unveiled GPT-5.6, which has also raised concerns about its potential for misuse and has limited access to it.

Because GLM is an open-weight model, it can be downloaded and run by anyone on readily available hardware. That gives it great flexibility and allows power users deep access, but it also makes it ripe for abuse by bad actors who can run it with little oversight.

【中文翻译】

中国智谱AI(Z.ai)发布了其开源权重模型GLM-5.2,一些研究人员声称该模型在某些漏洞发现和网络安全场景中可匹配Mythos。虽然GLM在更通用的任务上仍落后于Anthropic和OpenAI的模型,但中国似乎已大幅缩小了其模型与美国模型之间的能力差距。
这一水平的进步尤其令美国政府担忧,美国一直在努力限制中国获取Anthropic的Mythos和Fable等强大模型,以及训练和运行它们所需的硬件。美国政府将Mythos和其他能够识别漏洞的先进AI模型视为严重的国家安全威胁。最近,OpenAI发布了GPT-5.6,该模型也引发了对其潜在滥用风险的担忧,并限制了访问权限。
由于GLM是一个开源权重模型,任何人都可以在现有硬件上下载和运行。这赋予了它极大的灵活性,允许高级用户深度访问,但也使其容易被行为不端者滥用,因为他们可以在很少监督的情况下运行它。

【参考链接】

• https://www.theverge.com/ai-artificial-intelligence/958804/chinas-z-ai-glm-52-mythos-cybersecurity

────────────────────
📊 今日热点总结与趋势分析
核心主题:
• AI基础设施投资狂潮:韩国9000亿美元+美国科技巨头6500亿美元,算力需求持续爆发
• AI落地现实检验:Ford质检失败、TIDAL打击AI音乐——AI并非万能药
• AI治理加速:加州政府合作、健康数据立法、网络安全模型管控
• AI工具移动化:Cursor手机端、OpenAI硬件——工作范式正在改变
趋势研判:
1. AI产业链正从"模型竞赛"转向"全栈体验"竞争(硬件+软件+服务)
2. "人机协作"而非"AI替代"成为主流共识(Ford案例、Cursor移动化)
3. 政府级AI采购成为新战场,州级vs联邦级策略分化明显
4. 开源模型在垂直领域快速追赶闭源模型,出口管制面临新挑战
5. AI数据隐私立法进入加速期,医疗健康数据成为焦点
值得关注的信号:
• Gemini月活7.5亿——AI消费者市场竞争白热化
• Arena 8个月达1亿美元营收——AI评测基础设施商业化加速
• "灰胡子"工程师回归——领域专业知识在AI时代价值重估
• GLM-5.2开源——模型能力差距缩小的速度超预期
────────────────────
END
编辑:在哒转转
日期:2026年6月30日
数据来源:TechCrunch / The Verge / Wired
基本 文件 流程 错误 SQL 调试
  1. 请求信息 : 2026-07-01 05:41:14 HTTP/1.1 GET : https://www.yeyulingfeng.com/a/818882.html
  2. 运行时间 : 0.094305s [ 吞吐率:10.60req/s ] 内存消耗:5,009.63kb 文件加载:145
  3. 缓存信息 : 0 reads,0 writes
  4. 会话信息 : SESSION_ID=6f6237811b81533940ca4b8e7679323f
  1. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/public/index.php ( 0.79 KB )
  2. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/autoload.php ( 0.17 KB )
  3. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/composer/autoload_real.php ( 2.49 KB )
  4. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/composer/platform_check.php ( 0.90 KB )
  5. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/composer/ClassLoader.php ( 14.03 KB )
  6. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/composer/autoload_static.php ( 6.05 KB )
  7. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-helper/src/helper.php ( 8.34 KB )
  8. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-validate/src/helper.php ( 2.19 KB )
  9. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/ralouphie/getallheaders/src/getallheaders.php ( 1.60 KB )
  10. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/helper.php ( 1.47 KB )
  11. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/stubs/load_stubs.php ( 0.16 KB )
  12. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Exception.php ( 1.69 KB )
  13. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-container/src/Facade.php ( 2.71 KB )
  14. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/symfony/deprecation-contracts/function.php ( 0.99 KB )
  15. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/symfony/polyfill-mbstring/bootstrap.php ( 8.26 KB )
  16. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/symfony/polyfill-mbstring/bootstrap80.php ( 9.78 KB )
  17. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/symfony/var-dumper/Resources/functions/dump.php ( 1.49 KB )
  18. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-dumper/src/helper.php ( 0.18 KB )
  19. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/symfony/var-dumper/VarDumper.php ( 4.30 KB )
  20. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/guzzlehttp/guzzle/src/functions_include.php ( 0.16 KB )
  21. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/guzzlehttp/guzzle/src/functions.php ( 5.54 KB )
  22. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/App.php ( 15.30 KB )
  23. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-container/src/Container.php ( 15.76 KB )
  24. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/psr/container/src/ContainerInterface.php ( 1.02 KB )
  25. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/provider.php ( 0.19 KB )
  26. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Http.php ( 6.04 KB )
  27. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-helper/src/helper/Str.php ( 7.29 KB )
  28. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Env.php ( 4.68 KB )
  29. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/common.php ( 0.03 KB )
  30. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/helper.php ( 18.78 KB )
  31. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Config.php ( 5.54 KB )
  32. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/alipay.php ( 3.59 KB )
  33. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/facade/Env.php ( 1.67 KB )
  34. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/app.php ( 0.95 KB )
  35. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/cache.php ( 0.78 KB )
  36. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/console.php ( 0.23 KB )
  37. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/cookie.php ( 0.56 KB )
  38. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/database.php ( 2.48 KB )
  39. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/filesystem.php ( 0.61 KB )
  40. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/lang.php ( 0.91 KB )
  41. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/log.php ( 1.35 KB )
  42. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/middleware.php ( 0.19 KB )
  43. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/route.php ( 1.89 KB )
  44. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/session.php ( 0.57 KB )
  45. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/trace.php ( 0.34 KB )
  46. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/view.php ( 0.82 KB )
  47. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/event.php ( 0.25 KB )
  48. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Event.php ( 7.67 KB )
  49. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/service.php ( 0.13 KB )
  50. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/AppService.php ( 0.26 KB )
  51. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Service.php ( 1.64 KB )
  52. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Lang.php ( 7.35 KB )
  53. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/lang/zh-cn.php ( 13.70 KB )
  54. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/initializer/Error.php ( 3.31 KB )
  55. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/initializer/RegisterService.php ( 1.33 KB )
  56. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/services.php ( 0.14 KB )
  57. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/service/PaginatorService.php ( 1.52 KB )
  58. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/service/ValidateService.php ( 0.99 KB )
  59. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/service/ModelService.php ( 2.04 KB )
  60. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-trace/src/Service.php ( 0.77 KB )
  61. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Middleware.php ( 6.72 KB )
  62. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/initializer/BootService.php ( 0.77 KB )
  63. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/Paginator.php ( 11.86 KB )
  64. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-validate/src/Validate.php ( 63.20 KB )
  65. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/Model.php ( 23.55 KB )
  66. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/model/concern/Attribute.php ( 21.05 KB )
  67. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/model/concern/AutoWriteData.php ( 4.21 KB )
  68. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/model/concern/Conversion.php ( 6.44 KB )
  69. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/model/concern/DbConnect.php ( 5.16 KB )
  70. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/model/concern/ModelEvent.php ( 2.33 KB )
  71. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/model/concern/RelationShip.php ( 28.29 KB )
  72. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-helper/src/contract/Arrayable.php ( 0.09 KB )
  73. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-helper/src/contract/Jsonable.php ( 0.13 KB )
  74. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/model/contract/Modelable.php ( 0.09 KB )
  75. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Db.php ( 2.88 KB )
  76. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/DbManager.php ( 8.52 KB )
  77. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Log.php ( 6.28 KB )
  78. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Manager.php ( 3.92 KB )
  79. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/psr/log/src/LoggerTrait.php ( 2.69 KB )
  80. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/psr/log/src/LoggerInterface.php ( 2.71 KB )
  81. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Cache.php ( 4.92 KB )
  82. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/psr/simple-cache/src/CacheInterface.php ( 4.71 KB )
  83. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-helper/src/helper/Arr.php ( 16.63 KB )
  84. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/cache/driver/File.php ( 7.84 KB )
  85. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/cache/Driver.php ( 9.03 KB )
  86. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/contract/CacheHandlerInterface.php ( 1.99 KB )
  87. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/Request.php ( 0.09 KB )
  88. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Request.php ( 55.78 KB )
  89. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/middleware.php ( 0.25 KB )
  90. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Pipeline.php ( 2.61 KB )
  91. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-trace/src/TraceDebug.php ( 3.40 KB )
  92. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/middleware/SessionInit.php ( 1.94 KB )
  93. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Session.php ( 1.80 KB )
  94. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/session/driver/File.php ( 6.27 KB )
  95. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/contract/SessionHandlerInterface.php ( 0.87 KB )
  96. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/session/Store.php ( 7.12 KB )
  97. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Route.php ( 23.73 KB )
  98. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/route/RuleName.php ( 5.75 KB )
  99. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/route/Domain.php ( 2.53 KB )
  100. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/route/RuleGroup.php ( 22.43 KB )
  101. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/route/Rule.php ( 26.95 KB )
  102. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/route/RuleItem.php ( 9.78 KB )
  103. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/route/app.php ( 3.94 KB )
  104. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/facade/Route.php ( 4.70 KB )
  105. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/route/dispatch/Controller.php ( 4.74 KB )
  106. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/route/Dispatch.php ( 10.44 KB )
  107. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/controller/Index.php ( 9.87 KB )
  108. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/BaseController.php ( 2.05 KB )
  109. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/facade/Db.php ( 0.93 KB )
  110. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/connector/Mysql.php ( 5.44 KB )
  111. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/PDOConnection.php ( 52.47 KB )
  112. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/Connection.php ( 8.39 KB )
  113. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/ConnectionInterface.php ( 4.57 KB )
  114. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/builder/Mysql.php ( 16.58 KB )
  115. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/Builder.php ( 24.06 KB )
  116. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/BaseBuilder.php ( 27.50 KB )
  117. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/Query.php ( 15.71 KB )
  118. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/BaseQuery.php ( 45.13 KB )
  119. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/TimeFieldQuery.php ( 7.43 KB )
  120. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/AggregateQuery.php ( 3.26 KB )
  121. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/ModelRelationQuery.php ( 20.07 KB )
  122. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/ParamsBind.php ( 3.66 KB )
  123. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/ResultOperation.php ( 7.01 KB )
  124. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/WhereQuery.php ( 19.37 KB )
  125. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/JoinAndViewQuery.php ( 7.11 KB )
  126. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/TableFieldInfo.php ( 2.63 KB )
  127. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/Transaction.php ( 2.77 KB )
  128. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/log/driver/File.php ( 5.96 KB )
  129. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/contract/LogHandlerInterface.php ( 0.86 KB )
  130. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/log/Channel.php ( 3.89 KB )
  131. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/event/LogRecord.php ( 1.02 KB )
  132. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-helper/src/Collection.php ( 16.47 KB )
  133. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/facade/View.php ( 1.70 KB )
  134. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/View.php ( 4.39 KB )
  135. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/controller/Es.php ( 3.30 KB )
  136. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Response.php ( 8.81 KB )
  137. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/response/View.php ( 3.29 KB )
  138. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Cookie.php ( 6.06 KB )
  139. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-view/src/Think.php ( 8.38 KB )
  140. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/contract/TemplateHandlerInterface.php ( 1.60 KB )
  141. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-template/src/Template.php ( 46.61 KB )
  142. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-template/src/template/driver/File.php ( 2.41 KB )
  143. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-template/src/template/contract/DriverInterface.php ( 0.86 KB )
  144. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/runtime/temp/c935550e3e8a3a4c27dd94e439343fdf.php ( 31.50 KB )
  145. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-trace/src/Html.php ( 4.42 KB )
  1. CONNECT:[ UseTime:0.000557s ] mysql:host=127.0.0.1;port=3306;dbname=wenku;charset=utf8mb4
  2. SHOW FULL COLUMNS FROM `fenlei` [ RunTime:0.000684s ]
  3. SELECT * FROM `fenlei` WHERE `fid` = 0 [ RunTime:0.000287s ]
  4. SELECT * FROM `fenlei` WHERE `fid` = 63 [ RunTime:0.001180s ]
  5. SHOW FULL COLUMNS FROM `set` [ RunTime:0.000721s ]
  6. SELECT * FROM `set` [ RunTime:0.001432s ]
  7. SHOW FULL COLUMNS FROM `article` [ RunTime:0.000577s ]
  8. SELECT * FROM `article` WHERE `id` = 818882 LIMIT 1 [ RunTime:0.000981s ]
  9. UPDATE `article` SET `lasttime` = 1782855674 WHERE `id` = 818882 [ RunTime:0.001962s ]
  10. SELECT * FROM `fenlei` WHERE `id` = 64 LIMIT 1 [ RunTime:0.000362s ]
  11. SELECT * FROM `article` WHERE `id` < 818882 ORDER BY `id` DESC LIMIT 1 [ RunTime:0.000498s ]
  12. SELECT * FROM `article` WHERE `id` > 818882 ORDER BY `id` ASC LIMIT 1 [ RunTime:0.000406s ]
  13. SELECT * FROM `article` WHERE `id` < 818882 ORDER BY `id` DESC LIMIT 10 [ RunTime:0.000636s ]
  14. SELECT * FROM `article` WHERE `id` < 818882 ORDER BY `id` DESC LIMIT 10,10 [ RunTime:0.001052s ]
  15. SELECT * FROM `article` WHERE `id` < 818882 ORDER BY `id` DESC LIMIT 20,10 [ RunTime:0.001271s ]
0.096002s