2025-08-26

38 篇热帖

1. Google to require developer verification to install and sideload Android apps (9to5google.com)

Google has announced that only apps from developers that have undergone verification can be installed on certified Android devices in 2026...

2. Gemini 2.5 Flash Image (developers.googleblog.com)

Explore Gemini 2.5 Flash Image, a powerful new image generation and editing model with advanced features and creative control.

3. macOS 26 Tahoe's Dead Canary Utility App Icons (daringfireball.net)

These are the not the work of carpenters who care about the backs of the cabinets they’re building. These icons are so bad, they look like the work of untrained “How hard can it be?” dilettante carpenters who only last a few days on the job before sawing off one of their own fingers.

4. Framework Laptop 16 (frame.work)

Framework Laptop 16 is an endlessly customizable laptop with upgradable graphics, powered by NVIDIA® GeForce RTX™ 5070 and AMD's latest Ryzen™ AI 300 Series processors.

5. US Intel (stratechery.com)

The U.S. taking an equity stake in Intel is a terrible idea; it also happens to be the least bad idea to make Intel Foundry viable.

6. FCC bars providers for non-compliance with robocall protections (docs.fcc.gov)

FCC因不合规打击非法机器人电话,切断超1200家提供商网络接入

美国联邦通信委员会(FCC)于2025年8月25日采取执法行动,将超过1200家语音服务提供商从“机器人电话缓解数据库”中移除,从而切断了他们与美国电话网络的连接。这些提供商因未能维护准确的数据库认证,违反了FCC规定,逃避了保护消费者免受非法机器人电话骚扰的义务。

FCC主席布伦丹·卡尔强调,机器人电话是对美国家庭的常见困扰和威胁,FCC正全力反击这些恶意非法来电。未能履行阻止此类电话职责的提供商在网络中没有立足之地,FCC将持续采取行动。

背景与规定 “机器人电话缓解数据库”是FCC确保提供商积极打击机器人电话并实施STIR/SHAKEN来电显示认证机制的关键工具。所有提供商必须:

  1. 认证其已在所有基于IP的网络部分实施STIR/SHAKEN。
  2. 提交机器人电话缓解计划。

未能履行这些义务可能导致从数据库中移除,并阻止该提供商的流量传输。被移除的提供商需获得FCC执法局和有线竞争局的明确批准,方可重新提交申请。

执法历程

  • 2024年12月,FCC曾命令2411家提供商纠正其缺陷文件或说明不应被移除的理由。
  • 2025年8月6日,FCC执法局已先行移除了185家提供商,这些公司曾在至少一次溯源行动中被识别为发起、网关或无响应提供商。
  • 本次大规模移除行动是针对剩余不合规提供商的后续措施。

州检察长联合行动 在FCC移除首批185家公司后,一个由51位州检察长组成的两党联盟发起了“机器人电话围捕行动”,向37家语音提供商发送了警告信,要求其采取措施阻止非法机器人电话通过其网络传输。这些提供商被检察长指出未遵守FCC的溯源支持、数据库认证和缓解计划规定,其中包括七家已被FCC从数据库中移除的提供商。

9. Will Smith's concert crowds are real, but AI is blurring the lines (waxy.org)

Will Smith is being accused of generating fake fans with AI, but it's complicated: the crowds are real, but the videos were manipulated by Smith's team and YouTube itself.

11. One universal antiviral to rule them all? (www.cuimc.columbia.edu)

Taking inspiration from a rare mutation that makes people impervious to viral diseases, a Columbia researcher is developing a therapy that could bestow this superpower on the rest of us.

13. macOS dotfiles should not go in –/Library/Application Support (becca.ooo)

A CLI tool is not an app, and none of you are reading the docs as carefully as you think you are

15. Object-oriented design patterns in C and kernel development (oshub.org)

[My scheduler operations implementation] A benefit of working on your own operating system is that you’re free from the usual "restraints" of collaboration a...

17. Show HN: Turn Markdown into React/Svelte/Vue UI at runtime, zero build step (markdown-ui.com)

Markdown UI - Interactive widgets in Markdown

18. US retail giants raise prices due to tariffs (english.elpais.com)

Walmart, Home Depot, and Lowe’s protected their margins in the second quarter against higher procurement costs

21. Rv, a new kind of Ruby management tool (andre.arko.net)

For the last ten years or so of working on Bundler, I’ve had a wish rattling around: I want a better dependency manager. It doesn’t just manage your gems, it manages your ruby versions, too. It doesn’t just manage your ruby versions, it installs pre-compiled rubies so you don’t have to wait for ruby to compile from source every time. And more than all of that, it makes it completely trivial to run any script or tool written in ruby, even if that script or tool needs a different ruby than your application does.

22. Interactive map of Paul's first century travels in Roman world (www.intofarlands.com)

Use the interactive map to explore all four of Paul's journeys across the Roman World. Explore every stop he visited, the corresponding bible passages, and the stories that came about.

23. iOS 18.6.1 0-click RCE POC (github.com)

Contribute to b1n4r1b01/n-days development by creating an account on GitHub.

24. The MiniPC Revolution (jadarma.github.io)

Reasons why you should consider breaking your hardware up into MiniPCs.

26. How RubyGems.org protects OSS infrastructure (blog.rubygems.org)

Recently, Socket.dev published research highlighting malicious gems designed to steal social media credentials. We wanted to use this as an opportunity to share more about how RubyGems.org security...

27. Silicon Valley is pouring millions into pro-AI PACs to sway midterms (techcrunch.com)

The new pro-AI super-PAC network dubbed Leading the Future aims to use campaign donations and digital ads to advocate for favorable AI regulation and oppose candidates that the group thinks will stifle the industry.

28. Fenster: Most minimal cross-platform GUI library (github.com)

The most minimal cross-platform GUI library. Contribute to zserge/fenster development by creating an account on GitHub.

29. The Limits of NTP Accuracy on Linux (scottstuff.net)

Lately I’ve been trying to find (and understand) the limits of time syncing between Linux systems. How accurate can you get? What does it take to get that? And what things can easily add measurable amounts of time error? After most of a month (!), I’m starting to understand things. This is kind of a follow-on to a previous post, where I walked through my setup and goals, plus another post where I discussed time syncing in general. I’m trying to get the clocks on a bunch of Linux systems on my network synced as closely as possible so I can trust the timestamps on distributed tracing records that occur on different systems. My local network round-trip times are in the 20–30 microsecond (μs) range and I’d like clocks to be less than 1 RTT apart from each other. Ideally, they’d be within 1 μs, but 10 μs is fine. It’s easy to fire up Chrony against a local GPSTechnically, GNSS, which covers multiple satellite-backed navigation systems, not just the US GPS system, but I’m going to keep saying “GPS” for short. -backed time source and see it claim to be within X nanoseconds of GPS, but it’s tricky to figure out if Chrony is right or not. Especially once it’s claiming to be more accurate than the network’s round-trip time20 μs or so. , the amount of time needed for a single CPU cache miss50-ish nanoseconds. , or even the amount of time that light would take to span the gap between the server and the time source.About 5 ns per meter. I’ve spent way too much time over the past month digging into time, and specifically the limits of what you can accomplish with Linux, Chrony, and GPS. I’ll walk through all of that here eventually, but let me spoil the conclusion and give some limits: GPSes don’t return perfect time. I routinely see up to 200 ns differences between the 3 GPSes on my desk when viewing their output on an oscilloscope. The time gap between the 3 sources varies every second, and it’s rare to see all three within 20 ns of each other. Even the best GPS timing modules that I’ve seen list ~5 ns of jitter on their datasheets. I’d be surprised if you could get 3-5 GPS receivers to agree within 50 ns or so without careful management of consistent antenna cable length, etc. Even small amounts of network complexity can easily add 200-300 ns of systemic error to your measurements. Different NICs and their drivers vary widely on how good they are for sub-microsecond timing. From what I’ve seen, Intel E810 NICs are great, Intel X710s are very good, Mellanox ConnectX-5 are okay, Mellanox ConnectX-3 and ConnectX-4 are borderline, and everything from Realtek is questionable. A lot of Linux systems are terrible at low-latency work. There are a lot of causes for this, but one of the biggest is random “stalls” due to the system’s SMBIOS running to handle power management or other activities, and “pausing” the observable computer for hundreds of microseconds or longer. In general, there’s no good way to know if a given system (especially cheap systems) will be good or bad for timing without testing them. I have two cheap mini PC systems that have inexplicably bad time syncing behavior,1300-2000 ns. and two others with inexplicably good time syncing20-50 ns . Dedicated server hardware is generally more consistent. All in all, I’m able to sync clocks to within 500 ns or so on the bulk of the systems on my network. That’s good enough for my purposes, but it’s not as good as I’d expected to see.

30. Show HN: I integrated my from-scratch TCP/IP stack into the xv6-riscv OS (github.com)

Xv6 for RISC-V with Networking. Contribute to pandax381/xv6-riscv-net development by creating an account on GitHub.

32. WiFi-3D-Fusion – Real-time 3D motion sensing with Wi-Fi (github.com)

WiFi-3D-Fusion is an open-source research project that leverages WiFi CSI signals and deep learning to estimate 3D human pose, fusing wireless sensing with computer vision techniques for next-generation spatial awareness. - MaliosDark/wifi-3d-fusion

35. Blacksky grew to millions of users without spending a dollar (newpublic.substack.com)

How Blacksky grew to millions of users without spending a dollar

36. Reverse Engineering All the Raspberry Pis (www.jeffgeerling.com)

Earlier this month I covered Jonathan Clark's effort to reverse-engineer the Pi Zero 2 W, and just yesterday, I discovered TubeTime reverse-engineered the Compute Module 5.

i reverse-engineered the Raspberry Pi Compute Module 5! check it out at github.com/schlae/cm5-r...[image or embed]— Tube Time (@tubetime.bsky.social) August 24, 2025 at 3:57 PM

Both are graciously sharing their schematics and process on GitHub:

jonny12375/rp3a0 for the Zero 2 W / RP3A0 schlae/cm5-reveng for the CM5 / RP2712

Raspberry Pi shares limited board schematics, but sometimes—especially when digging into some esoteric edge case for a carrier board, or in Jonathan's case, desoldering all the chips and building a Pi Zero 2W into a Pico form factor PCB—you need more.

37. Meta is spending $10B in rural Louisiana to build its largest data center (fortune.com)

The massive data center buildout is underway, requiring massive amounts of new power and, increasingly, more fossil fuels and gas plants.

38. Taylor Otwell: What 14 Years of Laravel Taught Me About Maintainability (maintainable.fm)

Taylor Otwell looks back on 14 years of building and maintaining Laravel. From four stars on GitHub to a full-fledged ecosystem, he shares what it takes to design software that lasts—and why simple often wins.