包括 New York Times 、 The Atlantic 和 USA Today 在内的主要新闻媒体,近期已停止允许 Internet Archive 的 Wayback Machine 保存其内容。倡导者认为,此举威胁到新闻作品的长期可获取性与完整性。自 2026 年初起,这些机构主动封堵该存档工具,理由是担心生成式 AI 公司可能抓取其付费墙后的内容来训练模型。 Major news outlets like the New York Times, The Atlantic, and USA Today have recently stopped allowing the Internet Archive's Wayback Machine to preserve their content, a move that advocates argue threatens the long-term accessibility and integrity of journalistic work. Since early 2026, these organizations have actively blocked the archiving tool, citing concerns over generative AI companies potentially scraping their paywalled material to train models. Petition organizers from activist group Fight for the Future counter that these AI concerns are "wholly hypothetical" and ignore the Wayback Machine's decades-long track record as a respectful, nonprofit public service that skips paywalls and operates with integrity. They argue that AI companies can already scrape content directly from publisher sites, but the Internet Archive voluntarily adheres to rules like robots.txt to avoid doing so.
包括 New York Times 、 The Atlantic 和 USA Today 在内的主要新闻媒体,近期已停止允许 Internet Archive 的 Wayback Machine 保存其内容。倡导者认为,此举威胁到新闻作品的长期可获取性与完整性。自 2026 年初起,这些机构主动封堵该存档工具,理由是担心生成式 AI 公司可能抓取其付费墙后的内容来训练模型。
来自维权组织 Fight for the Future 的请愿发起人反驳称,这些对 AI 的担忧"纯属臆测",忽视了 Wayback Machine 数十年来作为非营利性公共服务的良好记录——它并不会刻意绕过付费墙,并以诚信方式运作。他们指出,即便没有 Wayback Machine,AI 公司也已能直接从出版商网站抓取内容,而 Internet Archive 自愿遵守 robots.txt 等规则以避免此类行为。
这场运动将封堵 Wayback Machine 视为对新闻自由的直接威胁,强调新闻的力量不仅在于发布,更在于为后世保存。发起人举出一个颇具讽刺意味的例子:USA Today 的调查报道本身就依赖 Wayback Machine 归档的网页内容,但该机构同时却阻止自己的报道被保存。超过 100 名记者联署了一封信,赞扬 Internet Archive 的作用并引发公众广泛讨论,但 The Atlantic 的 CEO 明确拒绝承诺寻找恢复存档权限的解决方案。此举发生在全球新闻业面临日益严峻威胁的背景下,包括审查、威权压力,甚至针对记者的暴力,这些都使独立存档比以往更加重要。
请愿书将 Wayback Machine 定位为至关重要的中立第三方,认为被归档的新闻更能抵御那些可能施压媒体修改或删除不利报道的强大势力。这种保障不仅对历史记录至关重要,也被视为强化民主问责的工具——确保事实在政治或商业压力下仍然可查可得。活动人士强调,独立存档符合任何严肃新闻机构追求真相的根本利益,但他们发现与 Internet Archive 在这项基本保存工作上的合作竟异常困难。
请愿的核心诉求很明确:各大媒体机构的领导者必须公开承诺与 Internet Archive 合作,恢复并维持新闻内容的存档。组织者强调,在虚假信息泛滥、记者身处直接威胁的时代,应对这些挑战的办法应是加强保存与开放获取,而非削弱。他们将 Wayback Machine 可能失去新闻内容视为对互联网上最重要档案工具的致命打击,敦促新闻机构立即改弦更张,支持这一维护公共信息完整性的盟友。
Major news outlets like the New York Times, The Atlantic, and USA Today have recently stopped allowing the Internet Archive's Wayback Machine to preserve their content, a move that advocates argue threatens the long-term accessibility and integrity of journalistic work. Since early 2026, these organizations have actively blocked the archiving tool, citing concerns over generative AI companies potentially scraping their paywalled material to train models. Petition organizers from activist group Fight for the Future counter that these AI concerns are "wholly hypothetical" and ignore the Wayback Machine's decades-long track record as a respectful, nonprofit public service that skips paywalls and operates with integrity. They argue that AI companies can already scrape content directly from publisher sites, but the Internet Archive voluntarily adheres to rules like robots.txt to avoid doing so.
The campaign frames the blocking of the Wayback Machine as a direct threat to press freedom, emphasizing that journalism's power depends not only on publication but on preservation for future generations. Organizers highlight a bitter irony exemplified by USA Today, which publishes investigative reporting that itself relies on archived web content through the Wayback Machine while simultaneously preventing its own work from being similarly preserved. Over 100 journalists signed a letter celebrating the Internet Archive's role, which sparked significant public discussion, yet The Atlantic's CEO notably declined to commit to finding a solution that would restore archiving access. This stance comes amid growing global threats to journalism, including censorship, authoritarian pressure, and even violence against reporters, making independent preservation more critical than ever.
Positioning the Wayback Machine as a vital neutral third party, the petition argues that archived news is more resilient against powerful interests who might pressure outlets to alter or remove damaging stories. This safeguard is portrayed as essential not just for historical record, but as a tool that actively strengthens democratic accountability by ensuring facts remain accessible despite political or commercial pressures. The campaign underscores that independent archiving serves the fundamental interest of any serious news organization committed to truth, yet finds it unnecessarily difficult to collaborate with the Internet Archive on this basic function of preservation.
The petition's core demand is straightforward. Leaders of major media outlets must publicly commit to working with the Internet Archive to restore and maintain the archiving of news content. Organizers stress that in an era of rising disinformation and direct threats to journalists, the way to combat these challenges is through more preservation and access, not less. They view the Wayback Machine's potential loss of news content as a mortal peril to the internet's most powerful archiving tool, urging news organizations to immediately reverse course and champion this ally in sustaining the integrity of public information.
Muneeb 和 Sohaib Akhter 是一对双胞胎兄弟,先前因计算机欺诈被判重罪。 2025 年 2 月,他们在一家为政府承包商担任 IT 职位时被解雇。被解雇数分钟内,Muneeb 利用权限撤销的疏漏,系统性删除了 96 个包含美国政府信息的数据库,其中包括 Department of Homeland Security 和 Equal Employment Opportunity Commission 的系统。他还下载了敏感文件,并通过清除系统日志、咨询 AI 工具如何抹去证据等手段试图掩盖痕迹。 Muneeb and Sohaib Akhter, twin brothers with prior felony convictions for computer fraud, were fired from their IT jobs at a government contractor in February 2025. Within minutes of being terminated, Muneeb exploited a lapse in access revocation to systematically delete 96 databases containing US government information, including systems for the Department of Homeland Security and the Equal Employment Opportunity Commission. He also downloaded sensitive files and attempted to cover his tracks by clearing system logs and consulting an AI tool on how to erase evidence.
Muneeb 和 Sohaib Akhter 是一对双胞胎兄弟,先前因计算机欺诈被判重罪。 2025 年 2 月,他们在一家为政府承包商担任 IT 职位时被解雇。被解雇数分钟内,Muneeb 利用权限撤销的疏漏,系统性删除了 96 个包含美国政府信息的数据库,其中包括 Department of Homeland Security 和 Equal Employment Opportunity Commission 的系统。他还下载了敏感文件,并通过清除系统日志、咨询 AI 工具如何抹去证据等手段试图掩盖痕迹。
两人有长期犯罪史。 2015 年,兄弟俩均对电信欺诈与计算机犯罪认罪,Muneeb 服刑三年,Sohaib 服刑两年。获释后,他们进入总部位于 Washington, DC 的 Opexus 工作,该公司为 45 个联邦客户提供服务。尽管进行了背景调查,但他们的前科要么被遗漏,要么审查不充分。在职期间,Muneeb 从公司网络中窃取了约 5,400 份凭证,借助定制脚本访问包括 Marriott 、 DocuSign 和多家航空服务在内的账户,有时还用受害者的里程为自己预订旅行。
两人在下午 4:50 通过 Microsoft Teams 通话被解雇后,Sohaib 的访问权限被立即撤销,但 Muneeb 的凭证仍然有效。在 4:56 至 17:50 之间,Muneeb 下达了多条破坏性命令,兄弟俩在此期间实时沟通。 Sohaib 煽动并建议删除文件系统、讨论可能的勒索方案,但 Muneeb 认为勒索风险太高而予以拒绝。事后,他们在一名未具名同谋的协助下重装了笔记本的操作系统。
三周后,联邦探员突袭了 Sohaib 的住所,查获了电子设备,并发现 7 支枪支和 370 发弹药——鉴于其前科,这些均属非法持有。两人于 2025 年 12 月被捕并面临多项指控。 Muneeb 于 2026 年 4 月签署认罪协议,承认主要指控;Sohaib 则诉诸审判,最终被判犯有共谋实施计算机欺诈、密码贩运及非法持枪罪,量刑将在九月进行。
Muneeb 此后自狱中提交手写请愿,声称辩护律师失职并试图撤回认罪,称签字系在压力下作出;他还申请自行辩护,但此类请求在联邦法院罕有成功。本案暴露出在解除访问权限和背景筛查流程上的严重失误,Opexus 承认本应采取更严格的审查,并表示负责雇用这对双胞胎的相关员工已不再任职。
Muneeb and Sohaib Akhter, twin brothers with prior felony convictions for computer fraud, were fired from their IT jobs at a government contractor in February 2025. Within minutes of being terminated, Muneeb exploited a lapse in access revocation to systematically delete 96 databases containing US government information, including systems for the Department of Homeland Security and the Equal Employment Opportunity Commission. He also downloaded sensitive files and attempted to cover his tracks by clearing system logs and consulting an AI tool on how to erase evidence.
The brothers had a history of criminal activity. In 2015, both pleaded guilty to wire fraud and computer crimes, with Muneeb serving three years and Sohaib serving two. After their release, they secured positions at Opexus, a Washington, DC-based firm serving 45 federal clients. Despite background checks, their past was either missed or inadequately vetted. During their employment, Muneeb amassed 5,400 stolen credentials from company networks, using custom scripts to access accounts on platforms like Marriott, DocuSign, and airline services, sometimes booking personal travel with victims' miles.
After their firing via Microsoft Teams call at 4:50 pm, Sohaib found his access immediately revoked, but Muneeb's credentials remained active. Between 4:56 pm and 5:50 pm, Muneeb executed destructive commands while the brothers communicated in real time. Sohaib encouraged the destruction, suggesting filesystem deletion and discussing potential blackmail schemes, though Muneeb rejected extortion as too incriminating. They later reinstalled operating systems on their laptops with help from an unnamed co-conspirator.
Federal agents raided Sohaib's home three weeks later, seizing technology equipment and discovering seven firearms and 370 rounds of ammunition, illegal possessions given his prior convictions. Both brothers were arrested in December 2025 and indicted on multiple charges. Muneeb signed a plea deal in April 2026 admitting to the major allegations, while Sohaib went to trial and was found guilty of conspiracy to commit computer fraud, password trafficking, and illegal firearm possession. He awaits sentencing in September.
Muneeb has since filed handwritten petitions from jail claiming ineffective counsel and attempting to withdraw his guilty plea, arguing he was pressured into signing it. He has also requested to represent himself, a move that rarely succeeds in federal court. The case highlights critical failures in both credential management during terminations and background screening processes, with Opexus acknowledging that additional diligence should have been applied and that the individuals responsible for hiring the twins are no longer employed.
讨论集中在一起由一对双胞胎兄弟访问敏感政府数据库所引发的安全漏洞事件上,暴露出招聘、凭证管理和数据保护方面的系统性缺陷。一个关键争议是雇主对类似事件的过度反应:许多人主张在员工离职时立即撤销所有访问权限,而另一些人则认为,如果已实施双人控制、哈希密码等恰当的安全措施,立刻切断访问既不人性也不必要。该事件还暴露出更严重的问题:涉事人员能够访问约 5000 个明文密码,且在有犯罪前科的情况下仍被聘用,凸显了技术标准和背景调查方面的严重疏漏,尤其是在处理敏感数据的岗位上。
普遍的观点是以明文存储密码不可原谅,哈希与加盐是不可妥协的最佳实践。该事件亦揭示了像 SOC2 这类合规框架的局限性:它们通常只验证是否遵守了某些政策,却不评估这些政策本身是否足够严格。多位评论者指出,政府机构常年运行过时系统(例如 Windows Server 2012),且未能执行基本的安全卫生措施,部分原因在于官僚惰性与缺乏问责。
讨论还反映出离职流程中安全需求与人道主义关切之间的紧张。一方面有人认为,突然终止访问是防止数据泄露的必要手段;另一方面有人提出更细致的做法,比如分阶段的离职中心,允许在受监控下有限访问以完成过渡任务,但这类方案需要投入且回报不明确,因此少见。个人经历展示了职场中普遍的不信任氛围:员工担心被盗或突然失业,因而不敢在办公桌上留个人物品。
招聘实践亦遭到审查,尤其是有重罪记录的人如何获得关键系统访问权。部分人将责任归咎于限制背景调查的"Ban the Box"法案,另一些人则质疑招聘经理的判断力。讨论还延伸到工具中立性的更广泛议题:人工智能是在助长恶意行为,还是仅仅降低了本就可能的入门门槛。归根结底,该事件是连锁失败的典型:不当招聘、薄弱的访问控制、过时的基础设施与缺乏监督相互叠加,最终导致重大损害。
The discussion centers on a security breach involving twin brothers with access to sensitive government databases, highlighting systemic failures in hiring, credential management, and data protection practices. A key concern is the overcorrection by employers in response to such incidents, with many advocating for immediate revocation of all access upon termination, while others argue this is dehumanizing and unnecessary if proper safeguards like two-person controls and hashed passwords are in place. The fact that the individuals had plaintext access to 5,000 passwords and were hired despite prior criminal convictions underscores serious lapses in both technical standards and background checks, especially for roles handling sensitive data.
There is broad agreement that storing passwords in plaintext is inexcusable and violates basic security principles, with hashing and salting being non-negotiable best practices. The incident also exposed weaknesses in compliance frameworks like SOC2, which verify policy adherence but do not assess the rigor of those policies themselves. Several commenters noted that government agencies often run outdated systems (e.g., Windows Server 2012) and fail to enforce basic security hygiene, partly due to bureaucratic inertia and lack of accountability.
The conversation reflects tension between security and humanity in offboarding processes. While some defend abrupt access termination as necessary to prevent data exfiltration, others propose more nuanced approaches, such as segmented offboarding centers that allow limited, monitored access for transition tasks. However, such solutions require investment without clear ROI, making them rare. Personal anecdotes reveal widespread distrust in workplace environments, with employees avoiding leaving personal items at desks due to fear of theft or sudden job loss.
Hiring practices came under scrutiny, particularly how individuals with felony records gained access to critical systems. Some attributed this to "Ban the Box" laws restricting background checks, while others questioned the competence of hiring managers. The discussion also touched on broader themes of tool neutrality, with debate over whether AI enables malicious behavior or merely lowers the barrier to actions that were already possible. Ultimately, the incident serves as a case study in cascading failures: poor hiring, inadequate access controls, outdated infrastructure, and lack of oversight combined to enable significant damage.
该仓库 OrcaSlicer-bambulab 由 FULU-Foundation 维护,是 OrcaSlicer 的一个专用分支,旨在为 Bambu Lab 3D 打印机恢复完整的 BambuNetwork 支持。与可能仅限本地网络(LAN)的标准版本不同,此构建通过 BambuNetwork 恢复互联网远程控制和打印功能,使用户能够像在限制出台前一样远程操作。该项目在 GitHub 上反响热烈,拥有 1.5k 星和 383 个 fork 。 This repository, OrcaSlicer-bambulab by FULU-Foundation, is a specialized fork of the OrcaSlicer software designed to restore full BambuNetwork support for Bambu Lab 3D printers. Unlike the standard version which may limit users to local network (LAN) only connections, this build enables full functionality over the internet through BambuNetwork, allowing users to control and print remotely just as they could before any restrictions were implemented. The project has gained significant traction with 1.5k stars and 383 forks on GitHub.
该仓库 OrcaSlicer-bambulab 由 FULU-Foundation 维护,是 OrcaSlicer 的一个专用分支,旨在为 Bambu Lab 3D 打印机恢复完整的 BambuNetwork 支持。与可能仅限本地网络(LAN)的标准版本不同,此构建通过 BambuNetwork 恢复互联网远程控制和打印功能,使用户能够像在限制出台前一样远程操作。该项目在 GitHub 上反响热烈,拥有 1.5k 星和 383 个 fork 。
安装方式因操作系统而异:Windows 用户需在以管理员权限运行的命令提示符或 PowerShell 中执行指定命令以启用 WSL 2(Windows Subsystem for Linux),然后才能启动 Orca Studio;Linux 用户可按常规方式安装,无需额外依赖;macOS 支持仍在开发中,尚未完全可用。
仓库包含面向 Windows 、 Linux 和 macOS 的各类构建脚本与配置文件。主要代码以 C++ 为主(约 82.5%),其余包括 C 、 JavaScript 、 HTML 、 CMake 和 Shell 脚本。项目采用 AGPL-3.0 许可证,保证其开源属性。
维护者 codedbyjake 还建议用户查看其其它仓库中的 BMCU 固件,BMCU 似乎是用于 3D 打印机的配套固件。仓库最近有活动,最新提交修复了工作流之间的工件名称冲突,首个发行版 v1.0.0 于 2026 年 5 月 12 日发布。对于希望通过 OrcaSlicer 保持对 Bambu Lab 打印机完整远程访问的用户而言,该项目是重要资源。
This repository, OrcaSlicer-bambulab by FULU-Foundation, is a specialized fork of the OrcaSlicer software designed to restore full BambuNetwork support for Bambu Lab 3D printers. Unlike the standard version which may limit users to local network (LAN) only connections, this build enables full functionality over the internet through BambuNetwork, allowing users to control and print remotely just as they could before any restrictions were implemented. The project has gained significant traction with 1.5k stars and 383 forks on GitHub.
Installation varies by operating system. Windows users need to enable WSL 2 (Windows Subsystem for Linux) by running specific commands in an elevated Command Prompt or PowerShell before launching Orca Studio. Linux users can proceed with a normal installation without additional requirements. macOS support is currently listed as a work in progress, indicating it's not yet fully functional or available.
The repository includes various build scripts and configuration files for different platforms, including Windows, Linux, and macOS. The primary codebase is written predominantly in C++ (82.5%), with smaller portions in C, JavaScript, HTML, CMake, and Shell scripting. The project is licensed under AGPL-3.0, ensuring it remains open source.
The maintainer, codedbyjake, also encourages users to explore BMCU firmware, which can be found in their other repositories. BMCU appears to be complementary firmware for 3D printers. The repository shows recent activity with the latest commit fixing artifact name conflicts between workflows, and the first release (v1.0.0) was published on May 12, 2026. The project serves as an important resource for Bambu Lab printer users who want to maintain full remote access capabilities through OrcaSlicer.
• Bambu Lab 目前的系统迫使用户在带远程监控的云模式和仅本地打印的 LAN/ 开发者模式之间二选一,用户希望两者并存,但公司通过固件限制人为阻止这一点。
• 已出现一个插件,通过模拟云认证使本地打印同时保留在线功能,但这仍要求信任本可在本地处理的云基础设施。
• Bambu 为其"Pro"企业用户保留了云与 LAN 同时使用的权限,表明技术上可行,却故意不向消费级打印机开放。
• 公司最初宣称即便是本地 LAN 打印也需要云授权,仅在社区强烈反对后才退让,这种做法已侵蚀用户信任。
• 通过软件更新在购买后移除硬件功能违反了许多司法管辖区的消费者权益,属于典型的"诱饵式调包"。
• Bambu 已威胁对致力于本地打印解决方案的开发者采取法律行动,施加经济压力,实际上威胁到了整个开发者社区。
• 用户可以通过 Home Assistant 集成和 MQTT 在本地实现大部分云功能,但像移动应用访问和取消单个打印部件等功能仍依赖云端。
• 强制云连接在实验室、初创企业和政府环境中带来安全隐患:通过公司服务器路由打印数据会增加间谍活动和数据收集的风险。
• 有人猜测中国政府的压力可能促使中国硬件公司要求连接到中国数据中心,以实现被动数据收集并在必要时远程使设备变砖。
• 争议引发了 Streisand 效应,Bambu 激进的反应引来更多审查,损害了其在创客社区的声誉。
讨论表明用户对 Bambu Lab 对本地打印功能的人为限制感到深刻挫败;大多数参与者认为强制云要求要么是技术无能,要么是为了掌控用户数据并为未来变现创造机会的刻意策略。社区已围绕"维修权"原则团结起来,认为已购硬件应在不受厂商附加限制的情况下使用。虽有少数人维护 Bambu 保护其软件与服务权利的立场,但主流观点认为在购买后移除功能并威胁开发者,标志着从产品所有权向对服务依赖的不可接受转变。
• Bambu Lab's current system forces users to choose between cloud mode with remote monitoring and LAN/Developer mode with local printing, but users want both simultaneously, which the company has made artificially impossible through firmware restrictions.
• A plugin has emerged that emulates cloud authentication to allow local printing while maintaining online functionality, though this requires trusting the cloud infrastructure for operations that could be handled locally.
• Bambu reserves simultaneous cloud and LAN functionality for their "Pro" enterprise users, demonstrating the technical capability exists but is deliberately withheld from consumer printers.
• The company initially announced that cloud authorization would be required even for local LAN printing, only backpedaling after significant community backlash, which has eroded trust.
• Removing functionality from hardware after purchase through software updates violates consumer rights in many jurisdictions and represents a "bait-and-switch" where products become services.
• Bambu has threatened legal action against developers working on local printing solutions, applying financial pressure that effectively threatens the entire developer community.
• Users can achieve most cloud functionality locally through Home Assistant integration and MQTT, though some features like mobile app access and individual part cancellation remain cloud-dependent.
• The forced cloud connectivity creates security concerns for users in labs, startups, and government environments where routing print data through company servers poses espionage and data harvesting risks.
• Some speculate Chinese government pressure may be motivating Chinese hardware companies to require cloud connections to China-based data centers, enabling passive data collection and potential device bricking.
• The controversy has triggered a Streisand effect, with Bambu's aggressive response drawing more scrutiny and damaging their reputation among the maker community.
The discussion reveals deep frustration with Bambu Lab's artificial restrictions on local printer functionality, with most participants viewing the forced cloud requirement as either technical incompetence or a deliberate strategy to control user data and create future monetization opportunities. The community has largely rallied around right-to-repair principles, arguing that purchased hardware should be usable without vendor-imposed limitations. While some defend Bambu's right to protect their software and services, the prevailing sentiment is that removing post-purchase functionality and threatening developers represents an unacceptable shift from product ownership to service dependency.
Scrcpy v4.0 正式发布,这是这款流行 Android 屏幕镜像工具的一次重要升级。最显著的变化是从 SDL2 迁移到 SDL3,带来了持续维护与错误修复,并新增了在调整窗口大小时锁定宽高比等功能,这一底层改进为本次发布的多项新特性奠定了基础。 Scrcpy v4.0 has been released, marking a significant update to the popular Android screen mirroring tool. The most notable change is the migration from SDL2 to SDL3, which brings active maintenance, bug fixes, and new capabilities like aspect ratio locking when resizing the window. This foundational upgrade enables several of the release's headline features.
Scrcpy v4.0 正式发布,这是这款流行 Android 屏幕镜像工具的一次重要升级。最显著的变化是从 SDL2 迁移到 SDL3,带来了持续维护与错误修复,并新增了在调整窗口大小时锁定宽高比等功能,这一底层改进为本次发布的多项新特性奠定了基础。
一个重大新增是弹性显示支持,允许虚拟显示随客户端窗口动态调整大小,可通过 --flex-display 或 -x 参数启用。这让在桌面上以可调整尺寸的窗口运行 Android 应用变得更加实用。新版还加入了摄像头控制,支持在会话中用 MOD+t 切换摄像头手电筒、用 MOD+↑/MOD+↓ 调整变焦,也可以通过新的命令行选项在启动时设置。
此次更新在用户体验上也做了若干优化:调整窗口大小时会保留宽高比以避免黑边(如需可通过选项恢复旧行为);新增的 --keep-active 选项可防止设备进入休眠而无需修改系统全局设置;默认背景色由黑色改为深灰色,断开连接时会先显示一个断开图标两秒再关闭窗口,从而更清晰地区分连接丢失与程序崩溃。
在底层修复方面,v4.0 解决了包括 Meta Quest 闪烁问题、已 root 设备的复制粘贴问题、色彩空间转换问题,以及一个奇怪的 bug:由于 OPUS 音频解码中的非规格化数,播放静音时会导致高 CPU 占用。新增了 F11 全屏和 MOD+q 退出等快捷键。该版本还升级了核心依赖(如 FFmpeg 、 SDL 和 platform-tools(adb)),并在整个代码库中做了多处技术修复与改进。
Scrcpy v4.0 has been released, marking a significant update to the popular Android screen mirroring tool. The most notable change is the migration from SDL2 to SDL3, which brings active maintenance, bug fixes, and new capabilities like aspect ratio locking when resizing the window. This foundational upgrade enables several of the release's headline features.
One major addition is flex display support, allowing virtual displays to be resized dynamically alongside the client window using the `--flex-display` or `-x` flag. This makes it much more practical to run Android apps in resizable windows on a desktop. The release also introduces camera controls, letting users toggle the camera torch with `MOD`+`t` and adjust zoom with `MOD`+`↑`/`MOD`+`↓`, either during a session or at startup via new command-line options.
The update improves the user experience in several ways. Window aspect ratio is now preserved during resizing to avoid black bars, though the old behavior can be restored with a flag. A new `--keep-active` option prevents the device from sleeping without changing global settings. The default background color changed from black to dark gray, and a disconnected icon now appears for two seconds before the window closes, making it clearer when a connection is lost versus a crash.
Under the hood, v4.0 fixes a range of issues including Meta Quest flickering, copy-paste on rooted devices, colorspace conversion, and a curious bug where playing silence consumed high CPU due to denormal numbers in OPUS audio decoding. New shortcuts like `F11` for fullscreen and `MOD`+`q` to quit have been added. The release also upgrades core dependencies including FFmpeg, SDL, and platform-tools (adb), along with various technical fixes and improvements throughout the codebase.
• scrcpy 广受好评,是一款通过 USB 或 TCP/IP 镜像并控制 Android 设备的利器。它在 Linux 、 Windows 和 macOS 上运行流畅、使用方便,无需 root 权限或在设备上安装额外应用,许多用户形容为"令人惊讶"的体验。
• 在实际场景中,scrcpy 展现了不可替代的价值:访问屏幕损坏的手机、把旧设备当成网络摄像头或麦克风、启用反向网络共享以共享互联网、以及从阻止截图的应用中获取内容 —— 在结合 ADB 和 root 权限时尤为有用。
• 高级功能也备受赞誉,比如通过 --flex-display 动态调整大小、为不支持 DeX 的设备创建虚拟显示器,以及在截图被禁用时仍能录制视频,这些特性既满足日常使用也适用于专业任务。
• 也有一些设备特定的问题被提及,例如在部分 Samsung 设备上手势导航可能会失效,需要重启才能恢复;如果事先未启用 ADB,则在屏幕完全损坏后难以访问设备,这凸显了事前启用 ADB 并信任永久密钥的重要性。
• scrcpy 的开发者还为 VLC media player 做出过贡献,该项目以简洁且可读性高的 C 代码著称,反映出优秀的软件工程实践。
• 实用的应急技巧包括通过调低屏幕亮度进行盲操作或使用 USB 外设,但在图案解锁和某些应用的可访问性方面仍有限制,尤其是银行类应用对屏幕阅读器的支持较差。
• 文中也提到过替代方案如 Droidcam 和 wo-mic,用于把旧手机当摄像头或麦克风,但 scrcpy 以其稳定性和低延迟脱颖而出;部分用户同时指出长时间使用时的电池续航和发热问题。
• 由于受欢迎,不少用户对其在 iOS 上缺失感到失望,甚至有人自行开发类似的解决方案(例如在 Android 上搭建 RDP 服务器)以实现统一控制。
• 一个反复出现的主题是"提前准备",在屏幕损坏前启用 ADB 并设置受信任的密钥,否则事后的访问将非常困难,这也让许多人对现代安全机制在数据恢复方面的限制感到无奈。
• 讨论还涉及更广的生态系统观察(如 ChromeOS 的 Android 集成),但凭借可靠性和社区支持,scrcpy 仍被一致推荐为必备工具。
总体而言,scrcpy 被定位为 Android 用户的常备工具:功能强大、性能无缝、开发者专业,既能解决设备恢复问题,也能实现旧硬件的创意再利用。用户普遍赞赏其"开箱即用"的开源特性,同时也提醒要注意设备兼容性与应急前的准备工作。
• scrcpy is widely praised as an exceptional tool for mirroring and controlling Android devices via USB or TCP/IP, with many users describing it as a "mind-blown" experience due to its smooth performance and ease of use across Linux, Windows, and macOS without requiring root access or installing an app on the device.
• The software proves invaluable in practical scenarios such as accessing phones with broken screens, using old devices as webcams or microphones, enabling reverse tethering for internet sharing, and capturing content from apps that block screenshots, especially when combined with ADB and root access.
• Users highlight advanced features like dynamic resizing with `--flex-display`, virtual displays for unsupported DeX functionality, and the ability to record video even when screenshots are blocked, making it versatile for both everyday use and specialized tasks.
• Despite its strengths, some users report issues like gesture navigation breaking on Samsung devices after use, requiring a reboot, and challenges accessing phones with dead screens if ADB debugging wasn't pre-enabled, underscoring the importance of setting up ADB and permanent key trust before screen failure.
• The developer behind scrcpy also contributed to VLC media player, and the project is noted for its clean, readable C code, reflecting high-quality software engineering practices.
• Practical workarounds using scrcpy include using it for blind navigation by adjusting screen brightness or leveraging USB peripherals, though limitations exist with pattern unlock and app accessibility, particularly with banking apps having poor screen reader support.
• Alternatives like Droidcam and wo-mic are mentioned for using old phones as webcams or mics, but scrcpy stands out for its stability and low latency, though some users note battery life and heat as concerns with prolonged use.
• The tool is so beloved that users express disappointment at its absence on iOS due to regional restrictions, and some have even developed custom solutions like RDP servers for Android to unify device control.
• A common theme is the necessity of preparation, such as enabling ADB and setting up trusted keys before screen damage, as post-failure access is extremely difficult without prior setup, leading to frustration with modern security measures that hinder recovery.
• The discussion also touches on broader ecosystem observations, like ChromeOS integrating Android features, but scrcpy remains a standout for its reliability and community support, with users consistently recommending it as a must-have utility.
The discussion overwhelmingly celebrates scrcpy as a remarkably reliable and versatile tool that solves real-world problems, from device recovery to creative repurposing of old hardware. Users share diverse use cases, emphasizing its seamless performance and the developer's expertise, while also noting minor drawbacks like device-specific bugs and the critical need for proactive setup to handle emergencies. The sentiment reflects a strong community appreciation for open-source software that "just works," with calls for better accessibility and cross-platform availability. Overall, scrcpy is positioned as an essential utility for Android users, blending technical excellence with practical utility.
文章介绍了六条排版规则,用来在科幻电影中营造未来感,并以对单词在 Eurostile Bold 字体上的逐步变形为例说明。规则一是加入斜体倾斜,暗示前进的动感;规则二把曲线与棱角结合起来;规则三在字母上加入"consummate Vs"(即尖锐的 V 形切口);规则四通过字母相互连接,呼应虚构的 "Kern Wars",并避免触犯 "Kern Tithe";规则五去掉字母里任意的水平线段;规则六则加入噪点纹理、拉丝金属效果、蓝色光效、浮雕以及星空背景。 The article presents six typographic rules for making text look futuristic in science fiction movies, using a step-by-step transformation of a word in Eurostile Bold as an example. Rule 1 involves adding an italic slant to suggest forward motion. Rule 2 introduces a mix of curvy and angular forms. Rule 3 adds "consummate Vs," or sharp V-shaped notches in letters. Rule 4 combines letters to reflect the fictional "Kern Wars" and avoid violating the "Kern Tithe." Rule 5 removes arbitrary horizontal segments from letters. Rule 6 incorporates noise textures, brushed metal effects, blue lighting, embossing, and a star field background.
文章介绍了六条排版规则,用来在科幻电影中营造未来感,并以对单词在 Eurostile Bold 字体上的逐步变形为例说明。规则一是加入斜体倾斜,暗示前进的动感;规则二把曲线与棱角结合起来;规则三在字母上加入"consummate Vs"(即尖锐的 V 形切口);规则四通过字母相互连接,呼应虚构的 "Kern Wars",并避免触犯 "Kern Tithe";规则五去掉字母里任意的水平线段;规则六则加入噪点纹理、拉丝金属效果、蓝色光效、浮雕以及星空背景。
作者把 Ridley Scott 的 Blade Runner 视为这些原则的"始祖范例"。文中列举了许多其他电影在不同程度上运用这些规则:Battlestar Galactica (2003) 和 Transformers 几乎涵盖了所有规则,后者尤重拉丝金属效果;Guardians of the Galaxy 除斜体外用到了大多数技巧;RoboCop 强调 consummate Vs 和夸张的浮雕;Star Wars 用相连的字母很好地体现了规则四;The Amazing Spider-Man 也遵循了大部分规则,但在字距处理上有些疏漏。
其它例子还包括:Captain America: The Winter Soldier 在规则二和三上表现突出;Alien vs. Predator 采用了斜体与金属化风格;G.I. Joe: Retaliation 使用了除字距调整外的所有技巧;WALL·E 侧重规则二;Back to the Future 展示了规则一、二和四。文末更新指出,Star Trek: The Next Generation 是一个典型范例,甚至用了星空背景。文章最后提到,这篇内容的扩展版收录在书籍 Typeset in the Future 中。
The article presents six typographic rules for making text look futuristic in science fiction movies, using a step-by-step transformation of a word in Eurostile Bold as an example. Rule 1 involves adding an italic slant to suggest forward motion. Rule 2 introduces a mix of curvy and angular forms. Rule 3 adds "consummate Vs," or sharp V-shaped notches in letters. Rule 4 combines letters to reflect the fictional "Kern Wars" and avoid violating the "Kern Tithe." Rule 5 removes arbitrary horizontal segments from letters. Rule 6 incorporates noise textures, brushed metal effects, blue lighting, embossing, and a star field background.
The author identifies Ridley Scott's Blade Runner as the "Ur Example" of these principles in action. Numerous other films are cited as following these rules to varying degrees. Battlestar Galactica (2003) and Transformers apply nearly all the rules, with the latter emphasizing brushed metal. Guardians of the Galaxy uses most tricks except italics, while RoboCop focuses on consummate Vs and extreme embossing. Star Wars exemplifies Rule 4 with its connected letters, and The Amazing Spider-Man follows most rules but is noted for missed kerning opportunities.
Further examples include Captain America: The Winter Soldier for its strong use of Rules 2 and 3, Alien vs. Predator for its italic and metallic style, and G.I. Joe: Retaliation for using every trick except kerning. WALL·E is highlighted for its focus on Rule 2, and Back to the Future demonstrates Rules 1, 2, and 4. An update notes that Star Trek: The Next Generation is a quintessential example, even featuring a star field. The article concludes by noting that an expanded version appears in the book Typeset in the Future.
- 讨论指出,某些字体被赋予了文化含义:Neuland 和仿中文字体常被当作非西方文化的刻板代表,而 Eurostile 等则在科幻媒体中成为"未来感"美学的代名词。
- 关于《回到未来》的 logo 是否真的比《夺宝奇兵》的更有"未来感"的争论表明,这类联想更多是语境和使用惯例赋予的,而非字体本身固有的属性。
- 作者在原网站内容基础上扩展成书,深入梳理了科幻字体惯例的历史背景,是理解这些设计趋势的宝贵资料。
- 多位评论者指出该网站已停止更新;有人建议观察 AI 生成字体是否会重复这些陈词滥调,也有人询问 Trajan 的流行是否终将结束。
- 讨论中提到具体案例,如《 Avatar 》使用的 Papyrus 字体和《 Terminator 》的 logo,并戏谑说《 Avatar 》续集可能会把 Papyrus 用到 2030 年代。
- 一位创客空间的 logo 设计师提到,Michroma 可作为 Google Fonts 中 Eurostile 的替代品,显示这些字体话题在实际设计中的应用价值。
- 该帖子在沉重的科技新闻中显得轻松幽默,评论者欣赏其诙谐语气,并引用了虚构的"2067 年字距战争"来调侃。
- 关于 ESPN logo 是否类似《 Star Trek 》字体的讨论有些混淆,一位评论者指出,尽管用于现代体育网络,但其外观讽刺性地非常有 80 年代风格。
- 讨论表明,字体的文化联想通常源于媒体和文化语境中的反复出现,而非字体本身的内在特性。
- 评论者普遍希望网站能继续更新,显示出大家对分析当代字体趋势及其文化影响的持续兴趣。
• The discussion highlights how certain typefaces become culturally coded, with Neuland and faux Chinese fonts serving as stereotypical representations of non-Western cultures, while Eurostile and similar fonts have become shorthand for "futuristic" aesthetics in sci-fi media.
• There's debate about whether the Back to the Future logo truly evokes "future" versus Raiders of the Lost Ark, suggesting these associations are more contextual than inherent to the typefaces themselves.
• The author's book expands on the website content with deeper historical context about how sci-fi typography conventions developed, making it a valuable resource for understanding these design trends.
• Several commenters note the site stopped updating, with one suggesting it would be interesting to see how AI-generated fonts might now produce these same clichés, and another asking if the Trajan font trend has finally ended.
• The conversation touches on specific examples like Papyrus for Avatar and the Terminator logo, with humor about Avatar sequels potentially keeping Papyrus in use through the 2030s.
• A makerspace logo designer mentions Michroma as a Google Font alternative to Eurostile, showing practical applications of these typography discussions.
• The post is appreciated as lighthearted content amid heavier tech news, with commenters enjoying the tongue-in-cheek tone and references to fictional "Kern Wars of 2067."
• There's some confusion about whether the ESPN logo resembles the Star Trek font, with one commenter noting it ironically looks very 80s despite being used for a modern sports network.
• The discussion reveals how typeface associations are often more about cultural context and repeated usage in media than any inherent qualities of the fonts themselves.
• Commenters express interest in seeing the site continue updating, suggesting there's appetite for more analysis of contemporary typography trends and their cultural implications.
2026 年 5 月 11 日,Simon Kelley 宣布 CERT 正在披露 dnsmasq 中的六个严重安全漏洞。这些漏洞长期存在,影响几乎所有现代版本的软件。厂商已被提前通知,预计很快会有相应的 dnsmasq 软件包补丁发布。详细信息和补丁可在 dnsmasq 官网找到,修复版本 2.92rel2 已可下载。 On May 11, 2026, Simon Kelley announced that six serious security vulnerabilities in dnsmasq are being disclosed by CERT. These are long-standing bugs affecting nearly all modern versions of the software. The vulnerabilities have already been pre-disclosed to vendors, so patched versions of their dnsmasq packages are expected to be released soon. Details and patches are available on the official dnsmasq website, and a fixed release, version 2.92rel2, has been made available for download.
2026 年 5 月 11 日,Simon Kelley 宣布 CERT 正在披露 dnsmasq 中的六个严重安全漏洞。这些漏洞长期存在,影响几乎所有现代版本的软件。厂商已被提前通知,预计很快会有相应的 dnsmasq 软件包补丁发布。详细信息和补丁可在 dnsmasq 官网找到,修复版本 2.92rel2 已可下载。
这些修复也已提交到开发分支。部分是向后移植的补丁,另一些则是更全面的重写,旨在从根本上解决问题。 Simon 指出,基于 AI 的安全研究大幅增加,导致漏洞报告激增。他花了大量时间来管理这些报告、过滤重复项,并判断哪些问题需要向供应商预先通报、哪些需要立即修复。他认为,鉴于"好人"和"坏人"都可能发现这些漏洞,长期保密期变得越来越不现实,协调保密和回溯修补的工作也非常繁重。
Simon 强调必须在今后的版本中修复这些漏洞,力求让新版本尽可能无漏洞。他提到,在此次公告发布前的几周里,已有多项安全修复提交到 git 仓库。他计划尽快发布 dnsmasq-2.93rc1,目标是尽快推出稳定的 2.93 版本,并鼓励社区测试该发布候选版本,以帮助尽早推出稳定版本。
展望未来,Simon 承认 AI 生成的漏洞报告潮流不太可能停止,因此漏洞管理和修复的工作很可能会持续。他计划优先保证 2.93 按时发布,即便这意味着一些正在进行的修复将在发布后再处理。总体目标仍是不断提高 dnsmasq 的安全性和稳定性。
On May 11, 2026, Simon Kelley announced that six serious security vulnerabilities in dnsmasq are being disclosed by CERT. These are long-standing bugs affecting nearly all modern versions of the software. The vulnerabilities have already been pre-disclosed to vendors, so patched versions of their dnsmasq packages are expected to be released soon. Details and patches are available on the official dnsmasq website, and a fixed release, version 2.92rel2, has been made available for download.
The fixes for these bugs have also been committed to the development tree. While some fixes are backported patches, others are more comprehensive rewrites aimed at addressing root causes. Simon notes that there has been a significant increase in AI-based security research, leading to a flood of bug reports. He has spent considerable time managing these reports, filtering duplicates, and deciding which issues require vendor pre-disclosure and which should be fixed immediately. He believes that long embargoes are becoming less practical, given that both "good guys" and "bad guys" are likely finding these bugs, and the effort to coordinate embargoes and backports is substantial.
Simon emphasizes the importance of fixing bugs in future releases and making new versions as bug-free as possible. He mentions that many security-fix commits have already been made to the git repository in the weeks leading up to this announcement. He plans to release dnsmasq-2.93rc1 soon, with the goal of a stable 2.93 release as quickly as possible. He encourages community testing of the release candidate to help ensure a timely and stable release.
Looking ahead, Simon acknowledges that the influx of AI-generated bug reports is unlikely to stop, so this process of managing and fixing vulnerabilities will likely continue. He plans to prioritize the timely release of version 2.93, even if it means some ongoing fixes will be addressed after the release. The focus remains on improving the security and stability of dnsmasq moving forward.
MaraDNS 已接受了广泛的安全审计(包括 AI 辅助审计),自 2023 年以来未发现严重漏洞。唯一发现的问题都是一些次要的边缘情况,例如在异常条件下资源释放较慢,或仅在极长的 $HOME 路径下才会触发的弃用工具中的缓冲区溢出。
尽管 MaraDNS 捆绑了 Lua 5.1(即 Lunacy),开发者已主动修补了已知漏洞(如 CVE-2014-5461)并采取了额外的安全加固措施。选择 Lua 5.1 的原因是它被广泛采用并被大量 fork,应用于 Adobe Illustrator 、 Roblox(通过 Luau)和 LuaJIT 等系统。
Lua 脚本组件(Lunacy)仅用于 coLunacyDNS —— 这是一个沙箱服务器,脚本只能在本地运行,无法进行远程执行。这显著限制了攻击面,即便理论上存在 Lua 漏洞。
批评者指出,捆绑 Lua 会让维护者对所有 Lua CVE 负责,无论漏洞代码路径是否可达。但语境很重要:许多 Lua 的 CVE 需要精心构造的输入或特定条件,而这些条件在具体部署中往往并不成立。
Debian 的 stable 发布模型依赖于向后移植安全修复,而不是升级到新版本,这一做法被辩护为保障生产稳定性的关键。它能让组织在避免意外行为变化的同时,仍接收关键的安全补丁。
反对者认为,Debian 的方法会导致软件陈旧、维护滞后以及容易出错的手工向后移植。他们主张采用自动化测试和内存安全语言(例如 Rust)等现代实践,从长远来看会更有效。
讨论凸显了稳定性与安全之间的紧张关系:Debian stable 更注重可预测的行为,而另一派则主张更频繁地更新或迁移到更安全的语言以降低漏洞风险。
AI 辅助审计是一把双刃剑——它能更快地发现漏洞,但也提高了对所有软件的审查强度,尤其是流行项目。不过,像 MaraDNS 这样虽不那么流行但审计充分的项目,实际上可能比那些被广泛使用却有更多未被发现缺陷的替代方案更安全。
dnsmasq 虽然在路由器和嵌入式系统中很受欢迎,但最近遭遇了多个严重 CVE,包括堆越界写入和由畸形数据包引起的无限循环。它在很少更新的设备中的广泛部署使这些漏洞尤为令人担忧。
一些用户更偏好模块化工具,而不是像 dnsmasq 这样的全能解决方案,这也符合 Unix 哲学中单一用途工具的理念。像 MaraDNS 这样的替代方案提供了专注且具有良好安全记录的功能,尽管其采用度不及 dnsmasq 。
总体来看,讨论反映出两种截然不同的观点:一方重视软件稳定性,另一方则优先通过现代语言和频繁更新来主动提升安全性。 AI 审计提高了漏洞检测的标准,但也暴露出维护遗留 C 代码库的局限性。受欢迎程度未必等于安全性,像 MaraDNS 这样的维护良好的小型项目展示了较强的韧性。关于 Debian 版本模型的争论则强调了生产可靠性与及时安全改进之间的权衡,目前尚无一致的最佳方案。
• MaraDNS has undergone extensive security audits, including AI-assisted ones, with no serious security bugs found since 2023. The only issues discovered are minor edge cases, such as slow resource release under unusual conditions or a buffer overflow in a deprecated utility triggered only by unusually long $HOME paths.
• While MaraDNS bundles Lua 5.1 (as Lunacy), the developer has proactively patched known vulnerabilities like CVE-2014-5461 and applied additional security hardening. Lua 5.1 was chosen because it's the most widely adopted and forked version, used in systems like Adobe Illustrator, Roblox (via Luau), and LuaJIT.
• The Lua scripting component (Lunacy) is only used in coLunacyDNS, a sandboxed server where scripts can only be controlled locally—remote execution is impossible. This limits the attack surface significantly, even if theoretical Lua vulnerabilities exist.
• Critics argue that vendoring Lua makes the maintainer responsible for all Lua CVEs, regardless of whether the vulnerable code paths are reachable. However, context matters: many Lua CVEs require crafted input or specific conditions that may not apply in a given deployment.
• Debian's stable release model, which relies on backporting security fixes rather than upgrading to new versions, is defended as essential for production stability. It allows organizations to avoid unexpected behavior changes while still receiving critical security patches.
• Critics counter that Debian's approach leads to outdated software, deferred maintenance, and error-prone manual backporting. They argue that modern practices like automated testing and memory-safe languages (e.g., Rust) would be more effective long-term.
• The discussion highlights a tension between stability and security: Debian stable prioritizes predictable behavior, while others advocate for more frequent updates or migration to safer languages to reduce vulnerability risk.
• AI-assisted auditing is becoming a double-edged sword—while it helps find bugs faster, it also increases scrutiny on all software, especially popular projects. However, less popular but well-audited software like MaraDNS may actually be more secure than widely used alternatives with more undiscovered flaws.
• dnsmasq, despite its popularity in routers and embedded systems, has recently faced multiple serious CVEs, including heap out-of-bounds writes and infinite loops from malformed packets. Its widespread use in rarely updated devices makes these vulnerabilities particularly concerning.
• Some users prefer modular tools over all-in-one solutions like dnsmasq, aligning with the Unix philosophy of single-purpose utilities. Alternatives like MaraDNS offer focused functionality with strong security track records, though they lack the broad adoption of dnsmasq.
The discussion reveals a deep divide between those who value software stability and those who prioritize proactive security through modern languages and frequent updates. While AI auditing is raising the bar for vulnerability detection, it also exposes the limitations of maintaining legacy C codebases. Popularity does not necessarily correlate with security, as smaller, well-maintained projects like MaraDNS demonstrate strong resilience despite less visibility. Meanwhile, the debate over Debian's release model underscores the trade-offs between production reliability and timely security improvements, with no clear consensus on the optimal approach.
Needle 是 Cactus Compute 开发的一款 2600 万参数的"Simple Attention Network",由 Gemini 3.1 蒸馏而来,专为在手机、手表、眼镜等消费端设备上高效运行而设计。该模型擅长个人 AI 场景下的一次性函数调用(single-shot function calling),在该任务上优于 FunctionGemma-270m 和 Qwen-0.6B 等更大模型。架构紧凑,采用编码器—解码器设计,使用了 GQA 、 RoPE 和 ZCRMSNorm 等技术;在 2000 亿 token 上完成预训练,随后在一个包含 20 亿 token 的函数调用数据集上进行了微调。 Needle is a 26-million-parameter "Simple Attention Network" developed by Cactus Compute, distilled from Gemini 3.1 and designed to run efficiently on consumer devices like phones, watches, and glasses. The model specializes in single-shot function calling for personal AI applications, outperforming larger models like FunctionGemma-270m and Qwen-0.6B on this specific task. It features a compact architecture with an encoder-decoder structure, using techniques like GQA, RoPE, and ZCRMSNorm, and was pretrained on 200 billion tokens before being fine-tuned on a 2-billion-token function call dataset.
Needle 是 Cactus Compute 开发的一款 2600 万参数的"Simple Attention Network",由 Gemini 3.1 蒸馏而来,专为在手机、手表、眼镜等消费端设备上高效运行而设计。该模型擅长个人 AI 场景下的一次性函数调用(single-shot function calling),在该任务上优于 FunctionGemma-270m 和 Qwen-0.6B 等更大模型。架构紧凑,采用编码器—解码器设计,使用了 GQA 、 RoPE 和 ZCRMSNorm 等技术;在 2000 亿 token 上完成预训练,随后在一个包含 20 亿 token 的函数调用数据集上进行了微调。
为设备端部署做了大量优化:在 Cactus 基础设施上运行时,预填充(prefill)速度可达每秒 6000 个 token,解码速度可达每秒 1200 个 token 。模型权重和数据集生成代码全部开源,可在 Hugging Face 的 Cactus-Compute/needle 仓库获取。网络由 12 层编码器和 8 层解码器组成,嵌入层权重共享,词表为 8192 个 BPE token 。
上手简单:克隆仓库并运行安装脚本后可在 localhost:7860 启动网页交互界面,方便测试模型并在自定义工具上进行微调。提供的 Python API 支持加载检查点、对输入进行 token 化并生成函数调用输出,接收文本查询和工具定义,返回结构化的函数调用参数。
在定制方面,Needle 同时提供网页界面和命令行工具,可在自定义数据集上微调。网页界面能利用 Gemini 生成合成训练数据、训练模型、评估性能并打包结果;CLI 支持完整训练流程、在 PleIAs/SYNTH 数据集上预训练、检查点评估,以及为有 Google Cloud 权限的用户管理 TPU 等操作。
尽管 Needle 在函数调用任务上表现突出,开发者也指出它仍属实验性、主要面向边缘设备的小型 AI 方向。更大的模型在对话能力和通用性上仍具优势。项目鼓励用户用自己的工具测试并根据需要微调,同时也提醒小模型有时表现可能较为不稳定。
Needle is a 26-million-parameter "Simple Attention Network" developed by Cactus Compute, distilled from Gemini 3.1 and designed to run efficiently on consumer devices like phones, watches, and glasses. The model specializes in single-shot function calling for personal AI applications, outperforming larger models like FunctionGemma-270m and Qwen-0.6B on this specific task. It features a compact architecture with an encoder-decoder structure, using techniques like GQA, RoPE, and ZCRMSNorm, and was pretrained on 200 billion tokens before being fine-tuned on a 2-billion-token function call dataset.
The model is optimized for on-device deployment, achieving impressive inference speeds of 6000 tokens per second for prefill and 1200 tokens per second for decode when running on Cactus infrastructure. Weights and dataset generation code are fully open-source, available on Hugging Face under the Cactus-Compute/needle repository. The architecture includes 12 encoder layers and 8 decoder layers, with tied embeddings and a shared vocabulary of 8192 BPE tokens.
Getting started with Needle is straightforward. Users can clone the repository and run the setup script to launch a web playground at localhost:7860, where they can test the model and fine-tune it on custom tools with minimal effort. The Python API allows for simple integration, with functions for loading checkpoints, tokenizing inputs, and generating function call outputs. The model accepts a text query and tool definitions, returning structured function call arguments.
For customization, Needle provides both a web interface and CLI tools for fine-tuning on custom datasets. The playground can generate synthetic training data using Gemini, train the model, evaluate performance, and bundle the results. The CLI supports various operations including full training runs, pretraining on the PleIAs/SYNTH dataset, evaluation of checkpoints, and TPU management for those with access to Google Cloud infrastructure.
While Needle excels at function calling, the developers note that it's experimental and focused specifically on redefining tiny AI for edge devices. Larger models still have advantages in conversational settings and general scope. The project encourages users to test the model with their own tools and fine-tune as needed, acknowledging that small models can sometimes be finicky in their behavior.
• Needle 的小体积(14MB,INT4)为自然语言命令行界面带来了可能性,用户可以用简单英文描述来操控设备。尽管大家普遍兴奋,但也有人担心额外 14MB 的存储开销和计算成本。
• 该模型已部署在一个 HuggingFace Space 上,并配有简易的 Dockerfile,方便做实验。有人建议并正在制作 playground 的视频演示。
• 有用户表示困惑:有人一开始把模型大小误读为 26B 而不是 0.026B 。标注中的 M 和 B 被认为不够直观,建议直接写成 0.026B 以提高清晰度。
• 蒸馏能把大型模型智能压缩为更小的模型,从而减少磁盘空间、内存和计算需求,但代价是基准性能低于原模型。
• 有人质疑为何用 Gemini 作为对比对象,认为其它模型在工具调用能力上可能更强。一个解释是选择 Gemini 部分原因在于其 API 定价更为实惠;另有用户指出 Gemini 和 Kimi 可以用于类似场景。
• 主要应用场景是在资源受限的设备上部署 AI(如手机、手表、耳塞和智能眼镜)。具体例子包括智能家居控制(例如用语音切换灯光)以及在树莓派等定制硬件上的复古收音机等设备中增强语音助手功能。
• 性能反馈总体积极:有用户报告说它在设置闹钟和管理购物清单方面优于 Siri 。但关于失效模式的问题仍未完全解决,比如它如何处理无法识别的请求、模糊的工具定义或多步骤工具链调用。
• 该模型可以作为大型智能体流水线中的第一道工具调用器,把结果传给更强大的模型。目前还不支持上下文学习,但未来计划加入。代码库中包含数据集处理管道,可能会全部开源。
• 在无特权的 CPU LXC 容器中运行时遇到了一些技术问题,尽管理论上该模型应能在纯 CPU 设备上运行。 HuggingFace 上 tokenizer 仓库的访问问题已被迅速解决。
• 强调了开源理念与实用部署细节,鼓励社区进行尝试。部分社区成员提出了训练数据版权方面的担忧,但团队澄清蒸馏过程中并未访问原始模型权重。
讨论表明,Needle 的极小体积让在边缘设备上实现本地化 AI 成为热点,智能家居控制和语音助手等实用场景被频繁提及。有人质疑是否需要为语音助手开发专门的轻量模型,而不是沿用现有方案;也有人认为本地化带来的延迟降低和隐私保护具有明显优势。技术社区对开放部署反应热烈,许多用户已开始测试或计划集成。关于模型训练数据的版权与伦理问题虽被提及,但并未主导讨论,反映了 AI 社区中持续存在的紧张议题。
• Needle's small size (14MB, INT4) opens possibilities for natural-language command-line interfaces where users can describe actions in plain English. Excitement exists but concerns about 14MB overhead and computational cost remain.
• The model has been deployed to a HuggingFace Space with a simple Dockerfile, making it accessible for experimentation. A video demo of the playground was also suggested and is being created.
• Some users report confusion: one initially misread model size as 26B instead of 0.026B. The M vs B notation was deemed too subtle, with 0.026B suggested for clarity.
• Distillation compresses large model intelligence into smaller models requiring less disk space, memory, and compute. The tradeoff is lower benchmark performance compared to the source model.
• Questions arose over choice of Gemini for comparison when other models may have better tool-calling capabilities. Clarification offered that Gemini was chosen partly for its cheaper API pricing. Another user noted Gemini and Kimi could serve similar purposes.
• The primary use case is deploying AI on resource-constrained devices like phones, watches, earbuds, and glasses. Concrete examples include smart home control (e.g., toggling lights via voice) and enhancing voice assistants on custom hardware like Raspberry Pi-based retro radios.
• Performance anecdotes are positive: one user reported it outperformed Siri for setting alarms and managing shopping lists. Questions about failure modes remain, such as how it handles unrecognized requests, ambiguous tools, or multi-step tool chaining.
• The model could serve as a first-pass tool caller in a larger agent pipeline, passing results to a more capable model. In-context learning is not yet supported but planned. The dataset pipeline is included in the codebase, with potential full release.
• Technical issues running on CPU in unprivileged LXC containers were reported, though the model should ideally work on CPU-only devices. Access issues with the tokenizer repository on HuggingFace were promptly resolved.
• Open-source ethos and practical deployment details are emphasized, with encouragement for community experimentation. Copyright concerns around training data were raised by some community members, though the team clarified distillation did not access original weights.
The discussion reveals strong enthusiasm for Needle's minimal footprint enabling local AI on edge devices, with practical use cases around smart home control and voice assistants recurring throughout. Some skepticism persists around whether current voice assistant needs justify dedicated tiny models versus existing solutions, while others see clear latency and privacy advantages. The technical community responded warmly to the open deployment, with several users immediately testing or planning integrations. Copyright and ethical concerns around model training data surfaced but didn't dominate the conversation, reflecting broader ongoing tensions in the AI community.
DuckDB 团队推出了 Quack,一种新的客户端 - 服务器协议,允许多个 DuckDB 实例相互通信。传统上 DuckDB 是进程内数据库,类似于 SQLite,在单一进程内运行、没有客户端 - 服务器架构。虽然这种设计在交互式分析和嵌入式场景中很出色,但当多个进程需要同时修改同一个数据库时就显得不足。很多用户不得不采用变通办法,比如自建 RPC 、使用 Arrow Flight SQL 的第三方实现,甚至在 PostgreSQL 中运行 DuckDB 。 Quack 直接填补了这一空白,使独立进程能够并发读写,实现完整的多用户体验。 The DuckDB team has introduced Quack, a new client-server protocol that allows multiple DuckDB instances to communicate with each other. Traditionally, DuckDB has been an in-process database, meaning it runs within a single process without a client-server architecture, similar to SQLite. While this design excels in interactive analytics and embedded use cases, it falls short when multiple processes need to modify the same database simultaneously. Many users resorted to workarounds like custom RPC solutions, third-party implementations using Arrow Flight SQL, or even running DuckDB inside PostgreSQL. Quack addresses this gap directly, enabling a full multi-user experience where separate processes can read and write data concurrently.
DuckDB 团队推出了 Quack,一种新的客户端 - 服务器协议,允许多个 DuckDB 实例相互通信。传统上 DuckDB 是进程内数据库,类似于 SQLite,在单一进程内运行、没有客户端 - 服务器架构。虽然这种设计在交互式分析和嵌入式场景中很出色,但当多个进程需要同时修改同一个数据库时就显得不足。很多用户不得不采用变通办法,比如自建 RPC 、使用 Arrow Flight SQL 的第三方实现,甚至在 PostgreSQL 中运行 DuckDB 。 Quack 直接填补了这一空白,使独立进程能够并发读写,实现完整的多用户体验。
从用户角度看,Quack 很容易上手。客户端和服务器都是 DuckDB 实例,功能通过 DuckDB v1.5.2 中的 Quack 扩展提供。使用时在一台实例上启动 Quack 服务器,另一台用简单的认证令牌连接即可。连接后,查询远程表与查询本地表一样简单。客户端还可以在远程服务器上创建表,或通过 query 函数把复杂的原生 SQL 直接发到远端执行。
Quack 的设计基于成熟技术并针对性能进行了优化。它以 HTTP 作为传输层,能利用现有且高度优化的基础设施,便于与负载均衡、防火墙等工具集成,也支持 DuckDB-Wasm 实例从浏览器原生连接。协议消息使用自定义 MIME 类型 application/duckdb,复用 DuckDB 自身高效且经过验证的序列化原语。安全性默认通过自动生成的认证令牌和绑定到 localhost 来保障;如果需要将服务器暴露到互联网,强烈建议用 nginx 等 HTTP 代理做 SSL 终止。性能方面,Quack 优化到可以在一次往返中完成查询及其初始结果返回,这对延迟敏感的操作至关重要,同时在大批量数据传输上也非常高效。
对 Quack 、 PostgreSQL 和 Arrow Flight SQL 的基准测试显示了令人信服的结果。在批量数据传输场景中,Quack 表现显著优于两者——在不到 5 秒内传输了 6000 万行数据,比 Arrow Flight 更快,且远超 PostgreSQL 。在小写入场景(强调往返效率)下,Quack 在最多 8 个并行线程时也意外地优于 PostgreSQL,达到约每秒 5500 次事务的水平。这些性能使 DuckDB 能够支持新的场景,例如汇总遥测数据或让多个数据生产者驱动仪表板,从而将其从"进程内分析工具"的小众角色推向数据架构中的更核心位置。
Quack 的发布只是更大路线图的第一步。未来计划包括把 Quack 集成到 DuckLake 以支持远程 catalog 服务器,改进 DuckDB 核心以应对更高的事务吞吐和更多并行线程;团队还在考虑通过扩展支持自定义消息,并增加用于只读副本的复制功能。该协议将在 2026 年秋与 DuckDB v2.0 一同为生产环境的发布而进一步完善。团队也承认 MotherDuck 、 GizmoSQL 等项目对其设计的影响;虽然他们选择不采用 Arrow Flight SQL,以保持对序列化的控制并避免强制性的多轮往返,但仍认可其作为交换格式的价值。
The DuckDB team has introduced Quack, a new client-server protocol that allows multiple DuckDB instances to communicate with each other. Traditionally, DuckDB has been an in-process database, meaning it runs within a single process without a client-server architecture, similar to SQLite. While this design excels in interactive analytics and embedded use cases, it falls short when multiple processes need to modify the same database simultaneously. Many users resorted to workarounds like custom RPC solutions, third-party implementations using Arrow Flight SQL, or even running DuckDB inside PostgreSQL. Quack addresses this gap directly, enabling a full multi-user experience where separate processes can read and write data concurrently.
From a user perspective, Quack is straightforward to set up. Both the client and server are DuckDB instances, and the functionality is provided through a Quack extension available in DuckDB v1.5.2. To connect, a user starts a Quack server on one instance and connects to it from another using a simple authentication token. Once connected, querying a remote table is as easy as querying a local one. The protocol also supports creating tables on the remote server from the client side and even shipping complex, verbatim SQL queries for remote execution using a `query` function.
The design of Quack is built on proven technologies and optimized for performance. It uses HTTP as its transport layer, benefiting from a ubiquitous and highly optimized infrastructure that is easy to manage with tools like load balancers and firewalls. This also allows DuckDB-Wasm instances to connect natively from a browser. Protocol messages use a custom MIME type, `application/duckdb`, which leverages DuckDB's own efficient and well-tested serialization primitives. Security is handled by default through auto-generated authentication tokens and binding to localhost, with strong recommendations to use an HTTP proxy like nginx for SSL termination when exposing the server to the internet. For performance, Quack is optimized to handle a query and its initial results in a single round trip, which is crucial for latency-sensitive operations, while also being highly efficient at bulk data transfer.
Benchmarking Quack against PostgreSQL and Arrow Flight SQL reveals compelling results. For bulk data transfer, Quack significantly outperforms both, transferring 60 million rows in under 5 seconds, which is faster than Arrow Flight and dramatically faster than PostgreSQL. For small writes, which stress round-trip efficiency, Quack surprisingly outperforms PostgreSQL up to 8 parallel threads, achieving around 5,500 transactions per second. This performance unlocks new use cases for DuckDB, such as centralizing telemetry data or driving dashboards from multiple data producers, moving it beyond its niche as an in-process analytics tool into a more central role in data architecture.
The release of Quack is the first step in a larger roadmap. Future plans include integrating Quack into DuckLake to enable remote catalog servers and improving DuckDB's core to handle higher transaction throughput with more parallel threads. The team is also considering extending the protocol to allow custom messages via extensions and adding replication capabilities for read replicas. The protocol will be refined for a production release alongside DuckDB v2.0 in the fall of 2026. The team acknowledges the influence of projects like MotherDuck and GizmoSQL, and while they chose not to use Arrow Flight SQL to maintain control over their serialization and avoid mandatory multi-round-trip waits, they see its value as an interchange format.
DuckDB 已成为许多工作流中不可或缺的工具,包括传感器数据摄取、 LLM 交互、分析和数据管道,用户赞赏其多功能性和性能。 Quack 协议解决了一个常见痛点:当另一个进程锁定数据库时无法访问 DuckDB,从而实现了并发访问,无需构建自定义服务器层。 Quack 为基于 DuckDB 的应用提供了水平扩展能力,使其更适合生产场景,比如内部分析平台和可观测性数据系统。将 DuckLake 与 Quack 结合使用,可以替代更重的系统(如 Mimir 或 ClickHouse),显著降低运维复杂度,尤其对已在 DuckDB 生态中投入的团队更有吸引力。
一些用户对 DuckDB 范围不断扩大的方向感到困惑,拿它与 SQLite 的明确角色作比较;另一些人则认为 DuckDB 作为嵌入式分析引擎的演进既连贯又优雅。一个实际用例是:在数据管道中生成 .duckdb 文件并通过 S3 提供服务,使应用以约 30GB 数据集达到类似 BigQuery 或 ClickHouse 的性能,而无需相应的基础设施成本。 Quack 更应被理解为一种将 DuckDB 作为执行层整合入更大数据工作流的简洁方式,负责远程访问和共享计算资源,而不是把 DuckDB 变成像 Postgres 那样的传统 RDBMS 。
MotherDuck 有自己的专有协议,和 Quack 是分开的,尽管将来可能会支持 Quack;Quack 被设计为任何 DuckDB 客户端 - 服务器通信的通用协议。对于并发需求适度(几千条记录、 2–3 个用户)的小型多用户应用,建议使用 Firebird 或 MySQL 作为比 Postgres 更简单的替代方案,尽管通常不建议将 DuckDB 用于事务性多用户负载。 Quack 为 DuckLake 实现了真正的客户端 - 服务器模型,允许远程客户端在不直接访问底层存储的情况下查询数据,因为远程 DuckDB 实例负责目录管理和计算。
Quack 选择 HTTP/2 作为传输层引发争议:批评者认为它并非大数据传输和流式传输的最优选,而支持者指出它使基于浏览器的原生访问(通过 DuckDB-WASM)成为可能,并且简化了反向代理后的部署。在 15 Gbps 网络上 4.6 秒传输 76GB CSV 的基准测试因为缺乏压缩后大小和编码细节而受到质疑,有估计认为实际传输速率相对于硬件限制并不理想。 WASM 兼容性被强调为关键功能,允许在浏览器中运行的 DuckDB 通过 Quack 直接连接到远程 DuckDB 实例,从而在不同环境间保持一致性。
总体讨论显示,人们对 DuckDB 能力扩展表现出强烈热情,尤其是 Quack 实现了客户端 - 服务器架构与远程访问。尽管有人担忧范围蔓延,但主流观点认为 DuckDB 作为嵌入式分析引擎的核心价值未变,而 Quack 和 DuckLake 等新功能扩展了其在生产负载中的实用性。协议设计选择,尤其是对 HTTP/2 的采用,在部署优势与理论性能权衡之间引发了争论。人们明显有兴趣用 DuckDB 替代更重的分析基础设施,尽管在传统事务性多用户应用中,Postgres 或 MySQL 等数据库仍更为合适。
• DuckDB has become an essential tool for many workflows, including sensor data ingestion, LLM interactions, analytics, and data pipelines, with users praising its versatility and performance.
• The Quack protocol solves a common frustration: the inability to inspect a DuckDB database while another process has it locked, enabling concurrent access without building custom server layers.
• Quack enables horizontal scaling for DuckDB-based applications, making it more viable for production use cases like internal analytics platforms and observability data systems.
• DuckLake combined with Quack could replace heavier systems like Mimir or ClickHouse with significantly less operational complexity, especially for teams already invested in the DuckDB ecosystem.
• Some users express confusion about DuckDB's expanding scope, comparing it to SQLite's well-defined role, though others argue that DuckDB's evolution as an embedded analytics engine with optional extensions is coherent and tasteful.
• A practical use case involves generating .duckdb files in data pipelines and serving them via S3, allowing applications to achieve BigQuery or Clickhouse-like performance without the infrastructure cost, with datasets around 30GB.
• Quack is best understood not as DuckDB becoming a traditional RDBMS like Postgres, but as a cleaner way to integrate DuckDB as an execution layer within larger data workflows, handling remote access and shared compute resources.
• MotherDuck has its own proprietary protocol and is separate from Quack, though it may support Quack in the future; Quack is designed as a general-purpose protocol for any DuckDB client-server communication.
• For small-scale multi-user applications with modest concurrency needs (a few thousand records, 2-3 users), options like Firebird or MySQL are suggested as simpler alternatives to Postgres, though DuckDB is generally not recommended for transactional multi-user workloads.
• Quack enables a true client-server model for DuckLake, allowing remote clients to query data without direct access to the underlying storage, since the remote DuckDB instance handles both catalog and compute.
• The choice of HTTP/2 for the Quack protocol is debated, with critics arguing it's suboptimal for large data transfers and streaming, while supporters note it enables native browser-based access via DuckDB-WASM and simplifies deployment behind reverse proxies.
• Benchmarks showing 76GB CSV transfer in 4.6 seconds on a 15 Gbps network are questioned for lack of detail on compressed size and encoding, with estimates suggesting the actual transfer rate may be underwhelming relative to hardware limits.
• The WASM compatibility is highlighted as a key feature, allowing DuckDB running in a browser to connect directly to remote DuckDB instances via Quack, maintaining consistency across environments.
The discussion reveals a strong enthusiasm for DuckDB's expanding capabilities, particularly around the Quack protocol enabling client-server architectures and remote access. While some users express concern about scope creep, the prevailing view is that DuckDB's core value as an embedded analytics engine remains intact while new features like Quack and DuckLake extend its utility for production workloads. The protocol design choices, especially the use of HTTP/2, spark debate between practical deployment benefits and theoretical performance trade-offs. There's clear interest in DuckDB replacing heavier infrastructure for analytics use cases, though it's generally not seen as suitable for traditional transactional multi-user applications where databases like Postgres or MySQL remain more appropriate.
Google 正在推出一款名为 Googlebook 的新笔记本电脑,定于 2026 年秋季发布。该设备旨在全面整合 Google 的 Gemini AI,将 AI 定位为现代计算的决定性特征,而不仅仅是硬件规格。 Google is introducing a new laptop called Googlebook, set to launch in fall 2026. The device is designed to fully integrate Google's Gemini AI intelligence, positioning AI as the defining feature of modern computing rather than just hardware specs.
Google 正在推出一款名为 Googlebook 的新笔记本电脑,定于 2026 年秋季发布。该设备旨在全面整合 Google 的 Gemini AI,将 AI 定位为现代计算的决定性特征,而不仅仅是硬件规格。
这款笔记本配备了多项由 Gemini 驱动的工具,帮助简化日常任务。 Magic Pointer 允许用户选中屏幕上的任意元素并即时让 Gemini 对其进行操作,例如将多张图像合成为定制乐队海报。 Create My Widget 则可通过简单的语音或文本指令生成个性化桌面小部件,比如为即将到来的 Iceland 之旅创建实时行程追踪器。
除 AI 功能外,Googlebook 还与 Android 手机实现无缝协作。 Cast My Apps 允许用户在笔记本上直接打开并使用手机应用,无需安装;Quick Access 则能像访问本地存储一样浏览手机上的文件。此集成需在运行 Android 17 或更高版本的手机上并完成初始设置。
硬件在追求轻巧机身的同时也提供强劲性能。 Google 与 Acer 、 ASUS 、 Dell 、 HP 和 Lenovo 等主要厂商合作打造该设备。笔记本在设计上也有细节考量,比如键盘上专门的 Google "G" 键,以及带有指纹印记设计的标准退格键。
Google 强调应对 Gemini 的回答进行核实,功能可能会发生变化,视觉匹配的结果也可能有所不同。某些语言在发布时可能不可用。感兴趣的用户可注册以在 2026 年秋季设备发售时收到通知。
Google is introducing a new laptop called Googlebook, set to launch in fall 2026. The device is designed to fully integrate Google's Gemini AI intelligence, positioning AI as the defining feature of modern computing rather than just hardware specs.
The laptop features several Gemini-powered tools that aim to make everyday tasks easier. Magic Pointer lets users select any element on screen and instantly ask Gemini to work with it, such as combining images to create a custom band poster. Create My Widget allows users to build personalized desktop widgets through simple voice or text commands, like generating a live travel tracker for an upcoming trip to Iceland.
Beyond AI features, Googlebook is built to work seamlessly with Android phones. Cast My Apps enables users to open and use their phone applications directly on the laptop without needing to install them, while Quick Access lets users browse files from their phone as if they were stored locally on the device. This integration requires a phone running Android 17 or above and initial setup.
The hardware itself follows a featherweight design philosophy while delivering substantial power. Google has partnered with major manufacturers including Acer, ASUS, Dell, HP, and Lenovo for the device. The laptop includes thoughtful design touches like a dedicated Google "G" key on the keyboard, alongside the standard backspace key with a fingerprint impression design.
Google emphasizes that responses from Gemini should be verified and that features are subject to change, with results varying based on visual matches. Some language availability may differ at launch. Interested users can sign up to be notified when the device becomes available this fall.
• 面向购物场景的 AI 营销显得脱离现实,因为大多数消费者并不会用 AI 做购买决策,而且除 Apple 外,没有任何一家主要公司成功把 AI 当作核心卖点来销售产品。
• AI 在购物方面确实有一些实用场景,例如帮忙找到服装店里难找的尺码,这对体型不标准的人群是真正解决问题的功能。
• 高端 AI 笔记本的目标受众更像是富裕的休闲阶层或社交媒体网红,广告里展示的生活方式就是明证——这更像是在营销"向往感"而非反映现实需求。
• Google 在精准定位 AI 目标受众方面的营销确有成效,即便 HN 用户并非其主要目标市场。
• 虽然部分用户能用 AI 整理产品推荐、过滤被 SEO 污染的搜索结果,但 AI 集成的实际功能(如读取日历等)有时反而有所倒退或仍处于半成品状态。
• 消费者对 Google 硬件存在根深蒂固的不信任,主要因为公司经常砍掉产品和放弃软件项目,这种口碑让人不愿买 Googlebook 之类的新设备,无论价格如何。
• Google 的硬件支持近年来确实有所改善,支持周期更长且时间线更透明,但早期的 Pixel 设备只有两年支持期,而那些承诺"7 年以上"的保障到目前也才持续了大约 2.5 年。
• Google 的战略看起来更像是在防守教育市场份额、抗衡 Apple 的 MacBook Neo,而不是积极进攻消费端高端设备市场。
• Googlebook 更像是对 Chromebook Plus 的升级,而不是廉价教育 Chromebook 的替代品;它的更高定价一方面用于与 Apple 的 Neo 竞争,另一方面也守住了低成本教育市场的阵地。
• Anthropic 、 OpenAI 等主要 AI 公司不太可能自研硬件,这意味着如果 Google 在设备上提供免费或捆绑的 AI 访问权限,会拥有独特优势。
• 广告里"把手机照片发到笔记本上再发邮件"的场景其实很常见,因为当前跨设备的本地文件传输方式仍然出奇地繁琐。
• Googlebook 的营销素材看起来比较仓促:照片和视频中硬件细节不一致,暗示这是对 MacBook Neo 发布的匆忙回应;文案里的一些错误还表明这些材料可能是由 AI 生成、没有经过人工细致校对的。
• 隐私和数据收集问题是人们回避 Google 硬件的常见理由,但也有人指出,大多数消费者更在意便利性和价格,而非隐私。
• ChromeOS 因为几乎不会崩溃、易于远程管理、对不懂技术的家庭成员非常友好而受到好评,尽管它会把用户锁定在 Google 的生态系统中。
• 西方国家的维修文化已经衰落,主要原因是人工成本相对于更换设备的成本过高,这更多是经济驱动而非纯粹的文化因素。
• 学校采用 Chromebook 的主要原因仍然是其集中管理系统;即便换成 Mac 可能在某些情况下更省钱,也会增加 IT 支持的负担。
• Google 服务可能成为依赖它们用户的单点故障:一旦失去 Google 账户访问权,可能意味着丢失笔记本、邮件和数据等整套数字生活。
• Googlebook 看起来运行的是 Android 而非 ChromeOS,上面叠加了桌面版的 Chrome 浏览器,这标志着 Google 在笔记本操作系统策略上的重大转变。
• 通过晃动鼠标来激活的 AI 指针功能存在问题,因为人在系统卡顿或无反应时自然会晃动鼠标,这会误触功能。
• 近期内存短缺和成本上升已经影响了笔记本配置,使得高内存的高端机型变得更昂贵。
讨论显示,对 Google 新款 AI 笔记本存在深层不信任,这源于多重因素:对公司产品承诺历史的不信任、对隐私和数据收集的担忧,以及认为其营销脱节于实际用户需求。很多评论者在权衡改进的支持周期与公司频繁砍掉产品的臭名时,也讨论了购买 Google 硬件的实际影响。对话还涉及更广泛的文化和经济趋势,比如西方维修文化的衰落和当前跨设备文件共享的局限性。总体共识倾向于将 Googlebook 视为 Google 为保住教育市场、对抗 Apple Neo 的防御性举措,而非开创性的新产品类别。
• Marketing AI for shopping use cases feels disconnected from reality because most consumers don't use AI for purchasing decisions, and no major company outside of Apple is successfully selling AI as a primary product feature.
• Specific practical applications of AI for shopping exist, such as scraping clothing stores for hard-to-find sizes, which solves a real problem for people with non-standard body types.
• The target demographic for premium AI laptops appears to be affluent leisure class individuals or social media influencers, based on the aspirational lifestyle shown in advertisements. This is a deliberate marketing strategy targeting aspiration rather than current reality.
• Google's marketing effectively identifies specific target audiences for AI, even if HN users as a demographic are not that target market.
• While some users successfully use AI to summarize product recommendations and filter through SEO-polluted search results, the actual functionality of AI integrations like calendar reading has regressed or remains half-baked.
• A pattern of distrust exists toward Google hardware because the company frequently discontinues products and abandons software projects. This reputation makes consumers hesitant to invest in new devices like the Googlebook regardless of price point.
• Google's hardware support has improved significantly in recent years, with longer support lifetimes and transparent timelines. However, early Pixel devices only had 2 years of support, and the promises of 7+ years are only 2.5 years old.
• Google's strategy appears to prioritize defending their education market share against Apple's MacBook Neo rather than competing in the consumer premium device space.
• The Googlebook appears to be an evolution of Chromebook Plus rather than a replacement for cheap school Chromebooks, targeting a higher price point to compete with Apple's Neo while defending their existing low-cost education segment.
• Other major AI companies like Anthropic and OpenAI are unlikely to make their own hardware, giving Google a unique advantage if they offer free or bundled AI access with devices.
• The ad's concept of emailing photos from phone to laptop is actually common practice because current methods for local file transfer between devices remain surprisingly difficult.
• Googlebook marketing materials appear hastily put together, with inconsistent hardware design details between photos and videos, suggesting a rushed response to the MacBook Neo launch. Some errors in marketing copy suggest these materials may have been generated by AI without proper human proofreading.
• Privacy concerns and data harvesting are frequently cited reasons to avoid Google hardware, though some users note that most consumers prioritize convenience and cost over privacy.
• ChromeOS is praised for being nearly unbreakable, easy to manage remotely, and perfect for non-technical family members, though it locks users into Google's ecosystem.
• Repair culture in Western countries has declined due to high labor costs compared to replacement costs. This is more economically driven than purely cultural.
• Systems for centrally managing Chromebooks in education remain the primary reason schools adopt them, and switching to Macs would create additional IT support burdens despite potential cost savings.
• Google services can be a single point of failure for users who depend on them. Losing access to a Google account can mean losing access to your entire digital life including your laptop, email, and data.
• The Googlebook appears to run Android rather than ChromeOS, with a desktop Chrome browser on top, which represents a significant shift in Google's OS strategy for laptops.
• The AI mouse pointer feature that activates when users wiggle the cursor is problematic because people naturally wiggle the mouse when a system is frozen or unresponsive.
• The recent RAM shortage and rising costs have affected laptop specifications, making premium devices with high RAM configurations more expensive.
The discussion reveals a deep skepticism toward Google's new AI-focused laptop, driven by a combination of historical distrust in the company's product commitment, concerns about privacy and data harvesting, and a perception that the marketing is out of touch with actual user needs. Many commenters discuss the practical implications of purchasing Google hardware, weighing the improved support timelines against the company's notorious habit of discontinuing products. The conversation also highlights broader cultural and economic trends, such as the decline of repair culture in Western countries and the limitations of current cross-device file sharing. The consensus leans toward viewing the Googlebook as a strategic defensive move to protect Google's education market share against Apple's Neo rather than a groundbreaking new product category.
Canada 的 Bill C-22(The Lawful Access Act)重新引入了有问题的监控措施,几乎是去年被撤回的 Bill C-2 的翻版。尽管 Bill C-2 在隐私团体强烈反对后被撤回,Bill C-22 却以边境安全为由保留了许多相同的问题,试图以牺牲数字隐私为代价扩大政府的监控权力。 Canada's Bill C-22, also known as The Lawful Access Act, is a reintroduction of problematic surveillance measures that mirror last year's failed Bill C-2. While Bill C-2 was withdrawn after significant backlash from the privacy community, Bill C-22 retains many of the same concerns under the guise of border security. The legislation represents another attempt to expand government surveillance powers at the expense of digital privacy rights.
Canada 的 Bill C-22(The Lawful Access Act)重新引入了有问题的监控措施,几乎是去年被撤回的 Bill C-2 的翻版。尽管 Bill C-2 在隐私团体强烈反对后被撤回,Bill C-22 却以边境安全为由保留了许多相同的问题,试图以牺牲数字隐私为代价扩大政府的监控权力。
该法案将要求包括电信运营商和消息应用在内的数字服务记录并保存用户的元数据长达一年。元数据能揭示人们的通讯对象、位置以及日常行为模式。扩大元数据的收集与保存,会迫使企业存储比现在更多的个人信息,从而增加数据泄露和被恶意方未经授权访问的风险。
更令人担忧的是,法案授权 Canada 的 Minister of Public Safety 要求公司为其服务设置后门,供执法部门访问。法案声称这些命令不会引入"systemic vulnerabilities",但专家指出在处理加密通信时,这在技术上不可能实现。法案还禁止公司公开披露此类政府命令的存在,完全消除了监控活动的透明度。
法案中对"systemic vulnerabilities"和"encryption"的定义模糊不清,为政府越权留下了大量空间。加拿大官员声称可以在不造成系统性漏洞的情况下增加监控,但这与技术现实相悖。宽泛的定义可能涵盖各类应用和操作系统,从而影响范围广泛的数字服务。
这一做法与英国的情况类似:英国政府曾要求 Apple 在其 Advanced Data Protection 功能中设置后门,Apple 最终为英国用户移除了该功能而非妥协。 Meta 和 Apple 都对 Bill C-22 可能赋予 Canadian authorities 类似权力表示担忧,并公开反对该法案。 US House Judiciary and Foreign Affairs committees 也在致 Canada 的 Minister of Public Safety 的联名信中表达了关切。
现实事件已经证明了监控后门的危险,例如 2024 年的 "Salt Typhoon" 黑客事件,攻击者正是利用了为执法访问用户数据而建立的系统。构建这些监控机制必然会带来可被恶意利用的漏洞。
公众理应享有强有力的隐私保护、透明的数据处理以及对加密信息的明确保障。 Bill C-22 未能提供这些保护,反而推动扩大所谓的合法访问机制,将危及数百万用户的数字安全。
Canada's Bill C-22, also known as The Lawful Access Act, is a reintroduction of problematic surveillance measures that mirror last year's failed Bill C-2. While Bill C-2 was withdrawn after significant backlash from the privacy community, Bill C-22 retains many of the same concerns under the guise of border security. The legislation represents another attempt to expand government surveillance powers at the expense of digital privacy rights.
The bill would force digital services, including telecoms and messaging apps, to record and retain user metadata for a full year. Metadata reveals extensive information about who people communicate with, their locations, and their daily patterns. Expanding metadata collection requirements would compel companies to store even more personal data than they currently maintain, creating larger targets for potential data breaches and unauthorized access by bad actors.
Perhaps most concerning is the provision allowing Canada's Minister of Public Safety to demand companies create backdoors in their services for law enforcement access. The bill claims these mandates cannot introduce "systemic vulnerabilities," though experts note this is technically impossible when dealing with encrypted communications. The legislation also prohibits companies from publicly disclosing the existence of such government orders, eliminating transparency around surveillance activities.
The definitions of both "systemic vulnerabilities" and "encryption" remain unclear throughout the bill, leaving significant room for government overreach. Canadian officials have maintained it's possible to add surveillance without creating systemic vulnerabilities, but this contradicts technical reality. The broad definitions could encompass apps and operating systems alike, potentially affecting a wide range of digital services.
This approach mirrors what occurred in the UK, where the government demanded Apple implement backdoors into its Advanced Data Protection feature. Apple ultimately removed the feature for UK users rather than comply. Both Meta and Apple have expressed concerns that Bill C-22 would grant Canadian authorities similar powers, and both companies have publicly opposed the legislation. The US House Judiciary and Foreign Affairs committees also raised concerns in a joint letter to Canada's Minister of Public Safety.
The dangers of surveillance backdoors are demonstrated by real-world incidents like the 2024 Salt Typhoon hack, which exploited systems built for law enforcement access to user data. Building these surveillance mechanisms inevitably creates vulnerabilities that malicious actors can access. Canadians deserve robust privacy protections, transparent data handling, and clear safeguards for encrypted information. Bill C-22 fails to provide any of these protections, instead pushing for expansive lawful access mechanisms that would compromise digital security for millions of users.
• Bill C-22 的强制性数据保留和加密后门条款可能迫使 Signal 、 WhatsApp 和 iMessage 等端到端加密通讯服务将加拿大用户完全屏蔽,因为这些要求与端到端加密不兼容,且在欧盟已被裁定为非法。
• 包括 Internet Society 、 OpenMedia 和 ICLM 在内的多个倡导组织已建立工具,帮助公民联系议员和部长以反对该立法。加拿大公民自由协会也发布了对该法案影响的详细分析。
• 关于政治行动在加拿大是否有效存在重大分歧:有人认为 FPTP 投票制使个人选票失去意义,另一些人则反驳称加拿大远未达到像俄罗斯那样真正危险的威权状态。
• 一些评论者对发达国家与发展中国家的自由状况进行了对比,指出尽管某些发展中国家在法律上形式自由度较低,但由于治理薄弱、现金经济普遍以及住房和商业监管较少,日常生活中反而享有更多实际自由。
• 该立法似乎深受英国《在线安全法》和加拿大最高法院 Bykovets(2024)案裁决的影响。情报机构声称这些裁决阻碍了其数据收集能力,导致 CSIS 所说的 "going dark"。
• 多位评论者指出,一旦监控基础设施投入使用,即便名义上更名或停止运作,也很难被彻底拆除;他们以 Total Information Awareness 和 Carrier-IQ 等多次更名的项目为例。
• 人们担忧自由党政府有重复尝试通过类似法案的模式:把失败的立法换个名字反复提交,直到最终通过,迫使公民反复抗争。
• 讨论强调了潜在的企业共谋,指出 Apple 和 Google 等大型科技公司本可通过拒绝实施严苛控制来阻止此类立法,但当合规能保护其垄断利益时,它们往往选择配合。
• 一些评论者对主流媒体在自由党提出监控立法时的监督不如在保守党执政时严格表示沮丧,暗示数字权利相关报道存在党派偏见。
• 最近对 James Comey 的起诉被引用为警示案例:指控基于一张模糊的 Instagram 照片,照片中贝壳排列成 "8647",说明监控权力如何被用来将可多种解读的言论刑事化。
讨论表明,公众对 Bill C-22 对加拿大数字隐私与加密通信的影响深感担忧。参与者利用国际比较、历史先例和技术理解来反对该法案。尽管对政治行动能否有效以及不同治理体系下的相对自由存在分歧,但广泛共识是:一旦建立,监控基础设施往往会持续扩张。讨论同时凸显了政府权力扩张与企业合规之间的复杂关系,有人认为科技垄断通过愿意实施利于国家监控和自身利益的控制措施,助长了这种立法。
• Bill C-22's mandatory data retention and encryption backdoor provisions would likely force encrypted messaging services like Signal, WhatsApp, and iMessage to block Canadian users entirely, as these requirements are incompatible with end-to-end encryption and have already been ruled illegal in the European Union.
• Multiple advocacy groups including the Internet Society, OpenMedia, and ICLM have created tools to help citizens contact their MPs and government ministers to oppose the legislation, with the Canadian Civil Liberties Association publishing detailed analysis of the bill's implications.
• There's significant debate about whether political action matters in Canada, with some arguing FPTP voting makes individual votes meaningless, while others counter that Canada remains far from authoritarian states like Russia where voting is genuinely dangerous.
• Some commenters draw paradoxical comparisons between developed and developing nations, arguing that despite less formal freedom on paper, some developing countries offer more practical day-to-day liberty through weaker governance, cash economies, and less regulatory burden on housing and business.
• The legislation appears heavily influenced by the UK's Online Safety Act and Canadian Supreme Court decisions like Bykovets (2024) that intelligence agencies claim have hampered their data collection capabilities, leading to what CSIS calls "going dark."
• Several commenters note that surveillance infrastructure, once implemented, is never truly dismantled even if officially renamed or discontinued, citing examples like Total Information Awareness and Carrier-IQ that evolved through multiple rebrandings.
• There's concern about the Liberal government's repeated attempts to pass similar legislation, with the pattern being to reintroduce failed bills under new names until they eventually succeed, requiring citizens to defend against such proposals repeatedly.
• The discussion highlights potential corporate complicity, noting that major tech companies like Apple and Google could effectively block such legislation by refusing to implement draconian controls, but choose compliance when it protects their monopolistic interests.
• Some commenters express frustration that mainstream media provides less scrutiny of surveillance legislation when proposed by Liberal governments compared to Conservative ones, suggesting partisan bias in coverage of digital rights issues.
• The recent indictment of James Comey based on an ambiguous Instagram photo of seashells arranged as "8647" is cited as a cautionary example of how surveillance powers can be used to criminalize speech that can be interpreted in multiple ways.
The discussion reveals deep concern about Bill C-22's implications for digital privacy and encryption in Canada, with participants drawing on international comparisons, historical precedents, and technical understanding to argue against the legislation. While there's disagreement about the effectiveness of political action and the relative freedoms in different governance systems, there's broad consensus that surveillance infrastructure tends to expand permanently once established. The conversation also highlights the complex relationship between government power grabs and corporate compliance, with some arguing that tech monopolies enable such legislation through their willingness to implement controls that serve both state surveillance and corporate interests.
119 comments • Comments Link
• archive.org 对 robots.txt 的遵从暴露了一个漏洞:出版商可以通过 robots.txt 阻止其爬虫抓取内容,但他人仍能借助该档案馆大规模获取这些内容。这也意味着,如果 archive.org 自行停止抓取,出版商可能会允许其他途径的访问。
• 令人沮丧的是,遵守 robots.txt 反而让 archive.org 处于不利地位,而一些人(包括资金雄厚的大公司)无视这些规则获利,却往往不会受到惩罚。
• robots.txt 的初衷是控制自动化爬虫,而不是阻止用户通过 Wayback Machine 手动访问 URL 。
• archive.org 明确表示,为了更广泛的可访问性,会忽略 robots.txt 。这一政策自 2017 年宣布后一直在执行。
• 关键问题在于,无论 LLM 公司是从 archive.org 还是直接从原始来源抓取数据,它们都在无视版权法,这使得 archive.org 在版权侵权中的作用相对有限。
• 有人提出折中方案,例如延迟开放访问(30 天到 1 年)或采用托管系统,以在保护出版商收入与保存档案之间取得平衡。
• 通过档案馆绕过付费墙,反而可能利于出版商:它能把一些原本不会接触内容的读者转化为付费订阅用户。
• 档案馆在学术研究和问责中至关重要,它们通过保存勘误、删除记录和文章原始版本来维护事实,否则这些信息可能会丢失。
• 传统媒体档案馆的衰落以及对保存工作的抵制,可能导致"数字黑暗时代",使那些无利可图但重要的信息消失殆尽。
• 利用比特币时间戳或分布式系统等技术构建的加密可验证互联网档案馆,可以在不依赖单一机构的情况下提供防篡改的保存方案。
讨论显示版权执法与信息保存之间存在紧张关系。与会者普遍认为,真正的问题是 AI 公司无视版权法,而非 archive.org 的存档行为。大家也认识到档案馆在研究与问责中的重要性;部分评论者指出,绕过付费墙反而可能将读者转化为订阅用户,从而惠及出版商。对话还涉及新闻业的可持续性、 robots.txt 作为控制手段的局限性,以及需要建立新模式以平衡出版商收入与公众获取信息权利的更广泛议题。 • Archive.org's respect for robots.txt creates a vulnerability where publishers block their crawler, yet people can still scrape publisher content at scale through the archive, suggesting that if archive.org blocked scrapers, publishers might permit access.
• There's frustration that respecting robots.txt puts archive.org at a disadvantage while others profit by ignoring these directives, though large well-funded companies also flout rules without consequence.
• The robots.txt specification was intended to control automated scanning, not prevent individual users from manually requesting URLs through the Wayback Machine.
• Archive.org has explicitly stated they ignore robots.txt for broader access, a policy announced in 2017 and applied consistently since then.
• The core issue is LLM companies disregarding copyright laws regardless of whether they scrape from archive.org or original sources, making the archive's role in copyright infringement negligible.
• Some propose compromises like delayed access (30 days to 1 year) or escrow systems that balance publisher revenue with archival preservation.
• Paywall circumvention through archives actually benefits publishers by converting some non-subscribers into paying subscribers who otherwise wouldn't engage with the content.
• Archives serve crucial functions as research resources and protect truth by preserving corrections, deletions, and original versions of articles that might otherwise be lost.
• The decline of traditional media archives and the fight against preservation efforts threaten to create a "digital dark age" where non-profitable but important information disappears.
• Cryptographically verifiable internet archives using technologies like Bitcoin timestamps or distributed systems could provide tamper-proof preservation without relying on a single organization.
The discussion reveals a tension between copyright enforcement and information preservation, with participants generally agreeing that the real problem lies with AI companies ignoring copyright rather than with archive.org's archival practices. There's recognition that archives serve vital research and accountability functions, with several commenters noting that paywall circumvention can actually benefit publishers by converting readers into subscribers. The conversation touches on broader concerns about the sustainability of journalism, the ineffectiveness of robots.txt as a control mechanism, and the need for new models that balance publisher revenue with public access to information.