← statichum.studio

Two communities hit the same wall in the past two weeks: bloggers drowning in SEO/link-building solicitations (lobste.rs), and job seekers flooded by LLM-personalized recruiting spam harvested from HN hiring threads (969-point thread). Both report that this mail comes from properly authenticated servers and sails past spam filters, leaving crude keyword rules as the only defense. The want: something that classifies sender intent on top of an existing Gmail/IMAP inbox instead of requiring a new email provider.

builder note

Protocol-level signals are exhausted — the spam IS well-authenticated, so the classifier has to read intent (link-building, guest-post, templated recruiting) the way a human does; ship it as a Gmail filter/label layer first, because HEY already proved the screening model and also proved that 'switch your email provider' is the adoption killer.

landscape (3 existing solutions)

Email authentication standards authenticate the sending domain and pass SPF/DKIM/DMARC checks, which is enough to clear most spam filters — but authentication is not delivery, and providers can still apply reputation and content signals on top of it. The practical effect is that LLM-personalized outreach from real authenticated domains sails past content filters, leaving intent classification as the only remaining defense. LLMs made it cheap to personalize at scale; nothing consumer-grade classifies sender intent on top of an existing inbox, leaving a gap between switching providers entirely (HEY) and hand-written keyword filters.

HEY Screener Approve-first screening solves exactly this — but only inside HEY; verified on its feature page that it works as part of the HEY service, not on existing Gmail/IMAP accounts, so adoption means migrating your address.
Gmail / standard spam filters Authenticated, LLM-personalized outreach passes SPF/DKIM/DMARC and content filtering; thread participants fall back to keyword rules ('anything with SEO straight into spam') — whack-a-mole that breaks on the next template.
Greylisting / SpamCop reporting Mail-server-admin tooling suggested in the lobste.rs thread; cuts automated bulk volume but not persistent sequenced outreach, and is unavailable to ordinary hosted-inbox users.
sources (2)
other https://lobste.rs/s/3g02jc/how_do_i_get_seo_email_spam_stop "they still come from legitimate-looking email servers with proper SPF/DKIM/DMARC" 2026-06-08
hn https://news.ycombinator.com/item?id=48370330 "hundreds of emails which are infeasible for a single human" 2026-06-02
emailspam-filteringllm-classifiergmailcold-outreach

Two heavily-upvoted HN threads in the last two weeks show the same pattern: a 664-point story of Codex escalating to root via the docker group, and an Ask HN where at least six independent commenters describe building their own agent sandboxes (yoloai, claude-sandbox, safeexec, QEMU VMs with gated SSH keys). Developers want to run agents at full permissiveness inside strong, local isolation without ceding code to a cloud sandbox — and today they each rebuild it from scratch.

builder note

Don't build another microVM runtime — build the boring glue: `sandboxed <any-agent>` with sane default policies, per-project credential scoping, and an audit log of what the agent tried; the evidence that packaging (not tech) is the gap is six senior HN devs each writing the same wrapper in the same month.

landscape (6 existing solutions)

Isolation tech is abundant (microVMs, gVisor, containers, cloud sandboxes), but nothing has become the low-friction, agent-agnostic local default with deny-by-default network/filesystem policy and scoped credential injection — so experienced developers keep duct-taping their own, which is the demand signal.

Ash Wraps any CLI agent via `ash run -- <agent>`, enforces deny-by-default policies over files, networks, processes, devices, and environment variables, and ships an audit GUI. Comes closest to the ask and ships today. The remaining gap is compositor: Ash is a per-invocation wrapper, not a persistent daemon with per-project credential scoping and a shareable policy file; the hand-rollers in these threads describe wanting to commit a sandbox config alongside their repo so every team member and CI run gets identical isolation automatically.
E2B Cloud-hosted Firecracker sandboxes pitched at enterprises ('Enterprise AI Agent Cloud'); code and credentials leave the laptop, which is precisely what the hand-rollers in these threads are avoiding.
Daytona Cloud sandbox runtime with fast cold starts and MCP integration — same objection: it's remote infrastructure, not a local wrapper around the dev's own machine and repos.
microsandbox Local-first libkrun microVMs — closest to the ask — but young (YC X26) and demonstrably not yet the default: the June 2026 threads show senior devs still hand-rolling QEMU/podman setups instead of adopting it.
Docker / devcontainers The stock answer, but the May 31 incident is literally Codex gaining root through docker group membership, and thread commenters call container isolation 'trivial to break out of.'
rivet sandbox-agent Runs Claude Code/Codex/OpenCode/Amp in sandboxes controlled over HTTP — server-shaped building block, not the one-line local CLI wrapper individual devs keep rebuilding.
sources (2)
hn https://news.ycombinator.com/item?id=48449187 "creates sandboxes... and then sets up an agent... with max permissiveness" 2026-06-08
hn https://news.ycombinator.com/item?id=48348578 "it should not try to find a workaround/exploit autonomously" 2026-05-31
ai-agentssandboxingsecuritydeveloper-toolslocal-first

Mac owners who bought perpetual Office licenses are about to lose editing: a licensing certificate expires July 13, 2026 and un-updatable installs drop to view/print-only. Office 2021 can escape via build 16.83 on macOS 12+, but Office 2019 has no fix, and the affected crowd explicitly refuses the Microsoft 365 subscription. They want buy-once software with real .docx/.xlsx fidelity — and they're loudly distrustful of every current option. Mac/iOS only; Windows and Android are unaffected.

builder note

Don't clone Office — the wedge is the July 13 deadline plus broken trust: SoftMaker already sells buy-once and nobody in these threads even knows it exists, so the gap is credible, public fidelity proof (open THEIR gnarly files) and a migration story marketed directly at stranded Office 2019 owners.

landscape (5 existing solutions)

Alternatives exist at every price point, yet a 1,014-point HN thread and an 8-page MacRumors thread are full of people threatening lawsuits and firewall hacks rather than switching — the persistent gap is a buy-once suite people trust to open their existing .docx/.xlsx perfectly on a Mac.

Microsoft's sanctioned paths (update or Microsoft 365) Per Microsoft's one-time-purchase support article, Office 2019 for Mac reached end of support on 2023-10-10 and cannot be updated to the required build (16.83 on macOS 12+), so 'this issue cannot be resolved by updating or reinstalling Office 2019 for Mac.' Office 2021 for Mac can reach 16.83 and keep working. For Office 2019 owners on older macOS, the sanctioned exits are a Microsoft 365 subscription or Office on the web — the 2024 perpetual option requires macOS 12+, which some 2019-era machines don't meet. Scope: macOS/iOS only, worldwide. Windows and Android unaffected.
Microsoft Office 2024 (perpetual) Perpetual-license Mac suite launched in 2024 and still sold on microsoft.com; covers the Office 2019 end-of-life scenario, though it requires macOS 12+ and costs ~$150 one-time. Addresses the central demand directly but has low awareness in the MacRumors/HN threads, and Microsoft's upgrade roadmap for perpetual licenses remains a trust risk given this very incident.
LibreOffice Free, but repeatedly rejected in both threads on OOXML round-trip fidelity for the Word/Excel files these users live in — 'If I wanted to use LibreOffice instead, I would have.'
SoftMaker Office Closest fit on paper — perpetual licenses including Mac confirmed on its order pages — but it has effectively zero mindshare in these threads (nobody mentions it), and its newer AI/translation features are sold as a subscription tier.
Apple iWork (Pages/Numbers) Free and Mac-native; MacRumors commenters are moving home use to it, but they still need Excel for work files — it's a partial exit, not a replacement.
sources (2)
other https://forums.macrumors.com/threads/microsoft-office-2019-f... "they put an expiration date into a software they specifically sold as a one-time-purchase" 2026-06-02
hn https://news.ycombinator.com/item?id=48341578 "This software I paid for specifically because I didn't want a subscription" 2026-05-30
office-suiteperpetual-licensemacosanti-subscriptionooxml