Elsewhere

A journal that happens to be a social network, with your posts in your files.

Elsewhere is a journal that happens to be a social network, instead of the other way around. Your posts live on your device and your domain, in plain files.

It cross-posts outward to the places your people still are. It is being built to hold my sixteen-year archive without making me become a platform mascot.

The idea

The thing I kept coming back to was stories. They almost solved the human problem, then served the business problem.

The way I said it in March:

“Stories are… kind of a cool journal. But it doesn’t behave as a journal. It behaves as an engagement machine, so that people have to stay stuck to their phones.”

I want the journal part without the trap. A place to put a sentence, a photograph, a little video, a note from the day. Something that can syndicate outward, but does not belong to the outward places.

The promise I recorded the same month:

“I would like to commit right now that we will never change this: we’ll never have an algorithm. If you want to follow your friends at their real domains… you will see every one of your friends’ feeds that you want to see, not based on an algorithm.”

You should be able to own your own social media without becoming a dork about it. It has to be nicer than Instagram, not a hair shirt. The last twenty years of the internet were a massive violation of trust. The way back is not another promise from another company. The way back is tools where you can check the promise because you hold the files.

Elsewhere lives under Sherwood with Amber because the archive and the hosting belong together.

What exists today

• There is a shared Rust core.
• The core uses a SQLite vault for the local archive.
• Static-site generation is wired into the core.
• JSON Feed works, including an _elsewhere extension for the extra social context.
• There is a quoteblock protocol for quoting between feeds without pretending screenshots are a data model.
• Native shells exist for iOS, macOS, Android, and Windows.
• Those shells are wired to the shared core instead of each inventing their own archive.
• Deploy adapters exist for Cloudflare, GitHub Pages, Netlify, and S3.
• Syndication adapters exist for cross-posting outward.
• Encrypted cross-device sync is built into the plan and code path.
• The living demo is the Elsewhere section of this site, where my sixteen-year cross-posted archive already flows through.

The demo matters because I do not want to build imaginary social software for imaginary users. I want to know whether my own archive can move through it without losing its shape.

What it isn’t yet

Elsewhere is pre-alpha. It is not publicly installable. It is not ready for normal people. It is not even ready for patient friends unless they enjoy bug reports as a social activity.

There are hard product problems still unresolved. Identity is hard. Import is hard. Cross-posting without weird duplicate behavior is hard. Sync is hard. Explaining “your domain” without turning the app into homework is hard.

The no-algorithm promise is easy to write and harder to make beautiful. Chronological feeds can still become noisy. Notifications can still become coercive. Owning your files does not automatically make software kind.

Where it’s going

The plan is to make Elsewhere feel like the thing people thought social media was before it became a casino. A place for your actual people. A place where a post can be tiny and still count. A place where your children can read what you wrote without asking a company for an export.

Practically, that means the public path starts with my archive, then a small circle, then boring import and export tools, then apps normal people can use without learning a manifesto.

It should work with Amber for media that needs durable hosting. It should sit inside Sherwood because I do not want the escape hatch from platforms to become another platform owned by whoever funded it.

If the promise is real, you should be able to leave and take the whole thing with you.