limbo

A publication where readers order the articles that don't exist yet. The want-list is public, so writers cook to visible demand instead of guessing — and the demand data is worth as much as the prose.

pairs well with instagrate-me — demand is data

Published ledgers of podcasts, books, audiobooks, and shows — the developer-exhaust doctrine applied to a media diet. What was consumed, when, and what it changed. Five posts have been stubbed since 2023; the kitchen knows.

pairs well with desh — same ledger, different inputs

Search that knows grep 3.11 from grep 2.5 and React 17 from React 19. Queries scoped to the versions you actually run, so answers stop being archaeology from four majors ago.

pairs well with unfiled — constructs carry their versions

GitHub-Blocks-style affordances where the docs already live: deploy this branch, scale that worker, spin a one-off environment. Buttons with permissions and an audit trail, replacing wiki instructions nobody trusts.

pairs well with webpoke — consent rails that already exist

Consumer-driven contract tests for CLIs, file formats, and event streams, enforced in CI. Anything with a boundary can make a promise; anything with a promise can break it loudly instead of quietly.

pairs well with webpoke & unfiled — boundaries with receipts

Exchange, fork, and remix interface specs the way jsfiddle did snippets — discussion attached to the change, not the file. A small plate once prototyped at Optic; the appetite remains.

pairs well with unfiled — semantic change wants a social surface

A new language or platform starves without its table-stakes ecosystem. Port it — or convincing placeholders for it — wholesale with LLMs, and measure what survives contact with users.

pairs well with desh — code on demand, supply side

A Tailscale-shaped VPN that lies to the browser, constructively: divert chosen domains to data already on the device, and truly offline web apps arrive on mobile without service-worker hoops — the URL stays, the network leaves. Generalized, the tailnet is an edge platform: a router for apps written sensibly for that runtime.

pairs well with layers — interposing on the web without permission

Train a network per person you actually call: ship keypoints and voice parameters, reconstruct the face and the voice at the far end, and normalize away bad webcams, bad mics, bad lighting, and bandwidth dips. NVIDIA sketched the video demo years ago and neural voice codecs already run at kilobits; the unshipped product is the relationship — a codec that gets better every call, honest about its tradeoffs. It's just the face and the voice, but it's always them.

pairs well with the tailnet trick — heavy compute at the edges, thin pipes between

An identity security suite for creators: scrub fingerprints, iris reflections, tattoos, voice patterns, and the background details that dox people — from the stream, in real time. The same pipeline that applies the fun filters runs the protection; the cat ears and the biometric firewall are one render pass.

pairs well with a codec of one's own — same face pipeline, opposite mission

Your devices expose context and affordances over the tailnet, LAN, or a Cloudflare tunnel; your phone renders whatever's reachable as a dynamic touchscreen. Rerun the build on the dev box, tail the failing test, approve the deploy — a Stream Deck that's software-defined and discovers its own buttons.

pairs well with desh & the tailnet trick — affordances over the wire

Cross-platform clipboard history synced over the tailnet — copy on the dev box, paste on the phone. With a secrets lane: passwords and tokens travel scoped, expiring, and audited instead of sitting plaintext in a history. The most-used data structure in computing, finally designed.

pairs well with the tailnet trick & desh — a ledger for the smallest buffer

Google Takeout, OpenAI and Anthropic chat exports — the data you already generated, treated as the input to an app ecosystem instead of a compliance download. Emails, notes, maps history, search history, watch history: literally all of it, a platform the providers keep handing you in a box and never let you eat in.

pairs well with avoidant — archives, value added retroactively

Shared chat transcripts are already a meme format; real ones are better. Providers should sign their outputs — verifiable attestations, not screenshots — publish privacy-friendly zeitgeist from the aggregate, and let users opt in to sharing slices: your AI coding spend as public proof of where your work and money go, a hiring signal that finds people already doing the job. Some skills shouldn't be relearned by everybody every time; some concentration funds deeper work.

pairs well with media exhaust — the exhaust doctrine, applied to your AI life

Contextual chat over any document: select a region and the affordances appear — give the author feedback, discuss with whoever else is standing in the same paragraph, translate in place, link the post that explains it, sell your expertise or the exchange itself as training data. Annotation, support, community, translation, and commerce in one selection-anchored UX. The margin was always the best part of the page; it just never had a server.

pairs well with layers, at least — every margin is a layer

Embeddable functions-as-a-service, virtual file systems, code separated from the platform it runs on — and a security story that's a capability model instead of a prayer. Better than sidecars for stream integrations: ship the function to the data, safely, inside anyone's process.

pairs well with ezaf — capabilities granted, not ambient

The backlog entry is two words and refuses elaboration: terraform everything. Calendars, playlists, DNS, org charts, household devices, this menu — if it has state, it can have a plan and an apply.

pairs well with instagrate-me — declared truth, monitored drift

Every codebase has a pattern doc nobody follows after the first deviation — once one person strays, the next can't tell which convention is real. Make the document executable: it explains the tradeoffs, lints the structure, checks the exported shapes, and previews components in context.

pairs well with unfiled — conventions are projections too

Dispatches from a developer filing from ten years in the past and ten years in the future, simultaneously. The genre is the argument: most 'futuristic' tooling is overdue, and most 'standard' tooling is expired.

pairs well with everything — that's the point