Postmob

The timeline cannot be where information ends.

It records when something appears, but not why it matters, what it came from, or where it leads. As new information arrives, everything before it moves further out of view. Saving it does not change the structure; a list of saved items is still another timeline. The information survives, but its context does not. Keeping everything is not the same as remembering it.

Building a network seemed to solve what the timeline could not. Folders, tags, backlinks, and graphs made old information retrievable and its relationships visible. But we still saved first and connected later, leaving more unfinished work as the collection grew. Keeping every possible relation made none stand out. Connecting everything is another way of connecting nothing. The problem was not the number of links. It was that connecting remained a separate task.

Postmob makes connecting part of posting. For nearly five years, we have asked how to build and navigate a network without managing it as a whole. We began with social media, where ideas gain context between people. You choose what should be read with a post when you connect it. The action is as simple as leaving a reply, yet each choice builds the network. Postmob lets people navigate it one connection at a time. This is what comes after the timeline.

Request access

Notes from the work

Longer notes on timeline alternatives, graph readability, and the process of building Postmob.

Building an Alternative Timeline Interface

June 2, 2026

I am building Postmob as an alternative timeline interface. Not because time is irrelevant, but because time alone has become too weak as the primary structure for reading what people think.

A timeline is useful when the question is what happened next. It becomes less useful when the question is what this is connected to, what changed, what it depends on, or what someone is trying to continue.

Before Postmob, I worked on Flint, a startup built around a similar conviction. Flint did not survive as a company, but the problem stayed alive. The interface was never just about arranging posts. It was about whether relation could become something a person could actually read.

Postmob starts from the smaller claim that posts should not only appear after one another. They should be able to point, answer, branch, return, and still remain legible on a screen.

The hard part is not drawing a graph. The hard part is making structure feel ordinary enough that people can use it before they have to explain why it matters.

Postmob is currently in closed beta. If this is a problem you already feel in feeds, threads, notes, or research, write to hello@postmob.net.

What It Means to Read a Graph

May 3, 2026

Postmob is a graph-native social network built on bidirectional threading. The graph is not the interface. It is what naturally forms underneath. And naturally, it becomes complex.

Graph-structured information may be natural for AI agents. Human thought branches like a graph, but our sensory system is built to take in information sequentially, one thing after another. For them, it is a native medium. For us, it is already close to the highest level of complexity we can still meaningfully understand and work with.

The problem is not graph structure itself, but whether people can read it without cognitive overload. A graph can preserve structure and still fail the moment it becomes too demanding to read. The real task is to make graph navigation intuitive enough that a person can follow what matters, trace what changed, and move through structure without losing the path of thought.

An earlier startup built around this direction did not survive, but the underlying conviction did. My cofounder and I believed that what made information useful was not just the information itself, but the context around it. We could feel that before we could measure it, and before we could explain it convincingly to anyone else. Like many new ideas, it had to be used before it could be believed.

This idea did not appear all at once. It moved slowly with me from Seoul to NYC to LA to Austin. What remained was how to preserve context without making it harder to read or build on. Postmob is my answer so far. The name carries the sense of a crowd in motion. Posts collect, collide, drift, and return. Postmob is an attempt to make that motion legible.

The work is still ongoing. If you want to follow it or respond to it, write to hello@postmob.net.

Help test a social space that remembers why things connect.

Postmob is in closed beta for people who write, research, or develop ideas with others.