Editorial note
A few pragmatic infrastructure stories led Hacker News today: small standards that could reshape domain marketplaces, and an engineering play that rethinks where state lives in high-throughput systems. There’s also some neat product-level ergonomics and hobbyist craft worth scanning.
In Brief
Fastmail offers EU data region
Why this matters now: Fastmail’s EU data region gives privacy- and compliance-conscious users explicit control over where their primary mail and file data are stored.
Fastmail now lets users choose the European Union as the "primary home" for their account data, with the main live copy hosted on company-owned servers in Amsterdam, according to Fastmail’s post. The company is upfront about trade-offs: backups, some metadata, and logs still replicate to U.S. locations for resilience, and Fastmail is an Australian company subject to Australian law.
"If what you need is a guarantee that your data remains only in the EU, we don’t have that," Fastmail writes.
This is a pragmatic nod to locality and transparency rather than a legal firewall; expect questions about CLOUD Act and cross-border access to linger.
Dithered QR codes: prettier, riskier
Why this matters now: Designers and product teams can embed low-res monochrome images in QR codes while preserving scan reliability on good surfaces.
Andrew T’s write-up on dithered QR codes adapts error-diffusion (Floyd–Steinberg) to force known QR data modules and then diffuse the visual error into neighbors. The result is a much cleaner-looking black-and-white image inside the code.
"the result is a low-res, one-bit photo with some salt-and-pepper noise on it."
Useful for posters and screens, but remember: aesthetics consume error correction budget. These stylized codes work well in controlled settings and can fail on damaged prints or poor cameras.
My server is a phone now
Why this matters now: Self-hosters get a reproducible template for using a rooted ARM phone as a low-power, portable personal server.
A hobbyist replaced a Hetzner VPS with a rooted CMF Phone 1, kept Android for drivers, and ran services from Termux and chrooted Debian images, with ingress handled by Cloudflare Tunnel and Tailscale—details in the original post. The author’s rationale is pragmatic: "Android already has working drivers for every piece of this hardware." It’s an appealing, low-cost stack for always-on personal services, but not a production-grade alternative: rooting increases the trust boundary and chroots are weak isolation.
Deep Dive
_for-sale DNS records
Why this matters now: Domain owners can now signal availability directly in DNS using a standardized TXT leaf, potentially simplifying domain marketplaces and automated checking.
RFC 10023 introduces a lightweight convention: place a TXT record at the exact _for-sale leaf with the required tag "v=FORSALE1;" and optional fields like contact URI (furi=), price (fval=) or a short note (ftxt=), per the specification write-up. The goal is tidy discovery: brokers and indexers can detect offers without changing the live site or registration metadata.
"The convention is designed to work while the domain is still in active use."
That minimalism is the innovation: a single DNS lookup that plays nicely with active sites. Operational rules are sensible — TTL ≤ 3600, one tag=value per TXT string, and remove the record when the domain is no longer for sale. But the spec also sensibly recommends DNSSEC, because unsigned TXT records are trivially spoofable.
Why this could matter beyond brokers: automated agents and marketplaces can now poll DNS at scale rather than crawling web pages or WHOIS indirectly. That reduces friction for legitimate transfers. But Hacker News discussion quickly landed on legal and marketplace risks. Publicly advertising readiness to sell can feed trademark disputes and UDRP arbitrations; multiple community comments reminded readers that listing a domain for sale doesn’t automatically lose a UDRP — panels still weigh intent and targeting — but it does change the surface area for challenge. Expect registrars, brokers, and trademark lawyers to watch adoption closely. Practical safeguards will likely follow: cryptographic proofs of ownership, registry-level flags, or marketplace verification badges to reduce misuse.
Shopify replaced Redis with MySQL for inventory reservations—and it scaled
Why this matters now: Shopify’s move shows relational databases can replace in-memory systems for certain high-concurrency reservations if you model state differently and use features like SKIP LOCKED.
Shopify reworked its checkout reservation system to stop using Redis and instead store reservations in MySQL by changing the model from "one row per SKU quantity" to "one row per sellable unit," according to their engineering post on scaling inventory reservations. They cap the pool per item/location, use composite primary keys to reduce locking contention, and rely on MySQL 8’s SKIP LOCKED to let concurrent processes claim rows without blocking. The replenisher refills the pool asynchronously; the overall design gets you ACID guarantees without a bespoke reservations service.
"MySQL can now handle workloads we used to assume required specialized infrastructure."
The engineering surprise was operational: the real bottleneck was connection exhaustion from other checkout paths holding connections too long. Instrumenting SQL at the ProxySQL layer revealed the guilty callers. Cleaning up those paths and tuning InnoDB concurrency removed the ceiling and let MySQL hit throughput targets, including Black Friday peaks.
Why this matters to systems designers: it reframes where you draw the line between "fast cache" and "durable source of truth." Redis remains great for ephemeral coordination, but MySQL’s maturity, tooling, and predictable durability can win when you accept a different data model (one row per unit) and leverage modern SQL features. Expect debate: some engineers in the thread argued the solution felt complex compared to simpler GC-based reservation designs; others welcomed the consolidation of operational surface area. Either way, the post is a useful case study in modeling state to match your database’s strengths instead of forcing an external system to behave like one.
Closing Thought
Small standards and careful modeling are quietly powerful. A tiny DNS tag could smooth domain commerce the way a row-model change turned MySQL into a viable reservations engine. Both remind engineers to look for saplings—small protocol tweaks and data-shape changes—that yield outsized operational returns.