Editorial: Today’s roundup mixes long‑running infrastructure decisions with handy engineering wins. One global timing rule is about to change the baseline for every clocked system. At the same time, small developer tools and hardware refinements remind us that practical engineering — not headlines — often shapes day‑to‑day operations.
In Brief
Any window from your Mac, on your iPhone and iPad
Why this matters now: Sill lets Apple Silicon Mac users stream and control a single Mac window or the whole desktop on iPhone/iPad with low latency and strong local‑first privacy guarantees.
Sill is an open‑source tool that captures a Mac window with ScreenCaptureKit, encodes with hardware HEVC, and sends it directly to an iPhone or iPad — no third‑party server required, according to the project page. The developer emphasizes a private workflow:
"There is no account and no server in between."
Users on Hacker News praised its speed and responsiveness compared with traditional VNC, and it fills a niche between remote‑control tools and Apple’s Sidecar (which extends a display rather than remotes a window). Caveats: it’s Apple‑silicon‑only, audio isn’t streamed, and macOS requires explicit screen‑recording and accessibility permissions.
For anyone who needs to carry a specific app with them — designers, support engineers, or devs demoing a single window — Sill is worth trying. If you rely on cross‑platform remote desktop solutions, treat Sill as a high‑performance, privacy‑first alternative for the Apple ecosystem.
RPKI now protects 70% of internet routes
Why this matters now: IP route origin validation via RPKI now covers about 70% of routed prefixes, meaning a meaningful reduction in accidental or malicious origin hijacks for many networks.
According to an analysis from IPinfo, RPKI adoption jumped sharply in the past year to roughly 70.3% coverage. The piece notes that a single country contributed a large share of the gain, which shows how concentrated action by big operators can move global security metrics quickly. IPinfo framed the milestone bluntly:
"RPKI now protects most Internet routes, and invalid routes barely travel."
This reduces a common class of BGP attacks — origin hijacks — but RPKI is not a panacea: it validates who is allowed to originate a prefix, not the full AS‑path, and misconfigurations can still be abused. Still, the momentum matters operationally: network operators should check ROA coverage for their prefixes and ensure their validators and route‑filters are up to date.
Apple routed a graphite pipe through the iPhone Duo's hinge to dissipate heat
Why this matters now: Apple’s hinge‑integrated graphite pipe helps spread heat across a foldable’s spine, enabling higher sustained performance for the iPhone Duo’s dual displays and new A20 Pro SoC.
Apple’s hardware team threaded a flexible graphite thermal path through the hinge and enlarged the vapor chamber to move heat between the two halves, improving sustained CPU/GPU performance in a very thin foldable, per reporting in PCMag. Apple described the design as a “fundamental state change in the thermal design,” noting they added a second display engine to support simultaneous inner and outer screens:
"For iPhone Duo, we added a second display engine to support simultaneous operation of the inner and outer displays."
For designers of foldables, this is an instructive example of co‑design: chassis, hinge, and silicon must be thought of together to avoid one half becoming a thermal bottleneck.
Deep Dive
BIPM decides to stop adding leap seconds to UTC
Why this matters now: The International Bureau of Weights and Measures (BIPM) will make "continuous UTC" the official standard on 20 May 2027, removing leap seconds and allowing civil time to drift up to one hour from Earth‑rotation time.
This is a concrete, near‑term policy change with real engineering consequences. The BIPM resolution sets the maximum allowed difference |UT1‑UTC| to 3,600 seconds (one hour) and establishes continuous UTC as the formal standard next May. The rationale is practical: leap seconds repeatedly break software and coordination across telecoms, IoT, GNSS, and national critical infrastructure. The body concluded that rare, system‑wide insertions have become increasingly hazardous to coordinate safely.
For engineers, the immediate tasks are familiar but urgent: inventory any codepaths that parse or assume leap‑second semantics, and decide whether to keep leap‑second handling locally, simplify to monotonic counts, or migrate to an alternative timebase. Common gotchas include text parsing or logs that expect a "23:59:60" second, devices that inject leap seconds into system time without compensating monotonic clocks, and integrations that rely on synchronized leap‑second announcements over NTP. Many in the tech community called this decision "long overdue"; others labeled it defeatist and pointed out that adopting TAI (International Atomic Time) outright could have been cleaner. Either way, the change is happening on a fixed schedule.
Operationally, here are practical steps to take now:
- Audit critical systems for leap‑second handling: schedulers, authentication tokens, event ordering, and any code that manipulates UTC strings.
- Test against a continuous‑UTC model: run simulations where a leap second never happens and where UTC drifts relative to UT1 to see downstream effects.
- For systems that must correlate with Earth rotation (astronomy, high‑precision pointing, some surveying), integrate services that provide UT1‑UTC corrections or keep a conversion layer to UT1.
- Revisit time‑sync setup: ensure NTP/chrony clients, GNSS inputs, and kernel timekeeping are configured to expose both wall clock and monotonic time where needed.
There’s also a long‑range social implication: civil clocks diverging slowly from solar time introduces cultural and legal questions over centuries. But for most engineers, the short‑to‑medium term story is migration and testing. The switch date gives teams about seven months to act before continuous UTC becomes the official baseline; treat that window as a firm deadline for inventories, tests, and documentation.
"The decision is driven by practical concerns: leap seconds are a recurring source of software and infrastructure bugs..." — summarized from the BIPM resolution and community discussion.
Closing Thought
Big systems bend around small technical choices. A seemingly arcane decision about leap seconds will ripple through infrastructure the same way a clever app or a hinge redesign quietly improves user experience. If you run—or depend on—time, routing, or device stacks, now is a good week to run that inventory and mark your calendar for May 20, 2027.