The following content is AI-assisted and being rewritten.

Timeline OS: Building on the Solid Web

In our modern digital lives, a troubling bargain has become the norm. We trade our personal data for services, allowing big tech companies to gather vast, detailed profiles on our habits, preferences, and relationships. This centralized model has created data silos that are both valuable targets for hackers and opaque to the very users whose information they hold.

Timeline OS is my response to this problem—a personal operating system for managing the stream of data that defines our lives. And at its foundation is Solid, Tim Berners-Lee's vision for a decentralized web where you own your data.

The Problem: Walled Gardens Everywhere

Your data is scattered and trapped in silos. Each app—Facebook, LinkedIn, Google, your bank—creates its own separate, inaccessible database. You have limited control and portability. Vendor lock-in is the norm.

Between 2009 and 2019 alone, data breaches resulted in the theft or loss of over 230 million healthcare records in the United States. Centralized data is a prime target for attacks.

The Solution: Personal Data Pods

Solid proposes a different model: Personal Data Pods. Your data lives in a secure online vault that you control. Apps connect to your data—they don't own it. You grant and revoke permissions as you see fit.

The revolutionary benefit is true data interoperability. Because your data is stored according to open standards, you can switch between compatible apps without losing your information:

"If a user decides they no longer prefer their current messaging application, they can switch to another one without losing any contacts, message history, or existing conversations."

Lessons From the Frontier

I've spent considerable time building on Solid, and I want to be honest: the tools are still under construction.

The vision is revolutionary, but the ecosystem of libraries, documentation, and servers needed to support it is very much a work in progress. API documentation where key functions are labeled "subject to change, even in a non-major release." Libraries that are buggy. On one occasion during development, a major section of the API reference disappeared for hours.

For most organizations building today, Solid isn't a practical option—yet.

The Control Paradox

A foundational principle of Solid is that the user has ultimate control. They decide who can access their data. This sounds ideal, but when applied to complex procedures like healthcare, it creates a paradox.

To allow a doctor to edit a patient's medical records, the patient must first possess the permission to edit those records themselves. In healthcare, a patient absolutely should not have the ability to alter their own medical history—this could have dangerous consequences. The current Solid specification struggles to accommodate these essential real-world rules.

The Enterprise Gap

A critical piece is missing for widespread enterprise adoption: proper Identity & Access Management (IAM). For an enterprise, IAM isn't just about logging in—it's about audit trails, regulatory compliance, role-based access control, and integration with existing corporate identity systems.

The irony: while one of Solid's key motivations is solving the problem of centralized data silos being attractive targets for ransomware, it currently introduces other fundamental security challenges.

Why I'm Still Building

Despite these challenges, I believe Solid represents the future. The dissertation I conducted on enterprise Solid development captured it perfectly:

"Solid will remain as a passion project at the brink of breaking into the mainstream."

The journey to reclaim our data is a marathon, not a sprint. The groundwork is being laid by dedicated pioneers.

Beyond Folders and Files

My research has led to some counter-intuitive insights about how we should design personal information systems:

1. Usage-Based Organization Beats Hierarchies

In 1990, Yukio Noguchi introduced a paper filing system with no categories. Documents go in envelopes, and each time you use one, it goes back to the left side of the shelf. Frequently used documents naturally migrate left; unused ones accumulate on the right for easy archiving.

This mirrors how Timeline OS approaches data: temporal flow over rigid folders.

2. Navigation vs. Search: Different Memory Systems

Here's a surprising truth: despite the power of modern search, people overwhelmingly prefer finding files by navigating folders. Studies show 56-68% of file retrievals are done by clicking through folders, while only 4-15% use search.

Why? fMRI studies reveal the answer. Navigating a file hierarchy activates the posterior regions of the brain—the same structures we use for real-world spatial navigation. It's largely autonomous, running in the background. Using search activates the left-lateralized frontal regions, associated with language and working memory.

The implication: when you're trying to write a report, using search forces your brain to compete for the same linguistic resources needed for your primary task. Navigation doesn't interfere—it feels effortless because it uses different cognitive pathways.

"Navigating through our folder structures uses the same brain area as navigation through the real world." — Yael Benn et al., 2015

Good systems should support both. Timeline OS provides a visual timeline you can navigate and a command prompt you can query—matching how your brain actually works.

3. Your Body as Interface

In my Bachelor's thesis (2009), I introduced the "Resting Hand Gesture" for multi-touch interfaces—simply placing your hand flat on a surface triggers context-sensitive menus at your fingertips. The interaction is completely natural.

This principle guides Timeline OS: technology that adapts to human behavior, not the other way around.

The Vision

Timeline OS organizes your life data along three axes:

• Temporal — When did it happen? Everything has a timestamp.
• Thematic — What is it about? Tags, categories, content types.
• Social — Who is involved? Relationships and sharing.

Each user has a personal pod—like nodes in a fungal network (rhizomorphs). These nodes can publish and connect, discoverable and queryable. You control what you share.

What's Next

The current building blocks:

• Eidotter — The shared design system with DOS terminal aesthetics
• Pomodoke Calendar — AI-powered scheduling
• Tracker — Habit tracking with retro MDA themes
• EatThisDie — Diabetes management

Each project is a "mod" in the larger Timeline OS ecosystem, all designed to eventually connect to your personal Solid Pod.

---

What killer app or feature would be compelling enough for you to embrace an early-stage technology like Solid for the promise of true data ownership?

Get in touch — I'd love to hear your thoughts.